You experience various issues when you upgrade to or downgrade from a version of Windows Small Business Server 2003

After you upgrade to or downgrade from a version of Microsoft Windows Small Business Server 2003 (Windows SBS 2003), you may experience the following issues:

• You may be unable to log on to the computer.
• You may receive an error message when you try to access the company Web site or a localhost Web site.
• You may receive an error message when you try to access Windows Server Update Services (WSUS) or the Windows SharePoint Services (WSS) Web site.
• You may be unable to start the Microsoft Firewall service.

This article describes methods that you can use to resolve these issues.

Note Generally, whenever you upgrade to or downgrade from the server software, you must reinstall any native components that were updated before the transition. For example, you must reinstall any updates to the Microsoft .NET Framework, to Microsoft Management Console, or to Windows Internet Explorer.

After you upgrade to or downgrade from Microsoft Windows Small Business Server 2003 (Windows SBS 2003), you may experience various issues. These issues that you experience depend on the scenario in which you upgrade to or downgrade from Windows SBS 2003.

Scenario 1

Consider the following scenario. You take one of the following actions:

• You upgrade from Windows SBS 2003 R2 to the full version of Windows Server 2003. To do this, you use the Windows SBS 2003 R2 Transition Pack.
• You downgrade from Windows Server 2003 Standard Edition to Windows SBS 2003, Standard Edition.
• You upgrade from the evaluation version of Windows SBS 2003, Premium Edition to the licensed version of Windows SBS 2003, Premium Edition.

However, before you take one of these actions, you install the Microsoft .NET Framework updates and Microsoft Management Console (MMC) updates from Windows Update or from Windows Server Update Services (WSUS).

In this scenario, you may experience one or more of the following symptoms.

Symptom 1

You cannot log on to the computer.

Symptom 2

You receive an error message when you try to take one of the following actions:

• You try to visit the company Intranet Web site, or you try to visit the localhost Web site. For example, you try to visit one of the following Web sites:
  http://companyweb
  https://companyweb
  http://localhost
  https://localhost
  http://localhost/exchange
  https://localhost /exchange
  http://localhost/remote
  https://localhost/remote
• You try to access WSUS by using Administrative tools.

The error message that you receive resembles the following error message:

Symptom 3

In the WSUS administration interface, you receive the following error message: Or, when you try to access the Windows SharePoint Services (WSS) Web site, you receive the following error message:

Scenario 2

Consider the following scenario:

• You upgrade from the evaluation version of Windows SBS 2003, Premium Edition to the licensed version of Windows SBS 2003, Premium Edition.
• You are running Microsoft ISA Server 2004 on this server.

In this scenario, when you try to start the Microsoft Firewall service, you receive the following error message:

Resolutions for Scenario 1

To resolve the issues that are described in the "Scenario 1" section, use the following methods.

Method 1: To resolve the issue that is described in the "Symptom 1" section

1. Start the computer in safe mode.
2. At a command prompt, type the following commands. Press ENTER after each command.
   
   Note By default, Windows Server 2003 is installed in the C:\Windows folder.
   %SystemDrive%
   cd \\%windir%\IE7\spuninst
   spuninst.exe
3. Complete the steps in the Windows Internet Explorer 7 Uninstall Wizard.
4. Restart the computer.
5. Activate the server software.
6. Reinstall Internet Explorer 7.

Method 2: To resolve the issue that is described in the "Symptom 2" section

If you installed any individual updates or packages before you upgraded to or downgraded from a version of Windows SBS 2003, you must now reinstall these packages. For example, if you installed Microsoft .NET Framework 2.0, MMC 3.0, or Internet Explorer 7, you must reinstall these packages.

Note Windows SBS 2003 R2 automatically installs the packages that are mentioned in this section. Therefore, in a scenario that includes Windows SBS 2003 R2, you may not have manually installed the packages. However, the instructions that are mentioned in this section still apply.

Method 3: To resolve the issue that is described in the "Symptom 3" section

If you installed WSUS 3.0 and WSS 3.0 before you upgraded to or downgraded from a version of Windows SBS 2003, you must determine which component you installed first. To do this, you must view the Windows services in the Services snap-in. If you installed WSUS 3.0 first, you will see the following entry in the services list:If you installed WSS 3.0 first, you will see the following entry in the services list:

If you installed WSUS first

If you verify that you installed WSUS first, follow these steps:

1. At a command prompt, move to the folder where the WSUSSetup.exe file is located.
2. Type the following command, and then press ENTER:
   WSUSsetup.exe /x
   This command extracts the files into the current directory.
3. Type the following command, and then press ENTER:
   cd wyukon
4. Type the following command, and then press ENTER:
   msiexec /i SSEE_10.msi CALLERID=OCSetup.exe REINSTALL=ALL REINSTALLMODE=omus /qn REBOOT=ReallySupress /l*v logfile_name
   Note In this step, logfile_name represents the name of the log file. For example, you can use "Output.log."
5. Start the Services snap-in.
6. Start the Windows Internal Database (MICROSOFT ##SSEE) service.

If you installed WSS first

If you verify that you installed WSS first, follow these steps:

1. At a command prompt, move to the folder where the SSEE_10.msi file is located.
   
   Note Typically, this file is located in the following folder:
   C:\Program Files\MSECache\Wssv3\Database 3
2. Type the following command, and then press ENTER:
   msiexec /i SSEE_10.msi CALLERID=OCSetup.exe REINSTALL=ALL REINSTALLMODE=omus /qn REBOOT=ReallySupress /l*v logfile_name
   Note In this step, logfile_name represents the name of the log file. For example, you can use "Output.log."
3. In Windows Explorer, move to the following folder:
   Drive:\Windows\Microsoft.Net\Framework\v2.0.50727
4. Right-click the Temporary ASP.NET Files folder, and then click Sharing and Security.
5. On the Security tab, assign the Modify right to the NETWORK SERVICE account.

Resolution for Scenario 2

To resolve the issue that is described in the "Scenario 2" section, follow these steps:

1. In Add or Remove Programs, click the entry for Microsoft ISA Server 2004, and then click Change/Remove.
2. Click Repair, and then complete the steps in the repair process.

For more information about scenarios that include Windows SBS 2003 R2, click the following article number to view the article in the Microsoft Knowledge Base: