Select the product you need help with
Windows\WMI\Mofcomp fails with error 0X8004400cArticle ID: 2543399 - View products that this article applies to. SymptomsMofComp fails with error SYNTAX 0X8004400c: Expected property or method name. CauseThis error can occur if you are trying to add a dynamic entry for a property name that contains special characters such as parenthesis or brackets. For example, if you are using the registry provider to populate a WMI property based on a DWORD registry value named "Test(minimum)", MOFComp will fail with the error above. ResolutionTo allow MOFComp to successfully process the MOF, edit the MOF to escape the opening and closing parenthesis using a carat character ("^", shift-6 on an US-English keyboard). Note that you cannot use the backslash as an escape character for this sequence as you can for other special characters. Example: BAD:
GOOD:
More InformationMOF property names must be alphanumeric or underscore only: http://msdn.microsoft.com/en-us/library/aa394554(VS.85).aspx. This means that there must be a disconnect between the property name and the registry key it derives from. In the example above, the registry value GPSiteAssignmentRetryDuration(Hour) becomes GPSiteAssignmentRetryDurationHour. The backslash character (\) is the escape sequence for most queries and paths. For characters such as the backslash and quotes, it must be used. The carat character (^) is the escape sequence for instances of classes and other derived data. There are other special characters, such as curly brackets ({}) can also use this escape sequence. \( and \) are not legal. MOFComp will not throw an error on an unescaped character. It simply reports a null value. This is by design. Common errors:
1. Illegal character in the property name results in this error:
2. An illegal character in the instance properties throws this error:
3. Attempting to use backslash rather than a carat results in this error
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.Properties |


Back to the top








