Hi,
I did battle a little bit longer with that stuff now after getting the event log flooded with messages from cqvSvc.exe "Initialization failed". Also the health.xml was no longer upgraded.
Since this happened after an unexpected power outage while powering up and there was also an error with accessing the Repository folder I decided to stop wmimgmt service, delete the folder and reboot the server.
This fixed another behavior (my Scaleo Home Server could not start the Intel Hardware Monitor any more), but the warning generated by cqvSvc.exe in event log changed to Invalid class. Since I am not a programmer and using Dependency Walker on the exe file did not reveal anything for me, I attempted to uninstall and reinstall the service by the commands:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\installutil /u "C:\Program Files\Windows Home Server\cqvsvc.exe"
which should successfully remove the service
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\installutil /u "C:\Program Files\Windows Home Server\cqvsvc.exe"
for installing the service again.
Rebooted - and still the same warning.
So I decided to run another round in the WMI struggle by executing the following batch (which I had still from another situation, in which I needed to repair WMI on a production server) - put the lines into a file and save it with extension .cmd before executing it on your server - I do not guarantee it working and not destroying anything in your specific installation):
cd /d c:\temp
if not exist %windir%\system32\wbem goto TryInstall
cd /d %windir%\system32\wbem
net stop winmgmt
winmgmt /kill
if exist Rep_bak rd Rep_bak /s /q
rename Repository Rep_bak
for %%i in (*.dll) do RegSvr32 -s %%i
for %%i in (*.exe) do call :FixSrv %%i
for %%i in (*.mof,*.mfl) do Mofcomp %%i
net start winmgmt
goto End
:FixSrv
if /I (%1) == (wbemcntl.exe) goto SkipSrv
if /I (%1) == (wbemtest.exe) goto SkipSrv
if /I (%1) == (mofcomp.exe) goto SkipSrv
%1 /RegServer
:SkipSrv
goto End
:TryInstall
if not exist wmicore.exe goto End
wmicore /s
net start winmgmt
:End
pause
After this was completed, I rebooted and did see the warnings happening about 10 minutes long again, but finally after seeing two informations with source LoadPerf in the application log about removal and loading of performance indicators for WmiApRpl (WmiApRpl) the health.xml file in C:\Inetpub\Intranet\health was created again and no more warnings have been shown.
Best greetings from Germany
Olaf
