skjoldtc (12/30/2009)
Is this a bug in SQL Server? Why would an instance that is not part of replication cause this behavior when removed?
The referenced article applies to SQL Server 2000 Standard Edition (see http://support.microsoft.com/kb/811008#appliesto). It looks like a bug in that edition. I hope there's no such bug in 2005 and 2008 🙂