SMS: Troubleshooting Inventory MIF Backlog Problems

• Microsoft Systems Management Server versions 1.0, 1.1, and 1.2

SYMPTOMS

MIFs may build up in the ..SMS\Site.srv\Dataloder.box\Deltamif.col directory (or the ..SMS\Site.srv\Dataloder.box\Deltamif.col\Process directory in version 1.2) for a variety of reasons. This article outlines troubleshooting suggestions to why the build up occurs and how to resolve it.

CAUSE

The ..SMS\Logs\Datalodr.log and the Windows NT Application Event Log on both the SQL Server computer and the Systems Management Server Site Server provide information about possible causes. You should also check the SQL Server error log.

NOTE: Before you begin troubleshooting, dump the Systems Management Server and Master databases and then back up the Systems Management Server directory structure and the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS registry key.

Site Speed

The site speed (set in Site Properties on the Services tab) should never be set to Very Fast. A setting of Medium or Fast will process MIFs faster because the Site Configuration Manager does not have to continually perform watchdog cycles which gives the Dataloader utility a chance to run uninterrupted for a longer period of time.

SQL Configuration

If Open Objects is set to less than 5,000, Dataloader can get backed up. Tempdb should be 20-30 percent of the largest database on the computer running SQL Server. User connections must be set appropriately.

For additional information about important tuning parameters, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q166244
   TITLE     : SMS: SQL Server Tuning Parameters for Systems Management
               Server

Database and Transaction Log Size

Make sure that the database and its transaction log are not full, and that the transaction log is 20 percent of the Systems Management Server database size. If the database is less than 20 percent free, failures may occur.

Services

Make sure that the Systems Management Server Executive Service is running on the site server.

Client Resyncs

Check the Windows NT event log for a high number of client resyncs (Event 186). If there are several resynchronizations, they may occur because duplicate SMSIDs are assigned. For additional information, please see the following articles in the Microsoft Knowledge Base:

   ARTICLE-ID: Q127052
   TITLE     : SMS Unique ID (SMSID) Allocation

   ARTICLE-ID: Q138021
   TITLE     : How Inventory Dataloader Finds Matching Computers in SMS

SQL Server Service Pack

Apply (or re-apply) the latest SQL Server Service Pack.

SQL Tracing

You can enable SQL statement input and output in the Dataloder.log by setting the

   HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Tracing\SQL Enabled

The Systems Management Server Executive Service must be stopped and restarted for the change to take effect.

NOTE: SQL Tracing should be disabled when you are not performing troubleshooting steps. Leaving it enabled causes the Dataloader to slow down and the log to fill up more quickly.

DBCC Checks

Run SQL Server DBCC Checkdb and NewAlloc on the Systems Management Server database in Single User Mode.

Site Reporter

Check the ..SMS\Site.srv\Siterep.box to see if there are files present. If there are, and the site is a child primary site, ensure that site-to-site communication is functioning properly. To determine this, do the following:

• Look in the appropriate sender log.
• Check the addresses.
• Check the Windows NT Application Event Log.
• Check the Outbox scheduling.

User Group MIFS

Check the SMS\Site.srv\Dataloder.box\Deltamif.col directory for UMF files. If there are several UMF files, and they are large, you probably have a large number of users, groups, or a complicated trust matrix in your environment.

You may want to change the default polling interval for user and group enumeration using the Setgug.exe utility. For additional information about the utility, please see the following articles in the Microsoft Knowledge Base:

   ARTICLE-ID: Q168724
   TITLE     : SMS: List of Tools Available on the SMS 1.2 Compact Disc

   ARTICLE-ID: Q171005
   TITLE     : SMS: Site Config Manager Service Locks Trusted Service
               Account

MIF Size

Check the SMS\Site.srv\Dataloder.box\Deltamif.col and SMS\Site.srv\Dataloder.box\Deltamif.col\Process directories and note the MIF size. Larger MIFs (that is, MIFs that contain custom information or extensive software inventory) will process slower.

I/O Errors

If SQL Server devices and Systems Management Server directories are on the same drive or the drive is mirrored with a single disk controller, check for I/O disk errors reported in the SQL log file and/or Performance Monitor.

If disk I/O appears to be a bottleneck, you may need to move SQL Server devices to another physical disk drive, install a second controller, and so forth.

SMSMaint Script

Run the SMSMaint.sql script from the BackOffice Resource Kit.

SPID Performance

Monitor the SQL SPID performance using SQL WHO and Performance Monitor to correlate this to the Dataloader thread. For additional information, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q117559
   TITLE     : How to Correlate Spid, Kpid, and Thread

Inventory Frequency

Decrease inventory frequency if necessary. For example: if there are six child sites of 2,000 to 4,000 plus clients that inventory every time they log on, and they report to a central site, an expected backlog will occur.

Systems Management Server 1.2 Dataloader is multithreaded. If MIFs are large, and/or the number of clients is large, a Systems Management Server version 1.0 or 1.1 site may have MIF backup and the troubleshooting suggestions may not help. If the site is 1.0 or 1.1, consider upgrading to Systems Management Server version 1.2 (and the latest Systems Management Server service pack).