SharePoint Services 3.0 SP1 Error Event ID 6614

Question

Hello,

I have a 2005 TFS Web Access Server running WSS 3.0 SP1 that is crashing every night around 1:50AM PST.  It throws the following error and then the entire SharePoint site throws a generic error stating ':

Event Type:    Error
Event Source:    Windows SharePoint Services 3
Event Category:    Runtime
Event ID:    6614
Date:        1/11/2012
Time:        1:52:48 AM
User:        N/A
Computer:    SERVER
Description:
Safe mode did not start successfully. The 'configuration' start tag on line 11 does not match the end tag of 'configSections'. Line 26, position 4. (c:\inetpub\wwwroot\automaton\web.config line 26)


Line 11:  <section name="SafeMode" type="Microsoft.SharePoint.ApplicationRuntime.SafeModeConfigurationHandler, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />

Line 26: <WebPartControls DatasheetControlGuid="65BCBEE4-7728-41a0-97BE-14E1CAE36AAE" />

We have Team System Web Access running on the same box and it does not go down.  It seems to be specific to SharePoint Services only.  Please let me know if you need any further information.  Any help would be greatly appreciated.

Thanks,
Ryan

Answer 1

It sounds like you have a problem which might be fixed via a recent hotfix.

Visit http://support.microsoft.com/kb/957691 for more info and to aquire the hotfix.

If this does not help, there are a few things I would suggest. Review the accounts that your application pools are running under. Then in Sharepoint Central Administration, on the Operations tab, use the service accounts option and go through it and set the account/password for any of your application pools again. Sometimes the account info that sharepoint holds and the account info actually being used by the application pools (as visible through IIS manager) are out of sync and it causes funny problems like this (especially after a backup/restore to another server).

Also review your Alternate Access Mappings again to make sure they are correct too and account for both URL sets you are using.

Answer 2

Thank you SPAdmin.  I am going to try applying SP2 and then SP3 to WSS3.0 to see if the issue still exists.  I will report back if this resolves my issue or if I also need to install the hotfix mentioned above.