3.6.0 MxDB for SQL Server Installation and Administration Guide (5697-7088, December 2007)

Chapter 7: Troubleshooting 106

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.

Instead, we recommend that you launch Enterprise Manager either

locally on the active node or within the local subnet. You can then create

the distributor.