A custom status MIF file does not return a "10009 - success" installation status message as expected in SMS 2003 (916797)


The information in this article applies to:

  • Microsoft Systems Management Server 2003

SYMPTOMS

In Microsoft Systems Management Server (SMS) 2003, a custom advertisement status Management Information Format (MIF) file is sometimes generated by a program such as Ismif32.exe. However, the SMS client does not always correctly report the package installation status from the MIF file. Instead, the package returns the following generic status message ID: 10008 -successYou expect the package to return the following custom status message ID: 10009 - successAdditionally, the following message is logged in the Execmgr.log file: execmgr Program exit code 0
execmgr Looking for MIF file to get program status The following message should be the next entry in this log file:A Matching MIF file mif name was foundHowever, this entry does not exist.

CAUSE

This problem occurs because Execution Manager requires data in one of the status matching fields. By default, these fields are blank.

Note These status matching fields are located on the Reporting tab in the package properties.

WORKAROUND

To work around this problem, add the name that is defined in the ISMIF32.EXE -p Name parameter to the NAME field on the package properties Reporting tab. By doing this, you enable the Execution Manager component to find a match between the package and the MIF file. You can also add the MIF File Name, Version, and Manufacturer fields, but these fields are not required.

This workaround requires that the Ismif32.exe command line include the -f Mif File name and -p Name switches. However, for status MIF matching to occur, only the Name value for the -p switch must be entered in the Name field on the Reporting tab of the corresponding package properties.

The MIF file is created in the Temp folder of a program's user context when that program runs. If the status MIF matching is successful, the MIF file will be automatically deleted from the Temp folder.

A failed attempt to match an MIF file leaves the orphaned MIF file in the Temp folder. To determine the Name value from an existing MIF file, open the MIF file in the Temp folder, and then locate the value in the following section:

START ATTRIBUTE
NAME Product
ID = 2
ACCESS = READ-ONLY
STORAGE = SPECIFIC
TYPE = STRING(64)
VALUE = SMS
END ATTRIBUTE

In the following sample command line, the MIF file name is "MYMIF," and the Name value is "SMS":

Ismif32.exe -f MYMIF -p SMS -d "Completed successfully"

Verify that the name in the "Value =" field matches the name in Name field on the Reporting tab. For example, if "Value = SMS" appears in the MIF file, "SMS" is entered in the Name field on the Reporting tab. Correct the information in the Name field if you have to, and then rerun the program. This action generates the Mymif.mif file that, in turn, generates the 10009 exit code.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

The switches map to the Reporting tab fields as follows:
MIF file nameValue entered for -f
NameValue entered for -p
VersionValue entered for -v
PublisherValue entered for -c
You may experience this problem when you run any program that creates a status MIF file. However, if the program is also set to create an entry in the Name field for status MIF matching, you will not experience this problem.

REFERENCES

For more information about parameters that are used by the Ismif32.exe process, click the following article number to view the article in the Microsoft Knowledge Base:

186415 Status MIF creator, Ismif32.exe, is available for Systems Management Server 1.2

268791 How a status Management Information Format (MIF) file produced by the ISMIF32.exe file is processed in SMS 2.0

Modification Type:MajorLast Reviewed:4/29/2006
Keywords:kbExpertiseAdvanced kbBug kbSMSPackage kbSMSAppScripts kbprb KB916797 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.