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 / December 2005

Tip: Looking for answers? Try searching our database.

The process could not deliver the snapshot to the Subscriber

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Shehab Kamal - 27 Dec 2005 11:55 GMT
I had a merge replication running between a publisher/distributer and 4
subscribers. Every thing was going well until I decided to reinitialize the
subscriptions, this was due to changing some stored proedures at the
publisher and I wanted them to be replicated to all other subscribers.
After reinitializing the following error is displayed by each merge agent
"The process could not deliver the snapshot to the Subscriber". After tracing
the agent session details I found that the agent has connected to the
subscriber and applied some scripts until this error appeared "the step was
cancelled as a result of a stop job request".
Has the error something to do with the size of the snapshot, i.e. the
snapshot is large so that the process timesout? If so, how can I increase the
timeout for the transfer of the snapshot agent?
Other questions:
1) Does the size of the snapshot equal the size of the ReplData folder?
2) If I can backup and restore the database at each subscriber, Do I need
the snapshot to be copied, i.e. the subscriber has the schema?
Sincerely,
Shehab.
Hilary Cotter - 29 Dec 2005 03:18 GMT
It could, you would need to enable logging to tell for sure. You should not
have to set the timeout for the snapshot agent, but it is an agent parameter
called querytimeout.

1) ReplData could contain the snapshots of many publications/subscriptions.
So if you have one publication and subscription ReplData would be the size
of your snapshot.
2) No, but I would use the copy subscription database method as it is the
most efficient way to do this.

Signature

Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

>I had a merge replication running between a publisher/distributer and 4
> subscribers. Every thing was going well until I decided to reinitialize
[quoted text clipped - 18 lines]
> Sincerely,
> Shehab.
Shehab Kamal - 29 Dec 2005 08:03 GMT
Thanks for the 3 answers, but can you tell me what are the possible causes of
such an error "The process could not deliver the snapshot to the Subscriber"
and the most likely solution.

> It could, you would need to enable logging to tell for sure. You should not
> have to set the timeout for the snapshot agent, but it is an agent parameter
[quoted text clipped - 28 lines]
> > Sincerely,
> > Shehab.
 
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.