Article ID: 818334 - View products that this article applies to.
You deploy SQL Server 2000 by using the hard disk image of another computer where SQL Server 2000 is installed. If you use SQL Server Enterprise Manager to configure a replication distributor, the configuration of the distributor may not be successful, and you receive the following error message:
SQL Server Enterprise Manager could not configure '<Server>\<Instance>' as the Distributor for '<Server>\<Instance>' .
Error 18483: Could not connect to server '<Server>\<Instance>' because 'distributor_admin' is not defined as a remote login at the server.
Note If you perform these steps on the default instance of SQL Server 2000, the instance name does not appear in the error message.
You may also see that the value of the @@SERVERNAME SQL Server 2000 system global variable is different from the network name of the SQL Server 2000 computer.
Note If you experience this issue in SQL Server 2005, the error message is slightly different. You can also use the workaround that is mentioned in this article to work around the issue.
When you deploy SQL Server 2000 from a hard disk image of another computer where SQL Server 2000 is installed, the network name of the imaged computer is retained in the new installation. The incorrect network name causes the configuration of the replication distributor to fail. The same problem occurs if you rename the computer after SQL Server is installed.
To work around this problem, replace the SQL Server 2000 server name with the correct network name of the computer. To do so, follow these steps:
You can use the @@SERVERNAME global variable or the SERVERPROPERTY('ServerName') function in SQL Server to find the network name of the computer running SQL Server. The ServerName property of the SERVERPROPERTY function automatically reports the change in the network name of the computer when you restart the computer and the SQL Server service. The @@SERVERNAME global variable retains the original SQL Server computer name until the SQL Server name is manually reset.
Steps to Reproduce the ProblemOn the computer where you deployed SQL Server from a disk image, follow these steps:
For more information about disk imaging and SQL Server installations, visit the following Microsoft Web sites:
Article ID: 818334 - Last Review: May 12, 2007 - Revision: 4.4