Microsoft KB Archive/944267

= How to troubleshoot common errors that occur when you run the SharePoint Products and Technologies Configuration Wizard on a computer that is running Windows SharePoint Services 3.0 or SharePoint Server 2007 =

Article ID: 944267

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft Windows SharePoint Services 3.0
 * Microsoft Office SharePoint Server 2007

-



INTRODUCTION
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.



MORE INFORMATION
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 &quot;404&quot; errors. These errors occur until the wizard has finished successfully.

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

By default, this file is located in the &quot;Program Files\Common Files\Microsoft Shared\Web server extensions\12\LOGS&quot; folder.
 * Upgrade.log

By default, this file is located in the &quot;Program Files\Common Files\Microsoft Shared\Web server extensions\12\BIN&quot; folder.

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.

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

[IisWebSiteSequence] [ERROR] [10/17/2007 11:38:22 AM]: Access to the path 'C:\Inetpub\wwwroot\wss\VirtualDirectories\5003\web.config' is denied.

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.

Symptoms
If ASP.NET is registered incorrectly in the IIS metabase, the Upgrade.log file will contain an error message that resembles the following:

[SPIisWebSiteWssSequence] [ERROR] [10/10/2007 10:21:25 AM]: Action 3.0.3.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. [SPIisWebSiteWssSequence] [ERROR] [10/10/2007 10:21:25 AM]: InstallAspNet  failed. [SPIisWebSiteWssSequence] [ERROR] [10/10/2007 10:21:25 AM]: at Microsoft.SharePoint.Upgrade.EnsureAspNetScriptMapInstalled.Upgrade at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade

In this case, the number between &quot;InstallAspNet&quot; and &quot;failed&quot; 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:  Click Start, click Run, type cmd, and then click OK. At the command prompt, move to the following folder:

%windir%\Microsoft.net\framework\v2.0.50727

 At the command prompt, type the following command, and then press ENTER:

aspnet_regiis.exe –s W3SVC/ /ROOT

Note  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

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:

Event Type: Error

Event Source: Windows SharePoint Services 3

Event Category: Topology

Event ID: 6800 Date: 10/17/2007

Time: 8:09:40 PM

User: N/A

Computer:

Description: The database WSS_Content on \Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.

Also, the Upgrade.log file contains the following error message:

[SPServerSequence] [DEBUG] [10/22/2007 7:44:21 AM]: Web service Instance SPWebServiceInstance Parent=SPServer Name= not added. Status = Provisioning

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:  Click Start, click Run, type cmd, and then click OK. Locate the &quot;Program Files\Common Files\Microsoft Shared\Web server extensions\12\BIN&quot; folder. At the command prompt, type the following commands, and then press ENTER after each command:

stsadm -o provisionservice -action stop -servicetype spwebservice -servicename &quot;&quot;

stsadm -o provisionservice -action start -servicetype spwebservice -servicename &quot;&quot;

</li> 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

</li></ol>

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

[AssemblyReferenceFixUp] [3.0.4.0] [ERROR] [10/18/2007 11:47:40 AM]: Application Web Config for this IIS site (944564711) could not be found at \wwwroot\wss\VirtualDirectories\5003\web.config.

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\ folder before you run the SharePoint Products and Technologies Configuration Wizard.

Note  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.

Clear the SharePoint cache
To clear the SharePoint cache, follow these steps:
 * 1) Use Windows Explorer to locate the &quot;Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\ &quot; folder.
 * 2) Back up the .xml files, and then delete the .xml files.
 * 3) Open the Cache.ini file, and then change the content of the Cache.ini setting to 1.
 * 4) Click Start, point to Administrative Tools, and then click Services.
 * 5) Restart the following Windows Services in the order shown:
 * 6) * Windows SharePoint Services Timer service
 * 7) * Administration service

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:

psconfig -cmd upgrade -inplace b2b –force

Additional query words: WSSv3 osconfig

Keywords: kbhowto kbinfo kbexpertiseinter KB944267

-

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

© Microsoft Corporation. All rights reserved.