SQL Server failed to install replication component workaround on this instance of SQL Server

Sqlserver2005 occurs when a subscription is copied:　　

"Microsoft SQL Server cannot access these components because replication components are not installed on this instance of SQL Server, see SQL Servers ..."

Workaround:

　　 Due to the need to configure a publication subscription, it has been reported that "SQL Server replication requires an actual server name to connect to the server and does not support connections through aliases, IP addresses, or any other alternative names." Please specify the actual server name "xxxx" (Replication utlities). "

After some analysis, it was found that the machine name was modified after installing SQL Server, and running the following two statements can be seen as follows:

Use Master

Go

SELECT @ @servername;
select SERVERPROPERTY (' servername ')

If these two results are inconsistent, the machine names are changed, and the error is reported when the configuration is copied.

--To fix this problem
--Execute the following statement, and then restart the SQL service after completion
   
if serverproperty (' servername ') <> @ @servername
begin
declare @server sysname
Set @server = @ @servername
exec sp_dropserver @server = @server
Set @server = Cast (serverproperty (' servername ') as sysname)
exec sp_addserver @server = @server, @local = ' local '
End

      

Finally, do not forget to restart the service Oh, after the start, after running:

Use Master

Go

SELECT @ @servername;
select SERVERPROPERTY (' servername ')

Everything is OK, copy also can use!

　　The above is quoted other netizens, according to the above method set up, or the same hint

Workaround:

Do not use IP address when connecting to the database, enter the computer name in the server name to

　　

　　

SQL Server failed to install replication component workaround on this instance of SQL Server