Troubleshooting: Fixing 'Invalid Data' Error When Importing Sms_def.mof in Configuration Manager

Table of Contents

This article provides a solution to an issue encountered in Microsoft System Center 2012 Configuration Manager where importing the Sms_def.mof file results in an “Invalid Data” error message. This problem prevents users from customizing their hardware inventory, a crucial aspect of system management within Configuration Manager. Understanding and resolving this error is essential for maintaining accurate and comprehensive hardware inventory data.

Symptoms¶

When attempting to import the Sms_def.mof file within System Center 2012 Configuration Manager to tailor hardware inventory settings, the process fails. Instead of successful import, the system displays an error message indicating that the file contains invalid data. This issue directly hinders the ability to customize hardware inventory, potentially leading to incomplete or inaccurate information about managed devices within the Configuration Manager environment. Administrators may find themselves unable to add, modify, or remove hardware inventory classes and properties as intended.

This error typically arises during the initial stages of importing the Sms_def.mof file. The Configuration Manager console will not proceed with the import process and will halt, displaying the “Invalid Data” error prompt. This behavior is consistent and repeatable whenever an attempt is made to import the problematic Sms_def.mof file. The impact of this symptom is significant, as it directly blocks the desired hardware inventory customization, potentially affecting reporting, compliance, and overall device management capabilities.

Resolution¶

To effectively address the “Invalid Data” error when importing Sms_def.mof, the primary step is to verify the integrity of the MOF file itself. This involves using a built-in Windows utility called mofcomp.exe (Managed Object Format Compiler). This tool is designed to parse and check the syntax and structure of MOF files, identifying any potential corruption or errors that might render the file invalid.

The resolution process involves the following steps:

1. Open Command Prompt: Access the Command Prompt with administrative privileges. This ensures that you have the necessary permissions to execute the mofcomp.exe command and access the file system. You can typically do this by searching for “cmd” in the Windows Start Menu, right-clicking on “Command Prompt,” and selecting “Run as administrator.”

2. Navigate to the MOF File Directory: Using the cd command in the Command Prompt, navigate to the directory where the Sms_def.mof file is located. For example, if the file is saved in C:\MOF_Files, you would type cd C:\MOF_Files and press Enter. It is crucial to be in the correct directory for the command to find and process the Sms_def.mof file.

3. Execute the Integrity Check Command: Once you are in the correct directory, execute the following command:

   mofcomp.exe -check <YourMOFName>.mof
   

   Replace <YourMOFName>.mof with the actual filename of your Sms_def.mof file. For instance, if your file is named Sms_def.mof, the command would be:

   mofcomp.exe -check Sms_def.mof
   

   This command instructs mofcomp.exe to perform a syntax and integrity check on the specified MOF file without attempting to compile or register it. The -check parameter is critical for simply validating the file’s structure and identifying errors.

4. Analyze the Output: After executing the command, mofcomp.exe will analyze the Sms_def.mof file and provide output in the Command Prompt window.

   • If the MOF file is valid: mofcomp.exe will typically complete without displaying any error messages. This indicates that the file structure is correct and that the “Invalid Data” error during import is likely not due to file corruption. In this case, further troubleshooting might be needed, focusing on the Configuration Manager import process or potential permission issues.

   • If the MOF file is invalid: mofcomp.exe will display error messages indicating syntax errors, structural problems, or other issues within the Sms_def.mof file. These error messages are invaluable in pinpointing the exact location and nature of the corruption or invalid data. Carefully review these error messages as they often provide clues to the specific lines or sections of the MOF file that are problematic.

5. Correcting Invalid MOF File (If Necessary): If mofcomp.exe -check identifies errors in the Sms_def.mof file, you will need to correct these errors. This might involve:

   • Manual Editing: Open the Sms_def.mof file in a text editor (like Notepad or Notepad++) and carefully review the lines indicated in the mofcomp.exe error messages. Look for syntax errors, typos, missing semicolons, incorrect data types, or any deviations from the expected MOF file structure. MOF syntax can be quite strict, so even minor errors can cause validation failures.

   • Restoring from Backup: If you have a backup copy of a known-good Sms_def.mof file, consider restoring it. This is often the quickest way to resolve corruption issues, especially if the errors are extensive or difficult to pinpoint manually. Ensure that the backup file is compatible with your Configuration Manager environment.

   • Recreating the MOF File: In some cases, it might be necessary to recreate the Sms_def.mof file from scratch, especially if the corruption is severe and you lack a reliable backup. Refer to the Configuration Manager documentation or relevant resources for the correct structure and syntax of the Sms_def.mof file for your version of Configuration Manager.

