The SMS_EXECUTIVE service stops when you process a MIF file in SMS 2.0 (841230)



The information in this article applies to:

  • Microsoft Systems Management Server 2.0

SYMPTOMS

The Microsoft Systems Management Server (SMS) SMS_EXECUTIVE service may cause an access violation in SMS Inventory Dataloader when Inventory Dataloader processes a Management Information Format (MIF) file. This scenario may cause the SMS_EXECUTIVE service to stop. (The SMS Site Component Manager service automatically restarts the service within an hour.) When this problem occurs, the last log entry that is written to the Dataldr.log file is similar to the following:
Processing file ab0x9s06.mif
The MIF file name in the log entry will vary.

CAUSE

Before SMS Inventory Dataloader adds the content of a MIF file to the SMS database, Inventory Dataloader parses the file to make sure that the file contains valid data. If Inventory Dataloader finds a problem with the MIF file content, Inventory Dataloader tries to log an error to the Dataldr.log file. A problem with the way that the log file data is formatted may cause the SMS_EXECUTIVE service to stop.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Systems Management Server 2.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have SMS 2.0 Service Pack 4 installed to apply this hotfix.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version           Size     File name     Platform
   ---------------------------------------------------------------------
   02-May-2002  01:10  2.0.1493.4225     538,048  Baseutil.dll  x86
   01-May-2002  23:35  2.0.1493.4218     234,896  Distmgr.dll   x86
   02-May-2002  01:10  2.0.1493.4225      41,312  Smssvreh.dll  x86


Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.


How to install the hotfix

  1. Create a folder in a location that is accessible to your SMS site servers.
  2. Copy the SMS2.0-SPX-KB841230-X86-ENU.exe update file to the new folder, where X is the service pack version.
  3. From each of the primary and secondary SMS site servers in your environment, use administrative credentials to log on to your site server.
  4. Quit the SMS Administrator console if it is running.
  5. Run the SMS2.0-SPX-KB841230-X86-ENU.exe command, where X is the service pack version, and then follow the instructions in the wizard. The wizard will perform a site reset at the end of the hotfix installation.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Microsoft Systems Management Server 2.0 Service Pack 5.

MORE INFORMATION

This problem may occur when Inventory Dataloader encounters a parsing error that invalidates a MIF file. For example, if the Last Hardware Scan attribute has a date value that is before the year 1980 or after the year 2035, you may experience this problem.

If you turn off server side logging for SMS, the problem still occurs.

Modification Type:MinorLast Reviewed:4/14/2006
Keywords:kbQFE kbHotfixServer kbSMS200preSP5fix KB841230