Microsoft KB Archive/936915

= Error message when you try to upgrade to Windows Small Business Server 2003 R2: &quot;Setup was interrupted because of either user intervention or an unexpected error&quot; =

Article ID: 936915

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Windows Small Business Server 2003 R2 Premium Edition
 * Microsoft Windows Small Business Server 2003 R2 Standard Edition
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
You try to upgrade one of the following configurations to Microsoft Windows Small Business Server 2003 (Windows SBS) R2:
 * A Microsoft Windows Small Business Server 2000-based domain controller that is also running Microsoft Windows Server 2003 R2
 * A Windows Server 2003 R2-based domain controller

However, the upgrade is not successful, and you receive the following error message in the Component Messages dialog box:

Setup was interrupted because of either user intervention or an unexpected error. Rerun Setup to continue.

Additionally, an error message that resembles the following is logged in the Eventlog.txt file:

Windows Small Business Server 2003: The path to the .ini file:

Windows Small Business Server 2003: d:\i386\schema.ini

Windows Small Business Server 2003: Schema version in the .ini file

Windows Small Business Server 2003: 30

Windows Small Business Server 2003: Local Schema Version

Windows Small Business Server 2003: 31

Windows Small Business Server 2003: CWin2KSetupComponent::IsSchemaMatch find un-match schema

Windows Small Business Server 2003: Schema did not update as expected. Erroring out.

The Eventlog.txt file is located in the &quot;Documents and Settings\Administrator\Local Settings\Temp&quot; folder.



CAUSE
This problem occurs when you install Windows Server 2003 R2 before you upgrade to Windows SBS R2. This problem occurs because the Windows Server 2003 R2 Setup program upgrades the local schema registry value to version 31. However, when you try to upgrade to Windows SBS R2, the Windows SBS R2 Setup program tries to determine whether the local schema version registry value has been upgraded to version 30 for Windows Server 2003. Because the local schema version registry values do not match, the upgrade is not completed successfully.



RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, follow these steps.

Note If you are upgrading a Windows Small Business Server 2000-based computer to Windows SBS R2, go to step 8.  Use an account that has administrative credentials to log on to the Windows Server 2003 R2-based computer. Click Start, and then click Control Panel. In Control Panel, double-click Add or Remove Programs. In Add or Remove Programs, click Add/Remove Windows Components. In the Windows Components Wizard dialog box, locate the following components to see whether they are installed. If an item is selected in the Windows Components Wizard, it has already been installed. You must uninstall selected components and subcomponents before you can upgrade to Windows SBS R2. To locate a Windows subcomponent, click a Windows top-level component, and then click Details to view the subcomponents.

Note The Terminal Server component is not a Windows Server 2003 R2 optional component. However, it is included in this list because a computer that has Terminal Server installed cannot be successfully upgraded to Windows SBS 2003 R2. Click to clear the check box next to the components that you want to uninstall, click Next, and then follow the instructions in the Windows Components Wizard when you are prompted.</li> After the Windows Components Wizard is finished, click Finish.</li> Modify the schema version in the registry. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> Click Start, click Run, type regedit, and then click OK.</li> Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/NTDS/Parameters

</li> Right-click Schema Version, and then click Modify.</li> In the Edit DWORD Value dialog box, click Decimal, and then type 30 in the Value data box.</li> Exit Registry Editor.</li></ol> </li> Rerun the Windows SBS 2003 R2 upgrade.</li> After the upgrade is finished and after the server restarts, you may receive the following activation message when you log on to the computer:

Windows Product Activation

This copy of Windows must be activated with Microsoft before you can continue. You cannot log on until you activate Windows. Do you want to activate Windows now?

To shut down the computer, click Cancel

If you receive this message, see the following Microsoft Knowledge Base article:

932442 Error message after you install the Windows Small Business Server 2003 Transition Pack: &quot;This copy of Windows must be activated with Microsoft before you can continue&quot;

</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
If you receive the following error message when you open any Microsoft Management Console (MMC) snap-ins, you may have to upgrade to MMC 3.0:

Microsoft Management Console MMC cannot open the file

This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient access rights to the file.

You can upgrade to MMC 3.0 by using one of the following methods: <ul> Install Windows Small Business Server 2003 R2 Technologies.</li> Install Windows Server 2003 Service Pack 2.</li> Install the MMC 3.0 update. For more information about MMC 3.0, click the following article number to view the article in the Microsoft Knowledge Base:

907265 MMC 3.0 update is available for Windows Server 2003 and for Windows XP

</li></ul>

After the intallation is complete and after you try to connect to the home page of a Microsoft Windows SharePoint Services Web site, you may receive one of the following error messages:

Error message 1

The Windows SharePoint Services virtual server has not been configured for use with ASP.NET 2.0. .0. For more information, please refer to Knowledge Base article 894903 at http://go.microsoft.com/fwlink/?linkid=42660

Note 2.0. .0 is the version of Microsoft ASP.NET 2.0 that is installed.

Error message 2

Web Part Error: This page has encountered a critical error. Contact your system administrator.

For more information about these error messages, click the following article number to view the article in the Microsoft Knowledge Base:

894903 You receive a &quot;The Windows SharePoint Services virtual server has not been configured for use with ASP.NET 2.0.xxxxx.0&quot; error message when you connect to the home page of a Windows SharePoint Services Web site

Keywords: kbtshoot kbprb kbexpertiseinter KB936915

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.