Jump to content

SLG Site Creation Job causes timer service to continuously crash


Recommended Posts

Posted (edited)

Have had SLG2 (June) installed on our WSS3 server recently. Since installation, the WSS timer service continuously crashes (and restarts). The issue is particularly apparent during a full farm backup as it causes the backup to halt while backing up the search database @ 50%. I've found that disabling the SLG Site Creation job works around the problem. Thus far I've tried applying KB949399 and KB913384, neither of which have addressed the issue.

 

I've logged it with Capita, but am posting on the off-chance that anyone else is experiencing the same.

 

These are the errors I'm receiving in the event logs:

 

Event Type: Error

Event Source: .NET Runtime

Event Category: None

Event ID: 1023

Date: 06/08/2008

Time: 11:51:38

User: N/A

Computer: BMS-SR-APPS1

Description:

.NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A05E2B3) (80131506)

 

For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.

 

Event Type: Error

Event Source: .NET Runtime 2.0 Error Reporting

Event Category: None

Event ID: 1000

Date: 06/08/2008

Time: 11:51:38

User: N/A

Computer: BMS-SR-APPS1

Description:

Faulting application owstimer.exe, version 12.0.6211.1000, stamp 46d085ee, faulting module mscorwks.dll, version 2.0.50727.42, stamp 4333e7ec, debug? 0, fault address 0x00113bc7.

 

For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.

 

Event Type: Error

Event Source: .NET Runtime

Event Category: None

Event ID: 0

Date: 06/08/2008

Time: 11:52:52

User: N/A

Computer: BMS-SR-APPS1

Description:

The description for Event ID ( 0 ) in Source ( .NET Runtime ) 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: Unable to open shim database version registry key - v2.0.50727.00000.

 

Event Type: Error

Event Source: Windows SharePoint Services 3 Error Reporting

Event Category: None

Event ID: 5000

Date: 06/08/2008

Time: 11:54:18

User: N/A

Computer: BMS-SR-APPS1

Description:

EventType ulsexception12, P1 owstimer.exe, P2 12.0.6211.1000, P3 46d085ee, P4 missing, P5 missing, P6 missing, P7 missing, P8 missing, P9 c0000005, P10 837l.

 

For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.

Edited by meastaugh1
sp
Posted
What error messages are you getting in the sharepoint error log located in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS on you sharepoint server
Posted

There were several invalid operation (or something like that) messages. Following Capita's advise to download all available Windows Updates seems to have resolved it. Well, it broke it first (of course) by changing the permission on the SQL internal database files so that only administrators had access, and not the system.

 

Thanks.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...