Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Replication Migration of the Distributer Error 26 Expand / Collapse
Author
Message
Posted Tuesday, July 2, 2013 9:40 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 8:26 AM
Points: 30, Visits: 295
Hello,

I have upgraded several Database instances form SQL 2000 to 2008 R2 and I am in the process of the following migrations:

Upgrade a Report Server (Currently SQL 2005), this report server contains replicated data from a SQL 2000 machine and is also the distributer and subscriber. I've built the new instance in readiness to move the DBs and have created the new distributer however I am unable to add the SQL 2000 Instance to the publishers list. The errors are of two types:

1) SQL Server Replication requires the actual server name to make a connection to the server. Connections through a server alias, IPAddress, or any other alternate name are not supported. Specify the actual server name, 'AliasName'.

The SQL 2000 Server is clustered so an alias is used, however this clustered node will be upgraded also soon.

2) When I provide the Alias Name, then I receive the following error:

SQL Server cannot connect to Server 'AliasName'. Do you still want to add this Server to the list.

Additional Information:
Failed to connect to server 'AliasName'.(Microsoft.SqlServer.ConnectionInfo).

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The Server was not found or was not accessible. verify that the instance name is correct and that SQL Server is configured to allow remote connections.(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)(Microsoft SQL Server).

Notes:

1)SQL browser Service is enabled
2) TCP Connections are enabled
3) I can connect to the SQL 2000 Node by using the instance Name but not the alias name via SQL Server Management Studio without any problems, this error only occurs through the the adding of publishers via the new distributer.
4) I have disabled the firewall locally and the error still occurs.

i've read through the following:

http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx

This error isnt making any sense to me? Does anyone have any suggestions?

Thanks
Post #1469627
Posted Thursday, July 4, 2013 4:53 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 8:26 AM
Points: 30, Visits: 295
FIXED!!!

Perseverance and we get there!.

The fix was as follows in my case:

Could connect using the [servername]\instancename but not using its alias.

SQL 2008 R2 Standard Edition x64 version

1) Open SQL Configuration Manager
2) Add a new alias entry in both the SQL Native 10.0 Configuration(32 Bit) and SQL Native Client 10.0 Configuration with the following:

a) Alias Name = your servers DNS Alias entry
b) Protocol: select 'Named pipes' from the drop down
c) Server: Should be the named of the server e.g. [servername]\instancename


as they say, 'it's easy when you know how'
And then retry connecting to the server using the Alias and BINGO. This should work for you also.
Post #1470400
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse