"Michael Hotek" <mhotek@nomail.com> wrote in message
news:er$z3OmLEHA.1388@TK2MSFTNGP09.phx.gbl...
> Is the error message occuring on the newly added tables or on already
> existing tables? In the script that you ran to create the new tables, did
> you have the rowguid column in the table and were all of the properties
set
> correctly?
>
> --
> Mike
> Principal Mentor
> Solid Quality Learning
> "More than just Training"
> SQL Server MVP
> http://www.solidqualitylearning.com
> http://www.mssqlserver.com
>
>

"Paul Kleynhans" <paul@synaxon.co.za> wrote in message
news:%23nBlViiLEHA.3052@TK2MSFTNGP12.phx.gbl...
> Hi
> I've been running Merge replication successfully now for about 6 months.
We
> use Pull subscriptions and Dynamic Snapshots with FTP over telephone
lines.
>
> Recently, we upgraded our software that runs on the database, resulting in
2
> new tables added to the published article list.I added these to the
> publication using Enterprise manager and recreated our snapshot.
>
> This resulted in all our subscriptions (100 of them) falling over with the
> following error message:
> Connecting to ftp site 'SERVER1'
> (Source: MARIAAN\CC (Agent); Error number: 20116)
> --------------------------------------------------------------------------
--
> -----------------------------------
> Table 'C_ClaimStatus' does not exist in the Subscriber database.
> (Source: MARIAAN\CC (Data source); Error number: 21078)
> --------------------------------------------------------------------------
--
> -----------------------------------
> '. Check sysobjects.
> (Source: MARIAAN\CC (Data source); Error number: 2501)
> --------------------------------------------------------------------------
--
> -----------------------------------
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> --------------------------------------------------------------------------
--
> -----------------------------------
>
> I added a script to be run pre synchronisation that creates the missing
> tables (I thought replication should've created them automatically, but
what
> can you do?)
> After this ran, the tables existed at the sites, but the error changed to
> the following:
> Invalid column name 'rowguidcol'.
> (Source: GAELEEN_PC\CC (Data source); Error number: 207)
> --------------------------------------------------------------------------
--
> -----------------------------------
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> --------------------------------------------------------------------------
--
> -----------------------------------
>
> This happens immediately after the process "Bulk copied data into table
> 'sysmergesubsetfilters' (11 rows)"
>
> What is wrong? I've tried the microsoft sites, but came up empty. ANY help
> would be appreciated.
> We can NOT afford to go to 100 sites to re-install replication AGAIN...
>
> Regards
> Paul Kleynhans
>
>
>

"Paul Kleynhans" <paul@synaxon.co.za> wrote in message
news:%23Sc9S$mMEHA.3404@TK2MSFTNGP10.phx.gbl...
> I've finally solved my problem.
> I had to build a "remote scripting" tool into my software.
> This allowed me to manually recreate the new tables at the subscribers.
Once
> I did this, the problem was solved.
>
> This does mean, however, that Dynamic snapshot is not reliable when it
comes
> to table changes or additions...
>
> I would redo the entire structure, but I've done that twice already, and
> with 100 sites, it just isn't feasable anymore.
>
>