6. Re-run Integrity Check: After making corrections to the Sms_def.mof file, re-run the mofcomp.exe -check command to verify that the errors have been resolved and that the file now passes the integrity check. Repeat the editing and checking process until mofcomp.exe completes without errors.

7. Attempt Import Again: Once the Sms_def.mof file passes the integrity check, attempt to import it into Configuration Manager again. Navigate to the hardware inventory settings within the Configuration Manager console and initiate the import process for the corrected Sms_def.mof file.

By meticulously following these steps, you should be able to identify and resolve issues related to MOF file integrity, effectively addressing the “Invalid Data” error and enabling successful import of the Sms_def.mof file for hardware inventory customization in Configuration Manager.

More Information¶

Understanding the context and underlying technology behind MOF files and the mofcomp.exe utility is crucial for effectively troubleshooting issues like the “Invalid Data” error. MOF files, or Managed Object Format files, are text-based files used by the Windows Management Instrumentation (WMI) system. WMI is a core component of Windows that provides a standardized way to manage and monitor system resources and devices.

Role of MOF Files in WMI and Configuration Manager:

• Defining WMI Classes: MOF files are primarily used to define and register WMI classes. These classes represent manageable objects within the Windows environment, such as hardware components, software applications, operating system settings, and more. They specify the properties and methods associated with these objects, providing a structured way to access and manipulate system information.

• Hardware Inventory Customization in Configuration Manager: In the context of Configuration Manager, Sms_def.mof plays a pivotal role in defining the hardware inventory data collected from managed clients. Configuration Manager leverages WMI to gather hardware and software information. The Sms_def.mof file allows administrators to extend and customize the default hardware inventory by defining new WMI classes or modifying existing ones. This enables the collection of specific data points that are relevant to an organization’s unique needs, going beyond the standard hardware inventory information.

• Compiling MOF Files with mofcomp.exe: The mofcomp.exe utility is the MOF compiler. Its primary function is to parse MOF files and compile them into the WMI repository. The WMI repository is a central database that stores WMI class definitions. When you run mofcomp.exe on a MOF file, it reads the MOF file, checks its syntax, and if valid, registers the defined WMI classes and their associated information into the WMI repository. This makes the new or modified WMI classes available to WMI clients, including Configuration Manager.

Why “Invalid Data” Error Occurs with Sms_def.mof:

The “Invalid Data” error when importing Sms_def.mof typically points to issues within the file’s structure or syntax that prevent mofcomp.exe from successfully parsing and compiling it. Common causes include:

• Syntax Errors: MOF syntax is strict and requires precise formatting. Even minor typos, missing semicolons, incorrect keywords, or improper use of data types can lead to validation errors.

• Structural Issues: Problems in the logical organization of the MOF file, such as incorrect class definitions, improper inheritance, or inconsistencies in property definitions, can also result in errors.

• File Corruption: Although less frequent, the Sms_def.mof file itself might become corrupted due to file system errors, incomplete downloads, or improper editing.

• Compatibility Issues: In some cases, a Sms_def.mof file designed for a different version of Configuration Manager or WMI might not be fully compatible with the current environment, leading to errors during import.

Best Practices for Working with Sms_def.mof:

• Backup Before Modification: Always create a backup copy of the original Sms_def.mof file before making any modifications. This allows for easy restoration if errors are introduced or if you need to revert to the default configuration.

• Use a Text Editor for MOF Files: Edit MOF files using a plain text editor like Notepad or Notepad++. Avoid using word processors like Microsoft Word, as they can introduce hidden formatting characters that can corrupt the MOF file.

• Validate with mofcomp.exe -check Frequently: After making changes to the Sms_def.mof file, use the mofcomp.exe -check command to validate its integrity before attempting to import it into Configuration Manager. This helps catch errors early and prevents issues during the actual import process.

• Refer to Official Documentation: Consult the official Microsoft Configuration Manager documentation and WMI documentation for detailed information on MOF file syntax, structure, and best practices. This ensures that you are following the correct guidelines when customizing your Sms_def.mof file.

• Test Changes in a Lab Environment: Before deploying modified Sms_def.mof files to a production Configuration Manager environment, thoroughly test them in a lab or test environment. This helps identify any unintended consequences or errors before they impact your live system.

By understanding the role of MOF files, the functionality of mofcomp.exe, and the common causes of “Invalid Data” errors, administrators can effectively troubleshoot and resolve issues related to Sms_def.mof import in Configuration Manager, ensuring accurate and customized hardware inventory collection.

---

Have you encountered this “Invalid Data” error when importing Sms_def.mof? What steps did you take to resolve it? Share your experiences and questions in the comments below!