June 8, 2006 at 10:37 am
I'm using the 2005 Management Studio tool on my desktop to manage many production SQL 2000 machines. Several are clustered databases (for failover support). I access these via an alias to the shared instance IP/port. This works great for looking at data and jobs but I can't look at replications. When I try to access a publication, I am denied with the message below. Has anyone else run into this? Is there a workaround?
I've tried this with RTM, SP1 & HotFix2153. No differences.
===================================
SQL Server is unable to connect to server 'xxxxx'.
------------------------------
<< Note: this porvides no help at all! >>
===================================
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, 'XXXXX\XXXXX'. (Replication.Utilities)
------------------------------
Program Location:
at Microsoft.SqlServer.Management.UI.ReplicationSqlConnection.CheckServerAlias(ServerConnection conn)
at Microsoft.SqlServer.Management.UI.ReplicationSqlConnection.Open()
at Microsoft.SqlServer.Management.UI.LaunchPubPropSheet.PrepareToShow()
June 8, 2006 at 11:31 am
I found the answer!
My initial alias was set up as 'xxxxx' (machine name), with the floating IP and port. To fix, I created a new alias as 'xxxxx\xxxxx'. Same IP and port. This one allows me to access the replications. I'm not sure why this worked, but it did.
I'm guessing you'll need use the 'xxxxx\xxxxx' version for the alias name when setting up connections that don't use the default port if you want to manage replications.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply