WSS 2.0 Upgrade To WSS 3.0 Failed With Violation of UNIQUE KEY constraint 'AllUserData_Url'
WSS 2.0 Upgrade To WSS 3.0 Failed With Violation of UNIQUE KEY constraint 'AllUserData_Url'
Couple of days a ago I had a very strange problem performing full upgrade from TFS 2005 to TFS 2010, the TFS upgrade went just fine but the WSS upgrade from 2 to 3 throws many couple of wired errors.
The WSS 2.0 to WSS 3.0 upgrade suppose to be “easy”, but this time I was though I got to a dead-end:
- WSS 2.0 Prescan –> Scan finished without failure.
- Installed WSS 3.0 and choose to perform Upgrade.
- Configuration \ Upgrade Failed.
After a deep dive in couple of upgrade logs I found the following error:
[SPContentDatabaseSequence] [ERROR] [9/13/2010 1:43:45 PM]: Action 3.0.87.0 of Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence failed.
[SPContentDatabaseSequence] [ERROR] [9/13/2010 1:43:45 PM]: Violation of UNIQUE KEY constraint 'AllUserData_Url'. Cannot insert duplicate key in object 'dbo.AllUserData'.
The statement has been terminated.
Violation of UNIQUE KEY constraint 'AllUserData_Url'. Cannot insert duplicate key in object 'dbo.AllUserData'.
This issue occurs when the WSS 2.0 site content includes discussion boards that have similar names.
For example, this issue occurs when the names of the discussion boards are Discussion Board1, Discussion Board2, and Discussion Board3.
In this case, the upgrade process cannot determine the unique name of each discussion board because the names of the discussion boards are similar.
To resolve this issue, use Microsoft Office SharePoint Designer 2007 or Microsoft Office FrontPage 2003 to rename the discussion boards before you try to upgrade from Windows SharePoint Services 2.0.
*** The discussion board names may looks completely different from WSS, but the real name will only revel him self using SharePoint Designer and front page. ***
Hope this helps.