SMS Executive Causes Access Violation When Processing Prochist.dat File

ID: Q241419

The information in this article applies to:

Microsoft Systems Management Server version 2.0

SYMPTOMS

The SMS Executive service may stop responding (hang) or generate an "Access violation" error message during the processing of the Prochist.dat file.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Systems Management Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English-language version of this fix should have the following file attributes or later:


   Date      Time   Version        Size      File name   Platform
   ---------------------------------------------------------------
   9/1/99    1:51pm 2.00.1380.2002   877,664 Baseobj.dll i386
   9/1/99    1:52pm 2.00.1380.2002 1,398,032 Baseobj.dll Alpha

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.

MORE INFORMATION

Installing the Hotfix

To install the hotfix, perform these steps on your Systems Management Server (SMS) site servers:

Stop the SMS Executive and SMS Site Component Manager services.

Replace the Baseobj.dll file in the SMS_root\Bin\Platform folder with the version obtained from the hotfix.

Restart the SMS Executive and SMS Site Component Manager services.

Identifying the Problem

To determine whether you are experiencing the problem outlined in this article, review the Crash.log file in the Sms\Logs\CrashDumps\Date of problem_smsexec folder. The Crash.log file points to the SMS Executive thread responsible for the problem. For example:

Exception Information

Time = 09/01/1999 09:41:03
Service name = SMS_EXECUTIVE
Thread name = SMS_CLIENT_INSTALL_DATA_MGR
Executable = D:\SMS\bin\i386\smsexec.exe
Process ID = 130
Thread ID = 344
Instruction address = 0x7801042A
Exception = 0xC0000005 (EXCEPTION_ACCESS_VIOLATION)
Description = "The thread tried to write to the virtual address 0x063B8000 for which it does not have the appropriate access."
Raised inside CService mutex = No
CService mutex description = ""

Review all thread logs for the thread responsible for the problem and determine whether the thread was responsible for creating the FlushToFile thread used for processing the Prochist.dat file. The thread ID may be different from the thread ID listed in the Crash.log file. For example:

SMS_CLIENT_INSTALL_DATA_MGR_thread_356

CProcHistoryCache::LoadData - Created FlushToFile thread... $$<SMS_CLIENT_INSTALL_DATA_MGR><Wed Sep 01 09:20:58.666 1999 Eastern Daylight Time><thread=356 (0x164)>

Additional query words: prodsms smsexec crash

Keywords : kbSMS120 kbSMS120bug
Version : winnt:2.0
Platform : winnt
Issue type : kbprb