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

Stairway to SQL Server Replication - Level 10: Troubleshooting Expand / Collapse
Author
Message
Posted Wednesday, July 20, 2011 6:14 AM


Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, August 09, 2011 7:01 AM
Points: 15, Visits: 36
Comments posted to this topic are about the item Stairway to SQL Server Replication - Level 10: Troubleshooting
Post #1144894
Posted Friday, April 20, 2012 1:51 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, February 07, 2013 11:21 AM
Points: 13, Visits: 104
Hi,

We have transactional replication setup which replicates data from server A (SQL 2008 SP2) to Server B (SQL 2005 SP2) to Server C ( SQL 2008 RTM).

These days specially after we migrated server A and Server C to SQL 2008 from 2005, I am getting error 'Initial snapshot for the publication/artice is not yet available' Even thought the snapshot agent ran 100% and the replication was stable for 2-3 days. I get error at later point may be after 4-5 days.

I don't know what could cause this issue. Can you please help?

Thanks,
Post #1287473
Posted Saturday, April 21, 2012 8:32 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, February 07, 2013 11:21 AM
Points: 13, Visits: 104
What was that? Be serious and reply approriately if you know the answer
Post #1287699
Posted Sunday, June 10, 2012 7:39 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: 2 days ago @ 8:12 AM
Points: 1,833, Visits: 731
Have you checked the read/write permissions for the post migration snapshot folder?

qh


SQL 2K acts like a spoilt child - you need to coax it round with lollipops.
Post #1313585
Posted Thursday, December 27, 2012 5:51 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Yesterday @ 6:51 PM
Points: 727, Visits: 1,393
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
Post #1400581
Posted Thursday, December 27, 2012 8:39 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: 2 days ago @ 8:12 AM
Points: 1,833, Visits: 731
1. It may not be possible to replicate from 2005 to 2012 (off hand I don't know this) you may need to have the 2005 server at SP4?
2. The size of the publication articles or possibly only one of them could be larger than 2GB - this can cause issues.

If so, you may have to perform a backup of publication database(s) then restore on subscriber server, then "reinitialize without snapshot".

Looking at the error text it may be no 1.

Good luck

qh


SQL 2K acts like a spoilt child - you need to coax it round with lollipops.
Post #1400643
Posted Thursday, December 27, 2012 9:00 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Yesterday @ 6:51 PM
Points: 727, Visits: 1,393
quackhandle1975 (12/27/2012)
1. It may not be possible to replicate from 2005 to 2012 (off hand I don't know this) you may need to have the 2005 server at SP4?
2. The size of the publication articles or possibly only one of them could be larger than 2GB - this can cause issues.

If so, you may have to perform a backup of publication database(s) then restore on subscriber server, then "reinitialize without snapshot".

Looking at the error text it may be no 1.

Good luck

qh


1) tested already between a 2005 SP4 install and the 2012 BI edition. It can be done.
2) Even doing a single table with 2 records in it isn't working. So size isn't the issue.

Interesting to note that it appears that the log reader is working (at least the logs say it is as I haven't setup the subscription since there isn't a snapshot to base it off of
)
Post #1400657
Posted Thursday, December 27, 2012 9:27 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: 2 days ago @ 8:12 AM
Points: 1,833, Visits: 731
Sounds obvious, but did you check Named Pipes settings? Or is that a typical SQL Server "red herring" error and nothing to do with NP at all?

qh


SQL 2K acts like a spoilt child - you need to coax it round with lollipops.
Post #1400674
Posted Thursday, December 27, 2012 9:37 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Yesterday @ 6:51 PM
Points: 727, Visits: 1,393
quackhandle1975 (12/27/2012)
Sounds obvious, but did you check Named Pipes settings? Or is that a typical SQL Server "red herring" error and nothing to do with NP at all?

qh

I think it is a red herring. As near as I can tell, the "test" and "prod" 2005 boxes are setup exactly the same regarding tcp/ip, named pipes, etc. I haven't changed anything on the 2012 box.

Fraggle
Post #1400681
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse