December 27, 2012 at 5:54 am
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,
Fraggle
December 27, 2012 at 9:44 am
What does this say when run against the Publisher, the Distributor and the Subscriber:
SELECT SERVERPROPERTY('Edition') AS Edition,
SERVERPROPERTY('ProductVersion') AS ProductVersion,
SERVERPROPERTY('ProductLevel') AS ProductLevel;
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
December 27, 2012 at 11:07 am
opc.three (12/27/2012)
What does this say when run against the Publisher, the Distributor and the Subscriber:
SELECT SERVERPROPERTY('Edition') AS Edition,SERVERPROPERTY('ProductVersion') AS ProductVersion,
SERVERPROPERTY('ProductLevel') AS ProductLevel;
PUblisher:
Standard Edition (64-bit)9.00.5000.00SP4
Distributor and Subscriber:
Business Intelligence Edition (64-bit)11.0.3000.0SP1
December 28, 2012 at 5:25 am
Alright, so apparently named pipes wasn't a red herring. It was the issue. My apologies for the confusion on that. Turned on Named Pipes in SAC, restarted the database system, and voila, snapshot starts to work without issue.
Thanks everyone for trying to help.
Fraggle
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply