Error compiling policy file on W2K Pro SP 4 1

[crobin1]

Out of 28 Windows 2000 Professional SP 4 PCs, I have one that will not install the SMS 2003 Advanced Client. The only error I can find in the log files is the following:

Error 25140 Setup was unable to compile the file PolicyDefaults.mof. The error code is 8004100E

As far as I've been able to tell, the settings on that PC are the same as every other PC.

I've searched several Web sites including Microsoft's, but haven't come up with anything. Anyone here have any ideas?

 

[jefius]

I have the same problem does somebody have a solution for it?

 

[tbrennans]

check the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Wbem\Scripting
The default namespace value should have the value data of root\cimv2.


if thats not it I would guess wmi has issues.

 

[tbrennans]

If a local WMI operation fails with an unexpected error code or you cannot start the WMI Control, make sure the local WMI service is running. Save the following code in a .VBS file and then run that script from the command prompt :

Set Svc = GetObject ("winmgmts:root\default")

If the script succeeds, the WMI service is working and is probably not the cause of the problem.

If the script fails, verify that the namespace specified in the script is a valid namespace. The sample script attempts to connect to the root\default namespace. If this namespace does not exist, you will likely get the error WBEM_E_INVALID_NAMESPACE (0x8004100E).

What if the namespace exists, but the class you are trying to connect to does not? In that case, you might see one of the following error codes when trying to access that class:

• WBEM_E_NOT_FOUND ( 0x80041002)

• WBEM_E_OUT_OF_MEMORY (0x80041006)


Failure to connect to a class might also indicate that the WMI repository has become corrupted. In that case you might see one of these error codes:

• WBEM_E_INITIALIZATION_FAILURE ( 0x80041014 )

• WBEM_E_CRITICAL_ERROR ( 0x8004100a )

• WBEM_E_FAILED ( 0x80041001)


If you believe the repository has become corrupted, your best course of action is to rebuild the repository.