Msmerge_genhistory problems

Hi,
I have 12 merge replications (1 Pub, 2 Subs) with remote distributor.
Recently all replications were failed. The error message is :
Cannot insert duplicate key row in object 'MSmerge_genhistory' with unique
index 'unc1MSmerge_genhistory'.
I investigated and discovered that the procedure sp_MsMakegeneration is
responsable for produce the error on line:
update dbo.MSmerge_genhistory set guidsrc = @.genguid, guidlocal = @.genguid,
coldate = @.dt where generation = @.gen
The problem is intermittent.
Error: 2601, Severity: 14, State: 3
Has anyone saw the same problem ?
Thanks
Rodrigo Varella
is this applicable?
http://support.microsoft.com/kb/276427/en-us
and how about
http://groups.google.com/group/microsoft.public.sqlserver.replication/msg/6f9a6ad3c148beef?dmode=source
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rodrigo Varella" <RodrigoVarella@.discussions.microsoft.com> wrote in
message news:B45D4DE6-B2F9-4B0E-BD89-9FF6A6B3DEA7@.microsoft.com...
> Hi,
> I have 12 merge replications (1 Pub, 2 Subs) with remote distributor.
> Recently all replications were failed. The error message is :
> Cannot insert duplicate key row in object 'MSmerge_genhistory' with unique
> index 'unc1MSmerge_genhistory'.
> I investigated and discovered that the procedure sp_MsMakegeneration is
> responsable for produce the error on line:
> update dbo.MSmerge_genhistory set guidsrc = @.genguid, guidlocal =
> @.genguid,
> coldate = @.dt where generation = @.gen
> The problem is intermittent.
> Error: 2601, Severity: 14, State: 3
> Has anyone saw the same problem ?
> Thanks
> Rodrigo Varella
>
>
|||Hi Hilary,
Thanks about the articles, but I had seem them before. My environment is
SQL 2000 full patched.
Rodrigo Varella
"Hilary Cotter" wrote:

> is this applicable?
> http://support.microsoft.com/kb/276427/en-us
> and how about
> http://groups.google.com/group/microsoft.public.sqlserver.replication/msg/6f9a6ad3c148beef?dmode=source
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Rodrigo Varella" <RodrigoVarella@.discussions.microsoft.com> wrote in
> message news:B45D4DE6-B2F9-4B0E-BD89-9FF6A6B3DEA7@.microsoft.com...
>
>
|||can you reinitialize and redistribute the snapshot to the subscribers?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rodrigo Varella" <RodrigoVarella@.discussions.microsoft.com> wrote in
message news:FCB2167B-556B-4642-BE3A-F7513044ACB4@.microsoft.com...[vbcol=seagreen]
> Hi Hilary,
> Thanks about the articles, but I had seem them before. My environment
> is
> SQL 2000 full patched.
> Rodrigo Varella
> "Hilary Cotter" wrote:
|||I also found this - it looks like its from a PSS incident.
http://www.gobrien.net/kb/sox/sox/01/11/28/X700048.txt
It suggests dropping the index.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rodrigo Varella" <RodrigoVarella@.discussions.microsoft.com> wrote in
message news:FCB2167B-556B-4642-BE3A-F7513044ACB4@.microsoft.com...[vbcol=seagreen]
> Hi Hilary,
> Thanks about the articles, but I had seem them before. My environment
> is
> SQL 2000 full patched.
> Rodrigo Varella
> "Hilary Cotter" wrote:
|||Hilary,
The procedure solves the problem!
Thank you!
Rodrigo Varella
"Hilary Cotter" wrote:

> I also found this - it looks like its from a PSS incident.
> http://www.gobrien.net/kb/sox/sox/01/11/28/X700048.txt
> It suggests dropping the index.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Rodrigo Varella" <RodrigoVarella@.discussions.microsoft.com> wrote in
> message news:FCB2167B-556B-4642-BE3A-F7513044ACB4@.microsoft.com...
>
>
|||I sometimes get this. I think it happens when you have an unreliable
environment - is this true in your case?. The fix is to run DBCC
DBREINDEX on the affected index.
Rodrigo Varella wrote:
> Hi,
> I have 12 merge replications (1 Pub, 2 Subs) with remote distributor.
> Recently all replications were failed. The error message is :
> Cannot insert duplicate key row in object 'MSmerge_genhistory' with unique
> index 'unc1MSmerge_genhistory'.
> I investigated and discovered that the procedure sp_MsMakegeneration is
> responsable for produce the error on line:
> update dbo.MSmerge_genhistory set guidsrc = @.genguid, guidlocal = @.genguid,
> coldate = @.dt where generation = @.gen
> The problem is intermittent.
> Error: 2601, Severity: 14, State: 3
> Has anyone saw the same problem ?
> Thanks
> Rodrigo Varella
>
>
|||I have more than 3.000 subscriptions and more than 100 publications. We have
used replications since 2000. We reindex all tables every day. I have never
seem this problem before. My enviroment is checked constantly. We discovered
the duplicate row in msmerge_genhistory using the snapshot procedure. I have
no idea the origin of the problem. It happened suddenly.
Rodrigo Varella
"JE" wrote:

> I sometimes get this. I think it happens when you have an unreliable
> environment - is this true in your case?. The fix is to run DBCC
> DBREINDEX on the affected index.
> Rodrigo Varella wrote:
>
|||I'm running inot the same problem, what was snapshot procedure you used to
resolve this? The link referenced is no longer viewable.
Thank you,
Pauly C
"Rodrigo Varella" wrote:
[vbcol=seagreen]
> I have more than 3.000 subscriptions and more than 100 publications. We have
> used replications since 2000. We reindex all tables every day. I have never
> seem this problem before. My enviroment is checked constantly. We discovered
> the duplicate row in msmerge_genhistory using the snapshot procedure. I have
> no idea the origin of the problem. It happened suddenly.
> Rodrigo Varella
> "JE" wrote: