SQL replication requires the actual server name to make a connection

Question

SQL replication requires the actual server name to make a connection

jvElecenter

SSCarpal Tunnel

Points: 4502
More actions
February 7, 2007 at 3:56 am

#172023

Hi all

We want to replicate our server to a suppliers' server.
Teh error we recieve is : SQL Server replication requires the actual name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name , ''X' (Replication.Utilities)

I have added the alias within SQL Server Configuration Manager, SQL Native client configuration, Aliases.

Anyone any idea ??

JV

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

markwnorsoft SSC Eights! Points: 827 More actions · Answer 1

Have you thought of adding a name to the host file that will point to the ip address of the server that you are trying to connect to.

MohammedU SSCoach Points: 19644 More actions · Answer 2

I don't think that is the case...

Try creating the linked server before configuring replication..

MohammedU
Microsoft SQL Server MVP

victoriapro SSC Enthusiast Points: 166 More actions · Answer 3

Check if in your MMS ditsributor/publisher server is registered as local. If that the case try re-registering it with the server name

omu51 Valued Member Points: 63 More actions · Answer 4

Try use T-sql script instead of Enterprise Manager to add the subscription.

SQL Server Replication requires the actual server name to make a connection to the server.

Connects through a server alias, IP addres, or any other alternate name are not supported.

If you script a publication, will find sp_addsubscriber at the end of the script.

david-719753 Valued Member Points: 73 More actions · Answer 5

I had a similar problem and got around it creating an alias on the publisher machine with the same same name as the subscriber machine. For instance if the subscriber server is called SERVER_A, create an alias with the same name then connect to the subscriber in the New Subscribtion Wizard using this name.

Hridaya Thikey Mr or Mrs. 500 Points: 501 More actions · Answer 6

If your destination server is named instance e.g. destservername\mssqlserver01, the solution for this can be found at:

http://www.sqlservercentral.com/Forums/Topic759989-291-1.aspx

Chand00 SSCertifiable Points: 6466 More actions · Answer 7

Hi,

markwnorsoft solution should work fine. Previously when I had configured replication for the first time over internet I too faced the same problem and adding entry to host file had resolved the problem.

[font="Verdana"]Thanks
Chandra Mohan[/font]

Hridaya Thikey Mr or Mrs. 500 Points: 501 More actions · Answer 8

Yes, adding server on hosts works fine but only for the default instance.

For the databases on the named instance you must set and use the alias.

Apurva SSCrazy Points: 2412 More actions · Answer 9

This link explains in detail how it can be done both for named as well as default instance.

http://social.msdn.microsoft.com/forums/en-US/sqlreplication/thread/9a8cf6b1-a449-4748-b3c2-1c13e2bfcc5b/

paul.millar SSC Veteran Points: 297 More actions · Answer 10

Assuming you haven't renamed machines (which brought me great pain ! even after sp_dropserver / sp_addserver etc)

I had to enable SQL browser on my SQL express (subscriber) instance, which then mediated nicely so that I could use the <hostname>\sqlexpress target - now this works.

Previously I had a default config of express, which did allow connection via SSMS from the publisher machine to the <hostname> (ie: no \sqlexpress) ...but would throw the '...actual server name to make a connection to the server..' error when I tried to setup replication.

Amy Boyd SSC Journeyman Points: 92 More actions · Answer 11

Thanks, Mark. This worked after I was able to create a sysadmin login.