August 1, 2008 at 3:48 pm
This may be confusing but here's my scenario:
Server A is running SQL 2K5 x64 on Win 2K3 X64
Server B is running SQL 2K on Win 2K3 X64
Server C is running SQL 2K5 x64 on Win 2K3 X64
Server B and C are replicating to Server A. Server A was running SQL 2K on Win 2K3 x64 but I rebuilt the server. I had stopped distribution on Server B and C before rebuilding A. We run all our SQL Servers as default instances on non-default ports. With SQL 2K servers, we've never had to specify the port in order for clients to connect, but for SQL 2K5 servers, we always have to have clients connect by specifying a port or creating aliases.
We created an alias for Server A on Server C and the replication was able to resume without issue. I cannot get an alias for Server A to work on Server B. Connections from Server B to Server A will not work unless the port is always specified in the connection string, ie in query analyzer using "ServerA,port." If we don't explicitly add the port, we get: [odbc sql server driver][dbnetlib]sql server does not exist or access denied.
I could get replication to work if I drop the current subscription and re-add Server A as a subscriber using sp_addsubscriber with "ServerA,port" instead of what is currently there, "ServerA". We've done it in other situations and it works. This is a last resort for this situation because I want to avoid having to re-initialize.
Bottom line question: Any idea why I can't get the aliases for SQL2K5 servers to work using the SQL2K client tools, when aliases created with SQL2K5 client tools work?
August 1, 2008 at 4:01 pm
I really don't have an answer to your specific question, but have you tried enabling the SQL Browser service on ServerA? That service should allow you to reference the servers by name without having to know the IP address.
Worth a try, at least 😉
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 1, 2008 at 4:15 pm
Yes, SQL Browser is running on Server A. It doesn't seem to make a difference if it is on or off, to tell the truth.
As an alternative, is there a way to completely change all current references to the subscriber (ServerA) at the publisher/distributor (ServerB)? Right now the name of the subscriber is "ServerA" but if it were to be changed to "ServerA,2433" I know replication would work and I wouldn't have to do the drop/add subscriber. Looking at all the tables in the distribution database, it appears I would have to change entries in MSsubscriber_info and MSsubscriber_schedule. Anywhere else? Is this a bad idea?
August 1, 2008 at 7:09 pm
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply