Link to home
Start Free TrialLog in
Avatar of ambisasia
ambisasiaFlag for Japan

asked on

Windows SharePoint Services Site not accessible

Since two weeks ago our Windows SharePoint Services 3.0 site is not accessible anymore.
We found the following errors in the event log:

Event Type:      Error
Event Source:      SharePoint Products and Technologies Configuration Wizard
Event Category:      None
Event ID:      104
Date:            2007-10-27
Time:            21:56:29
User:            N/A
Computer:      ServerName
Description:
Failed to initialize SharePoint Products and Technologies upgrade.
An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: The initialize command is invalid or a failure has been encountered.
A previous attempt to upgrade SharePoint Products and Technologies has failed.  For more information about this failure, review the upgrade log on server SRVJPTYOFP or review the SharePoint Timer service upgrade job status using the Central Administration Web Application.  To retry upgrade, run psconfig.exe and specify the force parameter along with the upgrade command on server SRVJPTYOFP.
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
   at Microsoft.SharePoint.PostSetupConfiguration.TaskCommon.CheckIfUpgrading(TaskBase task)
   at Microsoft.SharePoint.PostSetupConfiguration.InitializeTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Event Type:      Error
Event Source:      SharePoint Products and Technologies Configuration Wizard
Event Category:      None
Event ID:      100
Date:            2007-10-27
Time:            21:56:29
User:            N/A
Computer:      ServerName
Description:
Configuration of SharePoint Products and Technologies failed.  Configuration must be performed in order for this product to operate properly.  To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_10_27_2007_21_56_23_726_642100451.log, fix the problem, and run this configuration wizard again.

Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7000
Date:            2007-10-28
Time:            19:48:22
User:            N/A
Computer:      ServerName
Description:
The Windows SharePoint Services Administration service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

This is very urgent. Can anybody help?
Thanks.
Avatar of Robbie_Leggett
Robbie_Leggett
Flag of United Kingdom of Great Britain and Northern Ireland image

These seem to be errors relating to the upgrade of SharePoint, specifically from v2 to v3. Have you recently upgraded?

If so you need to run the prescan tool as outlined in this article:

http://blogs.neudesic.com/blogs/grant_earl/archive/2007/04/05/5465.aspx

:-)
Avatar of ambisasia

ASKER

No we fresh installed WSPS 3.0 a few month ago.
Only Windows Updates have been applied.
We also have a 33002 Error on the MSSQL Source and a 6398 Error on the WSPSearch Source.

We then searched the errors over the internet and found below;
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2272416&SiteID=1

It basically says that the problem is caused by one of the MS updates.
After confirming the update already installed on the server, We followed the instruction according to what is written there, but during the process a failed message was shown, means still no fix for the problem.
ASKER CERTIFIED SOLUTION
Avatar of Robbie_Leggett
Robbie_Leggett
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi Experts,

I have several more errors/information from the problematic server  Event Viewer as below;

***************************************************************************************************************************
<1>
Event Type:      Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 3759
Date: 2007-10-29
Time:16:20:18
User:N/A
Computer: Server Name
Description:
Database 'SharePoint_AdminContent_4b3bfde1-7341-41f1-b198-b796b64b4629' on SQL Server instance 'Server Name\Microsoft##SSEE' is not empty and does not match current database schema.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

<2>
Event Type:      Information
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (2)
Event ID: 5084
Date: 2007-10-29
Time:16:20:18
User:Domain Name\Admin ID
Computer: Server Name
Description:
The description for Event ID ( 5084 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: MULTI_USER, ON, SharePoint_AdminContent_4b3bfde1-7341-41f1-b198-b796b64b4629.
Data:
0000: dc 13 00 00 0a 00 00 00   Ü.......
0008: 1b 00 00 00 53 00 52 00   ....S.R.
0010: 56 00 4a 00 50 00 54 00   V.J.P.T.
0018: 59 00 4f 00 46 00 50 00   Y.O.F.P.
0020: 5c 00 4d 00 49 00 43 00   \.M.I.C.
0028: 52 00 4f 00 53 00 4f 00   R.O.S.O.
0030: 46 00 54 00 23 00 23 00   F.T.#.#.
0038: 53 00 53 00 45 00 45 00   S.S.E.E.
0040: 00 00 3d 00 00 00 53 00   ..=...S.
0048: 68 00 61 00 72 00 65 00   h.a.r.e.
0050: 50 00 6f 00 69 00 6e 00   P.o.i.n.
0058: 74 00 5f 00 41 00 64 00   t._.A.d.
0060: 6d 00 69 00 6e 00 43 00   m.i.n.C.

<3>
Event Type:      Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 6800
Date: 2007-10-29
Time: 15:55:18
User: N/A
Computer: Server Name
Description:
The database WSS_Content on Server Name\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

<4>
Event Type:      Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 5586
Date: 2007-10-29
Time: 15:55:09
User: N/A
Computer: Server Name
Description:
Unknown SQL Exception 33002 occured. Additional error information from SQL Server is included below.
Access to module dbo.proc_GetRunnableWorkItems is blocked because the signature is not valid.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
***************************************************************************************************************************

I found several postings on the internet more or less likely to be related to my problem;
http://www.microsoft.com/downloads/details.aspx?familyid=A49472F9-93EF-4423-BD0B-06B1B331C7AC&displaylang=en

http://groups.google.com.au/group/microsoft.public.sharepoint.windowsservices/browse_thread/thread/b7398493e055b188/e99aceb391d28356?

I tried the reinstallation of KB932091 according to the recommendation by extracting the patch file and ran "dw20w.msp" but it didn't work.

Your advice/support would be appreciated.
As I said, as this has been caused by a Microsoft update, you should call Microsoft PSS. They will be able to assist, and hopefully find a way to roll back the update.

:-)
this worked for me -
To resolve this problem, follow these steps:
Click Start, click Run, type cmd in the Open box, and then click OK.
Change to the following directory:
system drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin
Note The system drive placeholder represents the drive on which Windows is installed.
At the command prompt, type the following command, and then press ENTER to stop the SPWebService service:
stsadm -o provisionservice -action stop -servicetype spwebservice -servicename ""
After the SPWebService service has stopped, type the following command, and then press ENTER to start the SPWebService service:
stsadm -o provisionservice -action start -servicetype spwebservice -servicename ""
After the SPWebService service is started, type the following command to complete the hotfix process or the update process:
psconfig -cmd upgrade -inplace b2b -wait -force
Thank you very much. After running the force update and observed the upgrade log, i found out that there are permission problems with my database. After grand permission to sharepoint database and applied the update, everything get back to work.
Thanks for all of your support