| Event Id | 14010 |
| Source | MSSQLServer |
| Description | The remote server is not defined as a subscription server. |
| Event Information | "According to Microsoft Cause: Replication assumes that the local server name, the value returned by SELECT @@servername, is correctly configured to correspond to the computer name or the SQL virtual server name. If the value returned by @@servername is not the same as the computer name plus the optional instance name or the SQL virtual server name plus the optional instance name, you may see this error. Replication expects all servers in the topology to be registered by the computer name plus the optional instance name or, in the case of a clustered instance, the SQL virtual server name (SQL Network Name) plus the optional instance name. Replication is not supported and may not work if you have registered any of the SQL Server instances by IP address or by Fully Qualified Domain Name (FQDN). If you registered any of the SQL Server instances by IP address or by FQDN in the Enterprise Manager you used to configure replication, you may see the above error. Resolution: For each server involved in this replication topology, verify that the value of @@SERVERNAME is correct. Execute ""SELECT @@SERVERNAME"" and ""exec master..xp_cmdshell 'set computername'"". When 'set computername' is executed from Query Analyzer or OSQL for a clustered instance, it returns the SQL virtual server name rather than the node name, and the SQL virtual server name is the value needed for replication. 1.For a nonclustered default instance, ""SELECT @@SERVERNAME"" should return the same value as ""exec master..xp_cmdshell 'set computername'"". 2.For a nonclustered named instance, ""SELECT @@SERVERNAME"" should return the value as ""exec master..xp_cmdshell 'set computername'"" plus ""\"" plus the name of the instance. 3.For a clustered default instance, ""SELECT @@SERVERNAME"" should return the same value as ""exec master..xp_cmdshell 'set computername'"". 4.For a clustered named instance, ""SELECT @@SERVERNAME"" should return the value as ""exec master..xp_cmdshell 'set computername'"" plus ""\"" plus the name of the instance. If the value of @@SERVERNAME is not correct for a nonclustered instance, follow these steps: sp_dropserver '{old_name}', 'droplogins' go sp_addserver '{new_name}', 'local' go Note: After you run the sp_addserver stored procedure, you must restart the SQL Server service for the change to @@SERVERNAME to take effect. If the value of @@SERVERNAME is not correct for a clustered instance, then you must uninstall and reinstall the clustered instance to correct the name. Verify that all SQL Server instances used as a Subscriber, Publisher, and/or Distributor are listed in the replication properties by their computer name or their SQL virtual server name. If they are not, you will need to remove replication, register each SQL Server instance in your local Enterprise Manager by computer name or SQL virtual server name, then reestablish replication. For more information, see these Microsoft Knowledge Base articles: 321822 and 818334." |
| Reference Links | Event Id:14010 of Source Id:MSSQLServer |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.