View Complete Post
I have a publication on SQL Server 2008 Standard Edition using merge replication. When I attempt to generate the initial snapshot, the snapshot agent appears to hang on the step "Setting up the publication for filtered articles." I
get a long (over 4 hour) series of messages: "The process is running and is waiting for a response from the server." I know something is happening server-side, as SQL Server and the snapshot agent use a lot of memory and max out one core's
This has me confused as the publication is not doing any filtering.
Even more confusing: I backed up the database and restored it onto my development-test system. I created the snapshot there, and it took under 10 minutes every time.
Any suggestions for investigating and resolving this?
Have I correctly understood that a snapshot is only required in a merge replication (pull) when the subscription is first created or reinitialized?
And that the publisher is re-generating those snapshots on some schedule, only to speed up to process if some subscribers need to be reinitialized?
I'm asking this because I intend to download the snapshot via ftp manually (inorder to use passive FTP-SSL, merge replication itself only supports active FTP). Since the MergeSubscriptionAgent.IsSnapshotRequired() method takes ages to return a result
(more than a minute ove local LAN), I'd like to skip that part and simply go ahead and download the snapshot when the subscription has not been created or is marked for reinitialization.
I need answers to the questions above, so that if I go down this route -> a couple of weeks in production I wouldn't run into trouble, because SQL requires a new snapshot to say validate data or something...
Here is the complete scenario :- SBS 2003 running Sql Server 2005 Standard, Merge Replication and Push Subscription. Connection Via VPN. Subscribers are SQL SERVER 2005 express..
Sometimes due to some structural changes, snapshot is to be re-applied. This is rare but is possible in our case.. On some subscribers snapshot applying goes on for hours and days with no sucess.
Are there any step by step instructions on how we can reintialize or reapply the snapshot on those subscribers manually i.e. maybe by copying the replication folder manually to subscriber and applying manually..
I've searched far and wide, and so far have not been able to find any reference to this issue.
There is a merge replication setup on a SQL 2008 server, setup to replicate to SQL 2008 Express edition. We have similar setups in SQL 2005 AND SQL 2008 without issues. The setup is that the current merge replication snapshot file location is
\\<ServerName>\Repldata\UNC\<SERVER_PUBLICATION>\20101229112828 which represents the file location of the latest snapshot which was just generated due to an obsolete snapshot.
The issue comes in when attempting to replicate against the server. The replication says that the schema script could not be propogated to the subscriber. Under normal circumstances I would say it's due to security issues with being able to read to the above
folder, however this is not the case. The additional error that comes up is stating that it could not read the file along with an OS error 3 (The system cannot find the path specified).
What is unique about this, is that the subscriber is trying to download the snapshot from an old and now non-existent snapshot folder. Here is an copy of the error, noting the file location of "20091121130613" which no longer exists and is from an old snapshot.