This article describes how to troubleshoot some common errors that occur when you run the SharePoint Products and Technologies Configuration Wizard after you upgrade a computer that is running Microsoft Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007.

Back to the top

After you install one of the following updates or service packs on a computer that is running Windows SharePoint Services 3.0 or SharePoint Server 2007, you may have to rerun the SharePoint Products and Technologies Configuration Wizard (Psconfig.exe):

•	Windows SharePoint Services 3.0 software update
•	Windows SharePoint Services 3.0 service pack
•	SharePoint Server 2007 software update
•	SharePoint Server 2007 service pack

If the SharePoint Products and Technologies Configuration Wizard detects a problem, the wizard does not finish. Additionally, users who try to visit the SharePoint Web site may receive "404" errors. These errors occur until the wizard has finished successfully.

To help troubleshoot this problem, obtain the following SharePoint log files:

•	PSCDiagnostics_Datecode.log By default, this file is located in the "Program Files\Common Files\Microsoft Shared\Web server extensions\12\LOGS" folder.
•	Upgrade.log By default, this file is located in the "Program Files\Common Files\Microsoft Shared\Web server extensions\12\BIN" folder.

Back to the top

How to identify and resolve the problem

This section lists various problems that may be detected by the SharePoint Products and Technologies Configuration Wizard. Symptoms are listed for each problem to help you identify it.

The Web.config file is read-only

Symptoms

If the Web.config file is read-only, the Upgrade.log file will contain an error message that resembles the following:

Cause

This problem occurs when the Web.config file has been configured as read-only. This problem may also occur when a custom management program or a virus scan program locks the Web.config file.

Resolution

Make sure that everyone has write access to this file before you run the SharePoint Products and Technologies Configuration Wizard. Also make sure that the read-only check box is not enabled in the Web.config file properties dialog box and that no other process locks the Web.config file.

ASP.NET is registered incorrectly in the Internet Information Services (IIS) metabase

Symptoms

If ASP.NET is registered incorrectly in the IIS metabase, the Upgrade.log file will contain an error message that resembles the following: In this case, the number between "InstallAspNet" and "failed" in this message is the ID of the affected IIS Web site.

Cause

This problem occurs because ASP.NET is registered incorrectly in the IIS metabase.

Resolution

To resolve this problem, follow these steps:

1.	Click Start, click Run, type cmd, and then click OK.
2.	At the command prompt, move to the following folder: %windir%\Microsoft.net\framework\v2.0.50727
3.	At the command prompt, type the following command, and then press ENTER: aspnet_regiis.exe –s W3SVC/number/ROOT Note number is the ID of the affected IIS Web site.

A second cause can be a timing issue in the Windows SharePoint Administration service. To address this cause, set the following registry subkey: DWORD value: SleepOnStart set to 20000 decimal

You receive a "The database WSS_Content on ComputerName\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures" error message

Symptoms

The following error message is logged in the Application log on the computer that is running Windows SharePoint Services 3.0 or SharePoint Server 2007:Also, the Upgrade.log file contains the following error message:

Cause

This problem occurs when the initial provisioning of the Web service instance has not completed successfully. This behavior causes the upgrade process to skip the Web service instance.

Resolution

To resolve this problem, follow these steps:

1.	Click Start, click Run, type cmd, and then click OK.
2.	Locate the "Program Files\Common Files\Microsoft Shared\Web server extensions\12\BIN" folder.
3.	At the command prompt, type the following commands, and then press ENTER after each command: stsadm -o provisionservice -action stop -servicetype spwebservice -servicename "" stsadm -o provisionservice -action start -servicetype spwebservice -servicename ""
4.	After the SPWebService service is started, type the following command at the command prompt, and then press ENTER: psconfig -cmd upgrade -inplace b2b -wait -force

The Web.config file is missing

Symptoms

The Upgrade.log file contains an error that resembles the following:

Cause

This behavior occurs when the Web.config file has been deleted or moved.

Resolution

To resolve this problem, make sure that the Web.config file is located in the Wwwroot\Wss\VirtualDirectories\xxxx folder before you run the SharePoint Products and Technologies Configuration Wizard.

Note xxxx represents the virtual server physical location for the SharePoint Web application. In IIS, the virtual server physical location is listed next to Local path on the Home Directory tab in the virtual server properties dialog box.

The SharePoint Products and Technologies Configuration Wizard does not finish successfully

Symptoms

You run the SharePoint Products and Technologies Configuration Wizard (PSConfigui.exe) to upgrade the databases. When you do this, the wizard does not finish successfully. Additionally, the following error message is logged: This message is logged in the following log file:

Cause

This issue occurs because a lock exists on the SPFarm object. Therefore, the SharePoint Products and Technologies Configuration Wizard cannot update the databases.

Resolution

To resolve this issue, clear the Windows SharePoint Services configuration cache.

For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

How to force the Windows SharePoint Services 3.0 upgrade by using the Psconfig.exe tool at a command prompt

Perform the upgrade by running the Psconfig.exe tool at a command prompt. For example, type the following command:

Back to the top