In setting up replication, I ran across this issue:

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 dev. 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? I didn't see it in the list of troubleshoot items.

Thanks,

Fraggle