Microsoft KB Archive/328937

= SMS: Site Server Processes Management Information Format Files Slowly =

Article ID: 328937

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition

-



This article was previously published under Q328937



SYMPTOMS
A Systems Management Server (SMS) site server may process Management Information Format (MIF) files slowly for a number of reasons. For additional information about how to troubleshoot the most common reasons for MIF backlogs, click the following article numbers to view the articles in the Microsoft Knowledge Base:

201544 SMS: Information About Troubleshooting Inventory Management Information Format Backlog Problems

MIF processing may also be slow on SMS site servers that process a lot of hardware inventory data if SQL stored procedures are deleted and re-created. If you enable SMS SQL logging as described in the following Microsoft Knowledge Base article, the log file records the stored procedures that are dropped and re-created.

139141 Debugging SMS/SQL Related Problems

The log file contents are similar to the following entry in the Dataldr.log file:

SQL>>> IF EXISTS (SELECT * FROM sysobjects WHERE id = object_id('pSystem_DATA')) DROP procedure pSystem_DATASQL>>>>> Done. SQL>>>begin transaction SQL>>>>> Done. SQL>>>delete SMSProcedures from SMSProcedures where SMSProcedureID = 43 SQL>>>>> Done. SQL>>>commit transaction SQL>>>>> Done. SQL>>> IF EXISTS (SELECT * FROM sysobjects WHERE id = object_id('dSystem_DATA')) DROP procedure dSystem_DATA SQL>>>>> Done. SQL>>>begin transaction SQL>>>>> Done. SQL>>>delete SMSProcedures from SMSProcedures where SMSProcedureID = 44SQL>>>>>Done.SQL>>>commit transactionSQL>>>>> Done. SQL>>> IF EXISTS (SELECT * FROM sysobjects WHERE id = object_id('pSystem_DATA')) DROP procedure pSystem_DATA SQL>>>>> Done. SQL>>>CREATE PROCEDURE pSystem_DATA @Pragma int ,@MachineID int ,@TimeKey datetime ....

This example shows an entry that is logged when the stored procedures for the System_DATA class are dropped and re-created. You also typically see that the stored procedures for several other classes are dropped and re-created.



CAUSE
This behavior may occur if either of the following conditions exists:
 * An attribute that is contained in a MIF file does not match the value in the ValueType column.
 * The Key flag does not match the value in the IsKey column in the AttributeMap SQL table.

By default, SMS contains some of these mismatches. Custom changes to the Sms_def.mof file can create other mismatches.



Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft Systems Management Server 2.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

288239 How to Obtain the Latest Systems Management Server 2.0 Service Pack

Hotfix Information
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Systems Management Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix for SMS 2.0 Service Pack 4 (SP4) sites 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 --  01-May-2002  22:05  2.0.1493.4200  1,718,544  Conv20.exe  Alpha 01-May-2002 22:05  2.0.1493.4200  1,356,672  Conv20.exe  x86 Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Using the Hotfix Installer
Note Use this method only for Intel-based computers.
 * 1) Create a folder in a location that is accessible to your SMS site servers.
 * 2) Copy the update file (Q328937.exe) and platform folders to the new folder. You must arrange the folder structure so that the update file is located one folder &quot;above&quot; the platform folders.
 * 3) From each of the primary SMS site servers in your environment, log on to your site server by using an account with administrative credentials (including Database Owner).
 * 4) Quit the SMS Administrator console if it is running.
 * 5) Run Q328937.exe, and then follow the instructions in the wizard.

Note If you receive a &quot;Login to SQL Server Failed&quot; error message when you try to use Windows security (integrated security) to run Conv20.exe, you must either switch to SQL Server security (standard security) or run the SQL Client Network utility and make sure that Named Pipes is the default (first) network library (not TCP/IP).

Performing a Manual Installation

 * 1) Create a folder in a location that is accessible to your SMS site servers.
 * 2) Copy the platform folders that contain the hotfix files to the new folder.
 * 3) From each of the primary SMS site servers in your environment, log on to your site server by using an account with administrative credentials (including Database Owner).
 * 4) Quit the SMS Administrator console if it is running.
 * 5) At a command prompt, type conv20.exe.
 * 6) When you are prompted, type the server name, database, login ID, and password. Leave the Login ID box and the Password box blank if you are using Windows security (integrated security). Conv20.exe makes sure that the values in the AttributeMap SQL table match the corresponding values in the default Sms_def.mof file. However, Conv20.exe does adapt to any customizations that you have made by parsing the version of Sms_def.mof file that the SMS site server currently uses.
 * 7) Restart the SMS services.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Systems Management Server 2.0 Service Pack 5.



MORE INFORMATION
Conv20.exe logs entries in the %SystemDrive%\Conv20.log file, and displays a dialog box as it progresses. The following error messages are typical when you run this tool; you can ignore them:

Could not validate database.

SQL Msg #15511> Default bound to column.

This fix significantly increases the number of MIF files that are processed per minute. Use the Performance Monitor &quot;SMS Inventory Data Loader&quot; object and the &quot;MIFs Processed/minute&quot; counter to see how many MIF files are processed per minute on an SMS site server.

Keywords: kbqfe kbhotfixserver kbhardware kbsms200presp5fix kbbug kbfix KB328937

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.