I did some research on your situation, and this is what I found.
It seems that the WMI namespace root\cimv2 failed to create on installation. You can verify manually by opening wbemtest and trying to connect to namespace root\cimv2. If you get "namespace not found" then that is the issue.
This problem can usually be fixed by forcing an auto-recover of the default information stored in the repository.
- open a command window (start > cmd.exe) - type "net stop winmgmt" - type "cd %windir%\system32\wbem" - type "ren repository repository.old" (or alternatively delete it)
Then try to connect to root\cimv2 with wbemtest again. It may take a minute or so to complete while WMI rebuilds the database.
After that, you can re-run ADAP with the following command and after a minute or so check the event log again to verify you don't get the same errors.
- from %windir%\system32\wbem, run "wmiadap.exe /f"
and this information can be found on the following website.
Thanks Ramona,
Unfortunately none of this worked. The same namespace error occurs.
The message is
"Failed to load MOF C:\WINDOWS\SYSTEM32\WBEM\VSS.MFL while recovering repository file."
This message appears for all files trying to load
All the indications in the logs are that the files will not load, - syntax errors on particular lines reported. Does this mean that the original preinstall was corrupt?
The following are the original messages when the preinstall was started:
Message 1
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 80070006 from line 44 of d:\srv03rtm\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.
Message 2
The run-time environment has detected an inconsistency in its internal state. This indicates a potential instability in the process that could be caused by the custom components running in the COM+ application, the components they make use of, or other factors. Failed to CoCreate EventSystem object.
Process Name: setup.exe
Error Code = 0x80040206 : An unexpected internal error was detected
COM+ Services Internals Information:
File: d:\srv03rtm\com\complus\src\comsvcs\events\lcedisp.cpp, Line: 132
Comsvcs.dll file version: ENU 2001.12.4720.0 shp
Message 3
Volume Shadow Copy Service error: Writer with name WMI Writer and ID {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} attempted to subscribe during setup.
The above errors seem to indicate when/where the problem occurred. Then all of the .MOF files fail to load. Unfortunately I am not sure if this is a Windows error or a hardware problem, although my feeling is that its Windows and/or the original preinstall/image.
Sorry this is so long winded. Any help would be appreciated.
Ramon Ray
89 Posts
0
July 22nd, 2004 13:00
Hi
I did some research on your situation, and this is what I found.
It seems that the WMI namespace root\cimv2 failed to create on installation.
You can verify manually by opening wbemtest and trying to connect to
namespace root\cimv2. If you get "namespace not found" then that is the
issue.
This problem can usually be fixed by forcing an auto-recover of the default
information stored in the repository.
- open a command window (start > cmd.exe)
- type "net stop winmgmt"
- type "cd %windir%\system32\wbem"
- type "ren repository repository.old" (or alternatively delete it)
Then try to connect to root\cimv2 with wbemtest again. It may take a minute
or so to complete while
WMI rebuilds the database.
After that, you can re-run ADAP with the following command and after a
minute or so check the event log again to verify you don't get the same
errors.
- from %windir%\system32\wbem, run "wmiadap.exe /f"
and this information can be found on the following website.
http://www.mcse.ms/archive68-2004-1-290661.html
There is also a Microsoft Kb article with a solution also, it does refrence windows 2000, but it should provide a solution to your situation.
The kb article # is 26881
ENGIT
2 Posts
0
July 26th, 2004 01:00
Unfortunately none of this worked. The same namespace error occurs.
The message is
"Failed to load MOF C:\WINDOWS\SYSTEM32\WBEM\VSS.MFL while recovering repository file."
This message appears for all files trying to load
All the indications in the logs are that the files will not load, - syntax errors on particular lines reported. Does this mean that the original preinstall was corrupt?
The following are the original messages when the preinstall was started:
Message 1
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 80070006 from line 44 of d:\srv03rtm\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.
Message 2
The run-time environment has detected an inconsistency in its internal state. This indicates a potential instability in the process that could be caused by the custom components running in the COM+ application, the components they make use of, or other factors. Failed to CoCreate EventSystem object.
Process Name: setup.exe
Error Code = 0x80040206 : An unexpected internal error was detected
COM+ Services Internals Information:
File: d:\srv03rtm\com\complus\src\comsvcs\events\lcedisp.cpp, Line: 132
Comsvcs.dll file version: ENU 2001.12.4720.0 shp
Message 3
Volume Shadow Copy Service error: Writer with name WMI Writer and ID {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} attempted to subscribe during setup.
The above errors seem to indicate when/where the problem occurred. Then all of the .MOF files fail to load. Unfortunately I am not sure if this is a Windows error or a hardware problem, although my feeling is that its Windows and/or the original preinstall/image.
Sorry this is so long winded. Any help would be appreciated.