Hardware Inventory data files larger than 50MB may fail to process on a ConfigMgr 2007 site server

Article translations Article translations
Close Close
Article ID: 973754 - View products that this article applies to.
Expand all | Collapse all
Source: Microsoft Support

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Symptom



When attempting to process a full or delta hardware inventory (.MIF) file, a message similar to the following may be recorded in the dataldr.log file on the System Center Configuration Manager 2007 site server:

Cannot process MIF [xxxxxxxx].mif, moving it to C:\SMS\Inboxes\...\BADMIFS

Where [xxxxxxxx] represents a random alpahnumeric string.

There are no additional errors recorded before or after this message.

Cause



This issue can occur when a MIF file larger than approximately 50MB is received at the site server. Under normal circumstances a MIF file larger than 5MB would be rejected, however that 5MB value can be changed via the following registry key:

HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER
Name: Max MIF Size (REG_DWORD)
Data: Size in bytes. Default is 5000000 (~5MB)

At the time of this article, the upper limit for that value is 50MB. Anything larger than that will result in the log entries noted at the beginning of this article.

Resolution



The overall processing speed of very large (>5MB) MIF files may be unacceptable in many situations. Files of this size are not recommended as they can lead to backlogs of incoming data to be processed, as well as cause other performance degradation issues, such as slowing down the deletion of aged inventory records. Analysis of the individual MIF files should be performed to determine which class(es) are contributing to the overall MIF size.

Reporting for those classes should then be disabled in the SMS_DEF.MOF file.

More Information



For information on how to disable these classes, see the Configuring Configuration Manager Client Local Policy topic at the following Microsoft MSDN Web site:

http://msdn.microsoft.com/en-us/library/cc146756.aspx

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Properties

Article ID: 973754 - Last Review: July 16, 2009 - Revision: 1.0
APPLIES TO
  • Microsoft System Center Configuration Manager 2007
Keywords: 
kbrapidpub kbnomt KB973754

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com