Merge Replication SQL 7.0 1

[outback]

We are setting up Replication between our main office in Portland (where the distributor resides) and our office in California (where the publisher resides). We have registered to the CA server. We have gone through the wizard that sets up the distributor successfully and gone through the wizard that sets up publication and the articles on the publisher successfully.

The problem at hand is, when the initial snapshot runs for the first time down on the publisher, it generates the triggers and creates the schema and then errors out. The error we are getting is

Invalid object name 'sysmergepublications'

Although if you go to the database that we creating this merge publication for the 'sysmergepublications' table is there and it would appear all the correct data resides with in. Any help with problem would be very much appreciated.

Thanks in advanced

 

[JohnBates]

outback - I also use SQL Server 7's merge-replication.

Something puzzles me - you said that the Portland server is Distributor and CA is Publisher ? Did you intend to say that CA is Subscriber ? Because generally the Publisher and Distributor reside on the same server.....

I think you'll like what data replication can do for you once you get it stabilized. The only complaint/problem I have encountered concerns those pesky 'synchronization conflicts' that can occur from time to time and result in our losing 1 row of data. Seems to happen mostly when the servers are very busy and the replication to the alternate server has not had time to catch up.

good luck, John

 

[outback]

John,
Thanks for the response. Yes I did state the replication scenario right. The reason for the distributor residing up in Portland is because of having a centralized distributor, which will allow us to centrally manage multiple publishers from various locations
I know merge is the more complex of the replication scenarios, but what's puzziling to me is we can set up a snapshot replication and publish to a subscriber that also resides in Portland and have no problems what so ever.
Any further imput on the error at hand or information on when and how that particular table
( i,e sysmergepublications) is being called apon would be appreciated.

Thanks