locked
Migrating SBS 2003 to SBS 2011 - SharePoint Services 3.0 SP2 installed on SBS 2003 in-place upgrade rather than side-by-side in error RRS feed

  • Question

  • During a Windows Small Business Server 2011 Standard from Windows Small Business Server 2003 migration, following the V 11.10.04 procedure, an error was made during the Move the internal website for Windows SBS 2011 Standard migration step (page 51; or http://technet.microsoft.com/en-us/library/gg563792.aspx#BKMK_InstallWindowsSharePointServices3 ). 

    During installation of Windows SharePoint Services 3.0 Service Pack 2 on the Source Server, on the Upgrade tab, In-place-upgrade was chosen instead of side-by-side installation in error.  The installation compted successfully, however, the SharePoint Products and Technologies Configuration Wizard failed, noting that "Completed configuration settings will not be rolled back."  An exception of the type

    Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException

    was thrown.  Here's the full description from the Application Log error 104.

    Failed to initialize SharePoint Products and Technologies upgrade.

    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: The pre-upgrade scan tool has not yet been run successfully on all content databases in the server farm. The pre-upgrade scan tool must complete without errors before you can continue with the upgrade process. The pre-upgrade scan tool is available in the following location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin\prescan.exe. Before you can upgrade you must run the pre-upgrade scan tool against your existing Web sites. If you are performing an inplace or gradual upgrade you can run the pre-upgrade scan tool on this server now. If you are attaching a database from a previous version environment, you will need to run this tool on the previous version environment with this database attached before attempting to reconnect this database.

    Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.

       at Microsoft.SharePoint.PostSetupConfiguration.InitializeTask.PrepareForUpgrade()

       at Microsoft.SharePoint.PostSetupConfiguration.InitializeTask.Run()

       at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

    Here's the full description from the related Application Log error 100.

    Configuration of SharePoint Products and Technologies failed.  Configuration must be performed in order for this product to operate properly.  To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_8_27_2012_1_57_59_633_1820008950.log, fix the problem, and run this configuration wizard again.

    The Add or Remove Programs panel shows that Microsoft wiudnows SharePoint Services 2.0 (with two updates) is still installed and Microsoft Windows SharePoint Services 3.0 is also listed (with the SP2 update). 

    My inclination is to first remove Microsoft Windows SharePoint Services 3.0 then reinstall selecting the "No, do not upgrade at this time" option on the Upgrade tab, however, I don't want to dig myself in deeper.

    So, looking for best forward path to undo the boo-boo and get the migration back on track.  Thanks for your help.

    Monday, August 27, 2012 8:19 PM

Answers

  • The short answer is, yes, uninstallation and reinstallation (not upgrade) worked.

    Removed Microsoft Windows SharePoint Services 3.0 from the source server via the Add or Remove Programs panel, which took at ca. 11 minutes to complete successfully.  CompanyWeb is still functional on the source server.  Restart.  CompanyWeb is still functional.  Confirm removal of Microsoft Windows SharePoint Services 3.0 via the Add or Remove Programs panel: yes, it’s absent.  Check Event Logs for anything horrifying: looks OK.  Run the Microsoft Windows SharePoint Services 3.0 installation again, this time selecting the “No, do not upgrade at this time” option.  The installation completed successfully, then ran the SharePoint Products and Technologies Configuration Wizard which reported “Configuration Successful”.  Complete the migration of the CompanyWeb content to 2011 without issue.  WSUS seems to be working fine as well.

    • Marked as answer by Dave Hamm Tuesday, August 28, 2012 5:05 AM
    Tuesday, August 28, 2012 5:05 AM