The total number of files in the dataldr.box inbox of Inventory Data Loader on the site server has exceeded the standard operational threshold.
This folder temporarily stores Management Information Format (MIF) files that represent hardware inventory data for Configuration Manager client computers. It also stores IDMIF files for custom architectures.
This condition increases unless it is resolved. If the file count keeps going beyond the threshold, hardware inventory is not reflected in the Configuration Manager 2007 site database in a timely manner, and collections and reports might not accurately represent the devices on the network.
The total number of hardware inventory files can exceed the threshold because:
The SMS_Executive service is stopped or is not responding on the site server.
Inventory Data Loader could be sending inventory details to a new parent site. These changes take priority over standard hardware inventory file processing, which is suspended until they are processed.
The site server file processing rate is slower than the incoming rate of hardware inventory files.
The site server has insufficient resources such as CPU, memory, or disk space.
The Configuration Manager 2007 site database has no more space.
The SMS_def.mof file has been modified to collect additional information and the resulting larger inventory file requires increased processing time. Also, modifying the SMS_def.mof file forces a hardware inventory resynchronization which results in more hardware inventory files to be processed.
The site server might have lost connectivity to the Configuration Manager 2007 site database server.
To resolve this issue and to decrease the number of hardware inventory files:
Verify that the threshold for this alert is not too low and is beyond the standard operating threshold for this specific Configuration Manager 2007 site.
Verify that the SMS_Executive service is running on the site server. If it is stopped or is not responding, restart the service.
Verify that the Configuration Manager site database is performing properly.
Determine whether the increased load is due to an infrequent influx of new hardware inventory records, or whether the file load remains relatively constant. If the load is constant, update the Configuration Manager 2007 infrastructure to achieve zero processing backlogs. If the load is due to a large number of newly inventoried computers, the issue can resolve itself if there are sufficient resources to process pending files in addition to the standard file load.
Verify that the Configuration Manager site database has sufficient space. If the database is set to autogrow, verify that there is sufficient disk space for the database to expand.
Adjust the frequency of inventory collection to allow for a longer interval for files to be processed.
Plan carefully before modifying the SMS_def.mof file. Conduct performance testing to verify that the infrastructure can accommodate the extra load, including hardware inventory resynchronizations. If the infrastructure cannot accommodate the extra load you might need to return the SMS_def.mof to the default settings.
Verify that the site server has connectivity to the Configuration Manager 2007 site database server.
See Planning and Deploying the Server Infrastructure for Configuration Manager 2007 at the Configuration Manager Product Documentation Web page.
For more information about inbox folders and how they are used in Configuration Manager, see the “A description of inbox folders and how they are used in Configuration Manager” Web page (http://go.microsoft.com/fwlink/?LinkId=99539).
For more assistance, see a list of additional support options in the support section of the Configuration Manager Web site at Support for Configuration Manager.