"Shehab Kamal" <ShehabKamal@discussions.microsoft.com> wrote in message
news:8F7D11A3-1957-4266-957A-F6A3A46680E7@microsoft.com...
>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" wrote:

> 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.
>
> --
> 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
>
> "Shehab Kamal" <ShehabKamal@discussions.microsoft.com> wrote in message
> news:8F7D11A3-1957-4266-957A-F6A3A46680E7@microsoft.com...
> >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.
>
>