Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Replication / September 2006

Tip: Looking for answers? Try searching our database.

Merge replication failure

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Samuel Shulman - 29 Sep 2006 13:35 GMT
After working for about 30 minutes (delivering the snapshot) the replication
failed

I checked the Session details of the subscription and I found Action Message
saying the 'The process could not deliver the snapshot to the Subscriber.'

In the error information under Data Source I found the following message
'General network error. Check your network documentation.'

Checking the network log I got the following message: SQL Server Scheduled
Job 'SERVER\SERVER1-MRN1-MRN1_rep-XYZSERVER.ABC.LOCAL-12'
(0x97E3EAE1F1106144B16C808A6492CB9C) - Status: Failed - Invoked on:
2006-09-28 20:23:00 - Message: The job failed.  The Job was invoked by
Schedule 35 (Replication agent schedule.).  The last step to run was step 3
(Detect nonlogged agent shutdown.).

Any clue?

Samuel
Paul Ibison - 29 Sep 2006 14:07 GMT
Samuel,
what happens if you restart the agent - normally this'll solve a network
outage.
    Cheers,
         Paul Ibison SQL Server MVP, www.replicationanswers.com .
Samuel Shulman - 29 Sep 2006 15:48 GMT
It happens consistantly during the initial stage when the entire database
was replicated

> Samuel,
> what happens if you restart the agent - normally this'll solve a network
> outage.
>     Cheers,
>          Paul Ibison SQL Server MVP, www.replicationanswers.com .
Paul Ibison - 29 Sep 2006 16:40 GMT
Samuel,
I'd enable logging to see if this gets more info
(http://support.microsoft.com/?id=312292), especially if the failure is at
the same point each time. Otherwise I'd look at monitoring the network for
outages - network connectivity problems.
    Cheers,
         Paul Ibison SQL Server MVP, www.replicationanswers.com .
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.