all groups > sql server replication > march 2004 >
You're in the

sql server replication

group:

Schema script could not be propogated


Schema script could not be propogated DBA72
3/31/2004 4:56:06 AM
sql server replication:
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

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

Any ideas??

The schema script '\\VIVA-SQLHQ\C$\Viva\Snapshots\unc\VIVA-SQLHQ_VIS_VIS\20040331111236\tblApplicantLeadSource_554.sch' could not be propagated to the subscriber
(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
--------------------------------------------------------------------------------------------------------------
RE: Schema script could not be propogated Paul Ibison
3/31/2004 5:46:06 AM
Usually this is a permissions issue, but you say you have copied the files locally - I'm not sure what this means - did you log on as the agent's login on the subscriber then copy the files to the subscriber? If that worked then discard the following advice, but if you didn't do that, then my advice usually would be that in a pull subscription if you use a default share eg c$, the agent account must be a local administrator which it probably isn't here so try changing to a declared share; for the error above, the share becomes \\VIVA-SQLHQ\Repldata and is changed by entering distributor properties, publishers tab, publication ellipsis
Regards
Re: Schema script could not be propogated Hilary Cotter
3/31/2004 8:42:47 AM
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]
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]
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]
'\\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]

AddThis Social Bookmark Button