Master Data Services, Error 2601 when pressing "Add Member"

  • I am getting the following error in MDS when clicking the "Add Member" button:

    2601: Cannot insert duplicate key row in object 'mdm.tbl_2_30_EN' with unique index 'ux_tbl_2_30_EN_Version_ID_Code'. The duplicate key value is (2, 106229).

    We were not having any issues publishing to this entity before. Now, all of a sudden, this error is popping up.

    Does anybody have any ideas why this would start happening all of a sudden?

  • Never really found out why this error started occurring all of a sudden. I was able to fix it though. I had to go into the MDS database and perform a hard delete on the last ten or so rows of data that had been published to the entity that was returning the error.

    I was then able to publish those ten rows of data again without running into the error. Somehow an index, or something, got corrupted and SQL Server was trying to give the next row of data the same unique ID that a previously published row was given.

    I'm just glad that it was only ten recently published members that I had to delete, and not a much bigger problem.

  • acapone (9/12/2014)


    Never really found out why this error started occurring all of a sudden. I was able to fix it though. I had to go into the MDS database and perform a hard delete on the last ten or so rows of data that had been published to the entity that was returning the error.

    I was then able to publish those ten rows of data again without running into the error. Somehow an index, or something, got corrupted and SQL Server was trying to give the next row of data the same unique ID that a previously published row was given.

    I'm just glad that it was only ten recently published members that I had to delete, and not a much bigger problem.

    Hi Acapone,

    We are having similar error under MDS. My question is, how did you identified 10 records to delete from the MDS database?

    Thank you,

    HP

Viewing 3 posts - 1 through 2 (of 2 total)

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