SMS: "Cannot Save Query Result Format" Error

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

SYMPTOMS

When you try to create a new Query Result format using the Systems Management Server Administrator program, you may receive the following error message:

   Cannot save Query Result format.

CAUSE

This error message occurs when an invalid character, such as a single quotation mark (') is used in any of the fields other than the Description field during MIF form creation. These fields become the table names within the Systems Management Server database. The only character, other than actual letters and numbers, that SQL Server allows for inclusion of table names is the underscore character (_).

WORKAROUND

To work around this problem, perform the following steps:

1. Use the MIF Generator to re-create the .xnf file without using any illegal characters.

2. Ensure that all existing copies of the old .xnf file are replaced with the newly created .xnf file. For more information, see the following article in the Microsoft Knowledge Base:

         ARTICLE-ID: Q131614
         TITLE     : Propagating MIF Entry Forms (XNF files) to SMS Clients
   
   

3. Delete the corresponding .mif and .sev files from all clients in the Ms\Sms\Noidmifs directory.

4. Open the Systems Management Server Database Manager. On the Tools menu, click Delete Group Classes.

5. Select Personal Computer and click OK.

6. Select the group representing the offending MIF information and click OK to delete this group from the database.

7. Have the clients re-enter any of the fields and save the new MIF.

8. Have the clients log on again or otherwise run the Smsls.bat file to take inventory and send the new MIF information to the server.

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server versions 1.0, 1.1, and 1.2. A supported fix is now available for version 1.2 only, but it has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.