SQL Server does not install the copy component on this instance of SQL Server.

When copying and subscribing, sqlserver2005 appears: Because the replication components are not installed on this instance of SQL Server, Microsoft SQL Server cannot access these components. For details, see SqlServer solution: to configure a publishing and subscription, but always report: replication requires an actual server name to connect to the server,

When copying and subscribing, sqlserver2005 appears: Microsoft SQL server cannot access these components because the replication components are not installed on this instance of SQL Server. See SQL server solution: because you need to configure a publishing subscription, but always report: "sqlserver replication requires an actual server name to connect to the server,

Sqlserver2005 appears during replication and subscription:　　

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

Solution:

　　You need to configure a publishing and subscription, but always report: "SQL server replication requires an actual server name to connect to the server. You cannot connect to the server by alias, IP address, or any other backup name. Specify the actual server name "xxxx" (Replication Utlities ). "

After some analysis, we found that the machine name was modified after SQL server was installed. Run the following two statements:

Use master

Go

Select @ servername;
Select serverproperty ('servername ')

If the two results are inconsistent, the machine name is changed and the above error is reported during configuration replication.

-- To fix this problem
-- Execute the following statement and restart the SQL service.

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, don't forget to restart the service. After the service is started, run:

Use master

Go

Select @ servername;
Select serverproperty ('servername ')

Everything works, and replication works!

　　The above is a reference from other netizens. After setting the above method, the same prompt is returned.

Solution:

Do not use IP addresses when connecting to the database. Enter the computer name in the server name.