Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 Replication (2005)
 Actual server name required error, but not true!

Author  Topic 

gavinharriss
Starting Member

17 Posts

Posted - 2008-08-31 : 19:41:52
Hi,

I'm trying to set up SQL Server Replication between two servers with server names MASTER and READONLY.

I'm using a SQL Server account to establish the connection and using a custom port number for the connection to MASTER.

So I'm supplying Server Name as: MASTER,1436
And using a SQL account for login credentials.

On READONLY I can connect to MASTER using these credentials via the SQL Server Management Studio, and can see the Publication I want to make a subscription to. But when I start creating a subscription on READONLY and need to supply connection info to MASTER (in order to get a list of publications) I get the following error:

SQL Server replication requires the actual server 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, 'MASTER'. (Replication.Utilities)

Any idea what the problem could be? I'm totally stumped as I can use the same details in SQL Server Management Studio to establish a connection to MASTER from READONLY without any issue.

Any help or ideas would be greatly appreciated! Cheers.

www.gavinharriss.com

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-08-31 : 23:56:19
It is saying you can't use "MASTER,1436". You must use "MASTER" only. If you can't get to "MASTER" without an error, then add an alias for it. Replication won't care if the alias is named "MASTER" since that's the actual name too. Create the alias on the READONLY server.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

gavinharriss
Starting Member

17 Posts

Posted - 2008-09-01 : 00:01:59
Upon further investigation I've found the problem to disappear if I resort back to the default port of 1433.

Does anyone know how to use a custom port with replication?

www.gavinharriss.com
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-09-01 : 00:04:55
I guess you didn't read my post. You don't need to use the default port. We use custom ports for all of our database servers, most of which are mission critical and have high availability requirements.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

gavinharriss
Starting Member

17 Posts

Posted - 2008-09-01 : 00:43:57
Hi Tara,

Thanks for that - I'll add an alias to see if it will allow me to continue to use a custom port.

Cheers,
Gavin :)

www.gavinharriss.com
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-09-01 : 09:42:02
It will.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page
   

- Advertisement -