Skip to main content
       
Upgrade and Migration
 
   
Go Search
 
Upgrade and Migration > Questions and Answers  

Questions and Answers

Modify settings and columns
  
View: 
Sort by AttachmentsUse SHIFT+ENTER to open the menu (new window).
Question DetailsFilter
Product
AnswerFilter
How To: Solve the error - 'Upgrade conflict has occured' error during gradual upgradeUse SHIFT+ENTER to open the menu (new window).

 

SPS 2003; MOSS 2007

When you upgrade SPS 2003 to SPS 2007 RTM and choose gradual upgrade method with manual database name selection in the new content database that should hold upgraded V3 sites, you get the error;

================================

An update conflict has occurred, and you must re-try this action. The object SPWebApplication Name=WebSiteName_Pair Parent=SPWebService is being updated by DOMAIN\ACCOUNT, in the OWSTIMER process, on machine SERVER.  View the tracing log for more information about the conflict.
================================

This happens if you select the check box - 'Manual database' and provide a name which doesn't contain the string '_Pair ' at the end of it.  You can try providig a name with _Pair and this may work.  If not, run the configuration wizard again, disconnect from the existing cnfig db and re-run the wizard to create a new config db and then do the gradual upgrade.

Is it possible to upgrade directly from WSS 2.0 to MOSS 2007?Use SHIFT+ENTER to open the menu (new window).
WSS 2.0; MOSS 2007
Users must first upgrade from WSS 2.0 to WSS 3.0; then upgrade from WSS 3.0 to MOSS 2007.
Is it possible to move a test environment into production without rebuilding?Use SHIFT+ENTER to open the menu (new window).
MOSS 2007
There is a content deployment feature which allows information stored in a content database to be deployed across domains; deployment of configuration information across domains is not supported.
 
About Us Contact Us