Cannot insert duplicate key row in object 'sysmergeschemachange' with unique index 'schemachangeversion'.

Question

Cannot insert duplicate key row in object 'sysmergeschemachange' with unique index 'schemachangeversion'.

marcos jose

Old Hand

Points: 309
More actions
October 13, 2008 at 8:41 am

#94071

Hi,
Happened a problem that I don´t know the solution.
Look at this:
The process could not deliver the snapshot to the Subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
---------------------------------------------------------------------------------------------------------------
The process could not connect to Subscriber 'PVALDEVINO'.
(Source: PVALDEVINO (Agent); Error number: 20084)
---------------------------------------------------------------------------------------------------------------
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
(Source: PVALDEVINO (Data source); Error number: 18452)
---------------------------------------------------------------------------------------------------------------
I used dbcc checktable and dbcc dbrebuild, and even then select in the table, but nothing.
Anybody help me?

Viewing 14 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic. Login to reply

marcos jose Old Hand Points: 309 More actions · Answer 1

I really need help...

I think it is dirty database. I did upgrade in distribution and publisher. Sql server 7 to Sql server 2000. I disable all replication e able again in sql server 2000, but the subscribers are still sql server 7.

And now, this is only publication.

I executed the procedure sp_removedbreplication and didn't do.

Anybody know how use verboselevel.

Thanks again.

nary SSCrazy Points: 2869 More actions · Answer 2

your Subscriber should be equal or have to have higher version than Publisher so if your Publisher Server is 2000 then Subscriber should also be atlease 2000 not 7.0

marcos jose Old Hand Points: 309 More actions · Answer 3

Hi. Thanks for help.

The microsoft don't desagree to use publisher with sql server 2000 and subscribers 7 or 2000. Then had have the last Service Pack and we had clients with enviroment.

Jeff Moden SSC Guru Points: 1004441 More actions · Answer 4

So, try to manuall login to the subscriber machine using PVALDEVINO and see what happens.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

marcos jose Old Hand Points: 309 More actions · Answer 5

Ok. I did what you say. The same error happened. Yesterday I executed SP4 again. Don't change nothing...

The tables sysmergeschemachange, sysmergepublications, sysarticles and sysmergesubscriptios are working fine. then are same the good subscribers.

How I use OutputVerboseLevel?

Today we going to do a new database. If don

marcos jose Old Hand Points: 309 More actions · Answer 6

Ok. I did what you say. The same error happened. Yesterday I executed SP4 again. Don't change nothing...

The tables sysmergeschemachange, sysmergepublications, sysarticles and sysmergesubscriptios are working fine. then are same the good subscribers.

How I use OutputVerboseLevel?

Today we going to do a new database. If don't do, is the end...

Thanks.

marcos jose Old Hand Points: 309 More actions · Answer 7

And a new day born...

The error message complete.

The process could not deliver the snapshot to the Subscriber.

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

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

Cannot insert duplicate key row in object 'sysmergeschemachange' with unique index 'schemachangeversion'.

(Source: PVALDEVINO (Data source); Error number: 2601)

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

RAISERROR failed due to invalid parameter substitution(s) for error 20001, severity 16, state 1.

(Source: PVALDEVINO (Data source); Error number: 2757)

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

Well. That simple. Delete the duplicate key. But the duplicated is happining because it try send snapshot again and not insert, deletes and updates. Do you see?

Why?

Jeff Moden SSC Guru Points: 1004441 More actions · Answer 8

At this point, I agree... something is "dirty" in the data... my recommendation would be to delete the data at the subscriber and do a fresh snapshotl.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

marcos jose Old Hand Points: 309 More actions · Answer 9

Hi Doctor...

Yesterday, before I see your post, I tried another and last solution. Exactly watch you said. I droped subscribers, take off sql server 7 and put sql server 2000 with a new database.

When I starting the agent, everything worked.

Today I begging to change the others subscribers to sql server 2000.

Thanks a lot.

Jeff Moden SSC Guru Points: 1004441 More actions · Answer 10

It's not the change from SQL Server 7 to 2000 that did it. It's the fact that you had to do a new snapshot to make it work in 2000, just like I said.

Although I agree that upgrading from SQL Server 7 is a good idea, it is not necessary in this case. And, I wouldn't waste the time to upgrade to SQL Server 2000... after all, it's almost 9 years old and SQL Server 2008 is the berries compared to 2000.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

marcos jose Old Hand Points: 309 More actions · Answer 11

Hum...

But wasn´t wasted of time because I had have make a new snapshot, many times...

I believe that if I just droped database and recreated, worked very well, and, why not change to sql server 2000?

Jeff Moden SSC Guru Points: 1004441 More actions · Answer 12

marcos jose (10/18/2008)
... and, why not change to sql server 2000?

Heh... Why not change to 2k5 or 2k8?

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

marcos jose Old Hand Points: 309 More actions · Answer 13

Good question.

The software house don't allow yet. They are testing yours T-sql for sql2k5.