How to run a snapshot when one or more tables belong to other publ

[José Luis]

Hi.
Trying to start the snapshot I got the following error: "The subscription
could not be initialized using an initial snapshot because one or more tables
in the subscription belong to another publication, and therefore cannot be
dropped" (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200976).

I could make the first server publication and replication with no problem.
When I try to replicate with other suscriptor it is when I got this error.
Regards, José

P.S. Running SQL Server 2005 enterprise edition with SP2 on Windows 2003
server. Merge replication.

[José Luis]

Post by José Luis
Hi.
Trying to start the snapshot I got the following error: "The subscription
could not be initialized using an initial snapshot because one or more tables
in the suscription belong to another publication, and therefore cannot be
dropped" (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200976).
I could make the first server publication and replication with no problem.
When I try to replicate with other suscriptor it is when I got this error.
Regards, José
P.S. Running SQL Server 2005 enterprise edition with SP2 on Windows 2003
server. Merge replication.

This post was finally solved by our technical team.

[José Luis]

This post was solved by our technical team. We found out that the error was
caused because the Merge System Tables of the suscriptors were corrupted. For
some reason that we do not know there was the information of previous
replications in the table. So when the replication occurred all that
information was brought to the main server which makes the publication with
those redundancy tables. The error message was according to what was
happening. Now it would help us to know if there is some way through
configuration that we could prevent that in the future. It looked like the
SQL wasn´t cleaning the system merge tables each time that we eliminated the
suscriptor.

Post by José Luis
Hi.
Trying to start the snapshot I got the following error: "The subscription
could not be initialized using an initial snapshot because one or more tables
in the suscription belong to another publication, and therefore cannot be
dropped" (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200976).
I could make the first server publication and replication with no problem.
When I try to replicate with other suscriptor it is when I got this error.
Regards, José
P.S. Running SQL Server 2005 enterprise edition with SP2 on Windows 2003
server. Merge replication.

[j***@gmail.com]

Post by José Luis
This post was solved by our technical team. We found out that the error was
caused because the Merge System Tables of the suscriptors were corrupted. For
some reason that we do not know there was the information of previous
replications in the table. So when the replication occurred all that
information was brought to the main server which makes the publication with
those redundancy tables. The error message was according to what was
happening. Now it would help us to know if there is some way through
configuration that we could prevent that in the future. It looked like the
SQL wasn´t cleaning the system merge tables each time that we eliminated the
suscriptor.

Hi, Can you explain in detail. I am also having the same issue. Tried recreating the publisher and subscriber again n again , but encountering the same issue. It would be great if you can help me

Post by José Luis

Post by José Luis
Hi.
Trying to start the snapshot I got the following error: "The subscription
could not be initialized using an initial snapshot because one or more tables
in the suscription belong to another publication, and therefore cannot be
dropped" (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200976).
I could make the first server publication and replication with no problem.
When I try to replicate with other suscriptor it is when I got this error.
Regards, José
P.S. Running SQL Server 2005 enterprise edition with SP2 on Windows 2003
server. Merge replication.