Microsoft Knowledge Base Email Alertz

Error message when you try to upgrade from Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0 or to SharePoint Server 2007: Violation of UNIQUE KEY constraint 'AllUserData_Url'

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 937290 - Last Review: May 31, 2007 - Revision: 2.1

Error message when you try to upgrade from Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0: "Violation of UNIQUE KEY constraint 'AllUserData_Url'"

On This Page

SYMPTOMS

When you try to upgrade from Microsoft Windows SharePoint Services 2.0 to Microsoft Windows SharePoint Services 3.0, you receive the following error message:
Violation of UNIQUE KEY constraint 'AllUserData_Url'. Cannot insert duplicate key in object 'dbo.AllUserData'.

CAUSE

This issue occurs when the Windows SharePoint Services 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.

RESOLUTION

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. To do this, follow these steps, as appropriate for your situation.

SharePoint Designer 2007

  1. In SharePoint Designer 2007, click File, and then click Open Site.
  2. In the Open Site dialog box, click the Windows SharePoint Services 2.0 Web site that includes the discussion boards that have similar names.
  3. In the details pane, double-click Lists.
  4. Right-click the discussion board that you want to rename, click Rename, and then type a descriptive name for the discussion board, such as Technical Discussion or Planning Discussion.
  5. Rename all the discussion boards that have similar names, and then try to upgrade from Windows SharePoint Services 2.0.

FrontPage 2003

  1. In FrontPage 2003, click File, and then click Open Site.
  2. In the Open Site dialog box, click the Windows SharePoint Services 2.0 Web site that includes the discussion boards that have similar names.
  3. In the details pane, double-click Lists.
  4. Right-click the discussion board that you want to rename, click Rename, and then type a descriptive name for the discussion board, such as Technical Discussion or Planning Discussion.
  5. Rename all the discussion boards that have similar names, and then try to upgrade from Windows SharePoint Services 2.0.

APPLIES TO
  • Microsoft Windows SharePoint Services 3.0
Keywords: 
kbtshoot kbexpertiseinter kbprb KB937290
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Gary Ghotra - gs NOSPAM-AT-NOSPAM pherasl.com Report As Irrelevant  
Written: 9/4/2007 11:57 AM
We are facing same issues and tried to replicate the same in smaller env to find out what is best way other than distrubing end users for change. But guess it works and I have discussion board with what mentioned here as similiar names discussion board1,discussion board2,... Problem still exists in production envrionment and it is confusing to say if something works in test doesn't works in production.

asad Report As Irrelevant  
Written: 11/11/2008 10:28 PM
that's a great post. Really it helped me.