Where you able to deploy all other articles?
If so, it sounds like you have to re-initialize and then regenerate your
snapshot and distribute it again.
If not, you probably have an ftp error, where your subscriber can't find
your snapshot. Check your FTP settings and the security underneath your ftp
folder.
[quoted text, click to view] "DBA72" <anonymous@discussions.microsoft.com> wrote in message
news:482FFED1-5BF7-494A-A28B-0B767871762B@microsoft.com...
> I had perfectly fine replication environment where I was running merge
replication between one publisher/distributor and two pull subscriptions.
After making some change to the schema of the publication I now get the
following error.
[quoted text, click to view] >
> My initial thought was that this was a permissions problem when the
subscribers were trying to pull over the shapshot but even after the
snapshot was copied locally, I still got the error.
[quoted text, click to view] >
> Any ideas???
>
> The schema script
'\\VIVA-SQLHQ\C$\Viva\Snapshots\unc\VIVA-SQLHQ_VIS_VIS\20040331111236\tblApp
licantLeadSource_554.sch' could not be propagated to the subscriber.
[quoted text, click to view] > (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> --------------------------------------------------------------------------
-------------------------------------
> Could not find the cabinet file 'snapshot.cab' in folder
'\\VIVA-SQLHQ\C$\Viva\Snapshots\unc\VIVA-SQLHQ_VIS_VIS\20040331111236\'
> (Source: BOSERVER-CSC3 (Agent); Error number: 0)
> --------------------------------------------------------------------------
-------------------------------------
>