This article has been archived. It is offered "as is" and will no longer be updated.
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:
322756 How to back up and restore the registry in Windows
When an upgrade of a Microsoft Office SharePoint Portal Server 2003 database fails or is canceled by a user, you cannot restart the database upgrade. Or, the virtual servers in SharePoint Central Administration display upgrade.
If you view the event logs, you may receive the following Informational message in the Application log:
Event Type: Information Event Source: SharePoint Portal Administration Service Event Category: None Event ID: 601Date: 10/26/2005Time: 6:38:01 PM User: N/A Computer: COMPUTERNAME Description: Attempted to apply update to SharePoint Portal Server 2003 portal sites. Number of portal sites: 2 Number of portal sites attempted: 1 Number of portal sites successfully updated: 1 Not run: 1 Consult the ReadMe file included with this patch, or *_spsadmin.log for more details.
For more information, see Help and Support Center at http://support.microsoft.com. Data: 0000: 41 00 70 00 70 00 44 00 A.p.p.D. 0008: 6f 00 6d 00 61 00 69 00 o.m.a.i. 0010: 6e 00 3a 00 20 00 73 00 n.:. .s. 0018: 70 00 73 00 61 00 64 00 p.s.a.d. 0020: 6d 00 69 00 6e 00 2e 00 m.i.n... 0028: 65 00 78 00 65 00 e.x.e.
This problem may occur when you install Microsoft Office SharePoint Portal Server 2003 Service Pack 2 (SP2) or when you apply a SharePoint Portal Server 2003 post-SP2 hotfix. When you install SharePoint Portal Server 2003 SP2 or apply a SharePoint Portal Server 2003 post-SP2 hotfix, an upgrade of a SharePoint Portal Server 2003 database occurs as a part of the update.
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.
Review all SharePoint Portal Server 2003 logs. These logs include the *_spsadmin.log logs that are mentioned in event ID 601 in the "Symptoms" section. Correct failures as described in these logs. If correcting the issues that are found in all SharePoint Portal Server 2003 logs does not resolve the upgrade issue, use the following steps.
To resolve this problem, follow these steps as appropriate for your situation.
In single and small SharePoint Portal Server farms
Click Start, click Run, type regedit, and then click OK.
, type the appropriate value in the Value data box, and then click OK.
Note The appropriate value for SP2 is 184.108.40.206. However, post-SP2 hotfixes may contain a different schema version. Make sure that you enter the appropriate value.
Close Registry Editor, and then restart the computer.
After the computer restarts, click Start, point to Administrative Tools, and then click Services.
In the Services MMC snap-in, double-click SharePoint Portal Administration, click Start, set the Startup type to Automatic, and then click OK..
Click Start, point to Administrative Tools, and then click SharePoint Central Administration.
On the Central Administration page, click Configure virtual server settings under Virtual Server Settings.
Determine whether the virtual servers still display upgrade next to the virtual server name.
If upgrade is still displayed, repeat steps 1 and 2 to stop the SharePoint Portal Administration service on the computer. Then, repeat steps 4 to 15 on a different front-end Web server until at least one of the virtual servers does not display upgrade.
If the virtual server does not display upgrade under Virtual Server Settings, you must first back up all the SharePoint sites in the farm by using SharePoint Portal Server Data Backup and Restore.
For more information about how to back up and restore SharePoint Portal Server 2003, see the "Backup and Restore" section of the Microsoft Office SharePoint Portal Server 2003 Administration Guide.
After you back up SharePoint Portal Server 2003, you must perform a forced upgrade on the remaining front-end Web servers in the farm by running the following command at the command prompt:
Note By default, the stsadm command line tool is located in the \Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN folder.
You must perform these steps on each front-end Web server on which the extended virtual servers display upgrade.
The SharePoint Portal Server 2003 databases store the schema version in the PortalSchemaVersion tables in all the portal databases. These databases include the Configuration, _SITE, _PROF, and _SERV databases.
For the original release version of SharePoint Portal Server 2003 and for SharePoint Portal Server 2003 Service Pack 1 (SP1), the columns in the PortalSchemaVersion tables for all the portal databases should be as follows:
SchemaVersion 220.127.116.11 BuildVersion 11.0.5704.0
After SharePoint Portal Server 2003 Service Pack 2 (SP2) is installed, the columns in the PortalSchemaVersion tables for all the portal databases should be as follows:
SchemaVersion 18.104.22.168 BuildVersion 11.0.8126.0
Note The SchemaVersion of the Configuration database does not change. It will be 22.214.171.124.
After SharePoint Portal Server 2003 Service Pack 3 (SP3) is installed, the columns in the PortalSchemaVersion tables for all the portal databases should be as follows:
SchemaVersion: 126.96.36.199 BuildVersion 11.0.8168.0
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.