Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
Initial Snapshot Replication issue between 2005 and 2012

Answered Initial Snapshot Replication issue between 2005 and 2012

  • Thursday, December 27, 2012 12:46 PM
     
     
    Sign In to Vote
    0

    Hello Everyone,

    Here is the situation.  We are trying to use Transactional Replication from a 2005 Standard system to a 2012 BI system.  The 2012 BI Ed does have SP1 installed.  

    We did get it setup on our dev machines without issue.  However, when going to deploy it to production, it bombed during the initial snapshot phase.  I am using the same credentials as we did in test.  I have tried elevated all permissions to Sysadmin to ensure that wasn't an issue suddenly.  As near as I can tell, everything between the dev environment and the prod environment is the same.

    However, as stated, we run into errors during the intial snapshot replication initializatin.  Below is the error message from the SQL Agent Job that is trying to run the snapshot.

    /*******************************************************

    2012-12-27 12:13:31.65 Source: Replication
    2012-12-27 12:13:31.65 Exception Type: Microsoft.SqlServer.Replication.ConnectionFailureException
    2012-12-27 12:13:31.65 Exception Message: The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following:  the client tried to connect to an unsupported version of SQL Server; the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.)
    2012-12-27 12:13:31.65 Message Code: 233
    2012-12-27 12:13:31.65  


    *********************************************************/

    Thoughts?

    Thanks,

    Nathan

     

All Replies

  • Thursday, December 27, 2012 7:34 PM
     
     
    Sign In to Vote
    0
    I believe you are using the SQL Server 2005 SSMS to configure replication. Connect to SQL Server 2012 SSMS and connect to the SQL Server 2005 instance and then configure the replication.
     
  • Thursday, December 27, 2012 8:38 PM
    Moderator
     
     
    Sign In to Vote
    0

    This does not look like a problem with replication, but rather a problem with the publisher. It sounds like it is overloaded.

    How many subscribers are there? It could be a resource issue.

    looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

     
  • Thursday, December 27, 2012 9:53 PM
     
     
    Sign In to Vote
    0

    This error is a generic "cannot connect to server".  Please check your server name.  

    Can you remote desktop into the 2005 server and use SSMS to connect to the 2012 server/instance?

     
  • Friday, December 28, 2012 12:29 PM
     
     Answered
    Sign In to Vote
    0

    Everyone,

    Thanks for the help.  

    As it turns out, I had to turn on named pipes in the publisher database (2005 instance) to resolve this.  I had to do this through SAC and restart the database instance.  

    Not sure why replication felt required to use named pipes and am not certain why I needed it on this server, when it wasn't on in my test environment.  

    Either way, it is working now.

    Thanks you everyone.

    Nathan.