3.4.3 MxDB for SQL Server Installation and Administration Guide
Chapter 4: Troubleshooting 81
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
See the following Microsoft Knowledge Base articles for more
information about removing MSCS.
Windows Server 2003:
http://support.microsoft.com/kb/282227
Windows 2000 Advanced Server:
http://support.microsoft.com/kb/257928
Error When Creating a Distributor for
Replication
Typically you connect to MxDB for SQL Server via <virtual name>,<tcp
port>. However, this connection method does not work when configuring
a distributor for replication and results in the following error.
This situation is by design. Internally, Microsoft uses @@servername (i.e.,
vsql\instance) for verification, while Enterprise Manager uses the
registered server name (i.e., vsql,port#). Because the values do not match,
the attempt to create the distributor fails.
To work around this limitation, it is necessary to connect to MxDB for
SQL Server via <servername>\<instancename>. This type of connection is
not guaranteed from the remote Enterprise Manager because of name
resolution and the custom TCP port used for MxDB for SQL Server.