Issue on Replication

Please go this one, nicely written article here you may find the help http://www.cryer.co.uk/brian/sqlserver/replication_requires_actual_server_name.htm
To know more please go to my blog http://sqltechtips.blogspot.in/2016/02/fix-transactional-replication-error.html

Check the server name is sys.servers system view.

You have two options:

Option 1. change the server name in replication setup which is showing in sys.servers
                 

select * from sys.servers where server_id=0 

Select allOpen in new window

Option 2. Change the server in system table using below command.

commands:

select * from sys.servers where server_id=0

sp_dropserver <Server Name which is showing in result>
go
sp_addserver <Server Name by which you connect the SQL instance>, LOCAL
go

Select allOpen in new window

Thanks Deepak,

 I tried as same as your steps. But i faced same issue. Actually my requirement is 2014 server is subscriber and 2012 is publisher. As of now I tried to fix the issue, but never get to succeed.

Regards
Murali

Distributor is local or Remote?  

Well... can you try by creating the aliase of subscriber at publisher server.

Distributor is Local.

Actually Publisher is Local server(2012 Standard)  and Subscriber (2014 Standard) which is Cloud Server(AWS). I used to change the actual server name as 'es' server name. Even I tried to Replication from Local(2012) to AWS(2012) using same procedure it's working on good condition. Please help me how to fix this issue.

Regards
Murali

for which server you are getting connection error "can not connect to "SUbscriber" or Publisher\Distributor"

Have you checked the local server name.
SELECT SERVERPROPERTY(N'<servername>')
SELECT @@SERVERNAME

also check the server name and network name.
sp_helpserver

Are you able to connect all instance in ssms by the name which you are using in replication?

Yes both servers are using on their PublicIP. If we may not used to do Replication, its throwing error. That's why I used to connect using PublicIP.

Ok. Try by creating Aliase in SQl server configuration manager at publisher server.

If create aliase in configuration manager, that it may not effect to server right?

Deepak,

 As per your advise I did to change the server name and I finished on replication. Thanks for your support

Regards
Murali