Merge Replication problem

Merge Replication problem

Post by Ron Lounsbur » Fri, 18 Apr 2003 03:48:04



We are in the process of setting up merge replication of portions of a
database between 2 servers.  We have identified the tables, manually created
the articles to ensure that there is no problem with foreign keys, and run
the replication script.  The script creates a snapshot agent and a merge
agent.  We manually run first the snapshot agent and then the merge agent.
The snapshot agent completes with 65 aritcles created.  The merge agent
seems to get through all tables (performing changes to the conflict
resolution, bulk copying the data, and applying the changes to triggers and
DRI), but then stops with the error below.  On subsequent attempts to run
the agent it fails immediatly with the same error.

Error data:
Last Command: {call sp_mergemetadataretentioncleanup(?, ?, ?)}

Error Message:

The merge process could not perform retention-based meta data cleanup in
database 'NITSS2KChkRep'.

Error Detail:

The merge process could not perform retention-based meta data cleanup in
database 'NITSS2KChkRep'.

(Source: Merge Replication Provider (Agent); Error number: -2147199467)

----------------------------------------------------------------------------
-----------------------------------

Could not find stored procedure 'sp_MScleanup_zeroartnick_genhistory'.

(Source: BootNet (Data source); Error number: 2812)

----------------------------------------------------------------------------
-----------------------------------

The sp_mergemetadataretentioncleanup stored proc exists on the server that
is pushing the replication (and public has exec permission), but it does not
exist on the reciepient server.  Can anyone tell me what is happening here
and how to fix it?

TIA

Ron Lounsbury

 
 
 

Merge Replication problem

Post by TSVK [MSFT » Sun, 20 Apr 2003 03:56:12


YOu should try rerunning replmerg.sql on your box to fix the problem.
Somehow this proc is missing.
I suspect you had a setup problem

--
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"

Quote:> We are in the process of setting up merge replication of portions of a
> database between 2 servers.  We have identified the tables, manually
created
> the articles to ensure that there is no problem with foreign keys, and run
> the replication script.  The script creates a snapshot agent and a merge
> agent.  We manually run first the snapshot agent and then the merge agent.
> The snapshot agent completes with 65 aritcles created.  The merge agent
> seems to get through all tables (performing changes to the conflict
> resolution, bulk copying the data, and applying the changes to triggers
and
> DRI), but then stops with the error below.  On subsequent attempts to run
> the agent it fails immediatly with the same error.

> Error data:
> Last Command: {call sp_mergemetadataretentioncleanup(?, ?, ?)}

> Error Message:

> The merge process could not perform retention-based meta data cleanup in
> database 'NITSS2KChkRep'.

> Error Detail:

> The merge process could not perform retention-based meta data cleanup in
> database 'NITSS2KChkRep'.

> (Source: Merge Replication Provider (Agent); Error number: -2147199467)

> --------------------------------------------------------------------------
--
> -----------------------------------

> Could not find stored procedure 'sp_MScleanup_zeroartnick_genhistory'.

> (Source: BootNet (Data source); Error number: 2812)

> --------------------------------------------------------------------------
--
> -----------------------------------

> The sp_mergemetadataretentioncleanup stored proc exists on the server that
> is pushing the replication (and public has exec permission), but it does
not
> exist on the reciepient server.  Can anyone tell me what is happening here
> and how to fix it?

> TIA

> Ron Lounsbury


 
 
 

Merge Replication problem

Post by Ron Lounsbur » Sun, 20 Apr 2003 04:45:46


TSVK
    Thanks for the response.  I think that that is essentially what we ended
up (the last few days are a bit of a blur <g>), but I do remember killing
and reinstalling SQL on the system.

Ron Lounsbury


> YOu should try rerunning replmerg.sql on your box to fix the problem.
> Somehow this proc is missing.
> I suspect you had a setup problem

> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> OR if you wish to include a script sample in your post please add "Use of
> included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm"


> > We are in the process of setting up merge replication of portions of a
> > database between 2 servers.  We have identified the tables, manually
> created
> > the articles to ensure that there is no problem with foreign keys, and
run
> > the replication script.  The script creates a snapshot agent and a merge
> > agent.  We manually run first the snapshot agent and then the merge
agent.
> > The snapshot agent completes with 65 aritcles created.  The merge agent
> > seems to get through all tables (performing changes to the conflict
> > resolution, bulk copying the data, and applying the changes to triggers
> and
> > DRI), but then stops with the error below.  On subsequent attempts to
run
> > the agent it fails immediatly with the same error.

> > Error data:
> > Last Command: {call sp_mergemetadataretentioncleanup(?, ?, ?)}

> > Error Message:

> > The merge process could not perform retention-based meta data cleanup in
> > database 'NITSS2KChkRep'.

> > Error Detail:

> > The merge process could not perform retention-based meta data cleanup in
> > database 'NITSS2KChkRep'.

> > (Source: Merge Replication Provider (Agent); Error number: -2147199467)

> --------------------------------------------------------------------------
> --
> > -----------------------------------

> > Could not find stored procedure 'sp_MScleanup_zeroartnick_genhistory'.

> > (Source: BootNet (Data source); Error number: 2812)

> --------------------------------------------------------------------------
> --
> > -----------------------------------

> > The sp_mergemetadataretentioncleanup stored proc exists on the server
that
> > is pushing the replication (and public has exec permission), but it does
> not
> > exist on the reciepient server.  Can anyone tell me what is happening
here
> > and how to fix it?

> > TIA

> > Ron Lounsbury

 
 
 

1. Merge replication problems

Hi.

I'm working with SP2 trying to do merge replication. I have one central
subscriber which pull subscriptions from three local databases. The three
local DB has some rows in some tables which has the same primary key as in
another local DB. This makes a conflict occur when trying to replicate the
three local DB into the subscriber. The first database works OK, but the
next one causes a violation on primary key constraint because a row has the
same primary key at the subscriber and in the local DB and the rowguid
differs.

I thought I could write a script to update the rowguid so the agent
understand that it's the same row, but I got the message that I couldn't
update rowguid. I also tried to delete rows if there was a primary key
conflict, but then I violated referential integrity.

Do you have any tips how I can get these three local DB into one DB
(subscriber) without violating primary or foreign key constraint ? Should i
write a script, make a stored procedure, is there an option in the wizards I
can choose....???

  Thanks in advance.

          / Erik Pettersson, Sweden

2. Q: Sybase IQ logon time

3. Merge Replication Problem

4. Btrieve in NW5 config problem

5. Triggers and retrieving values

6. Merge replication problem over internet

7. replication between MS-SQL server 2000 and MS-Access

8. SP2 and merge replication problem

9. Merge replication problem using SQL 7.0 to Access 2000

10. Merge Replication Problem

11. Merge Replication Problems

12. Please help with merge replication problem