SMS server services may unexpectedly stop when an access violation occurs in SMS 2003 (906317)


The information in this article applies to:

  • Microsoft Systems Management Server 2003

SYMPTOMS

The SMS_EXECUTIVE service (Smsexec.exe) may unexpectedly stop when an access violation occurs in Microsoft Systems Management Server (SMS) 2003. The access violation occurs during the startup of the SMS_EXECUTIVE service.

This problem typically occurs when the SMS_SITE_COMPONENT_MANAGER service tries to start the SMS_EXECUTIVE service after the scheduled Backup SMS Site Server task has completed.

Additionally, an error message that is similar to the following is logged in the Crash.log file:
Exception = c0000005 (EXCEPTION_ACCESS_VIOLATION)
Description = "The thread tried to read from the virtual address 00000060 for which it does not have the appropriate access."
Note The "Thread name" that is listed in the Crash.log file varies.

This problem may also occur with the SMS_SQL_MONITOR, SMS_SERVER_LOCATOR_POINT, and SMS_SITE_BACKUP services.

CAUSE

SMS 2003 uses Open Database Connectivity (ODBC) to connect to a Microsoft SQL Server database. Occasionally, the operating system unloads the Comsvcs.dll file too early. Therefore, SMS 2003 cannot successfully make an ODBC connection to the database.

RESOLUTION

To resolve this problem, install hotfix 897667 on the SMS 2003 site servers, SMS server locator point servers, and the computers that are hosting the SMS 2003 database.

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

897667 Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type:MajorLast Reviewed:3/14/2006
Keywords:kberrmsg kbtshoot kbprb KB906317 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.