Twice now on a production FIM server, WMI got corrupted in some fashion preventing us from running Scheduled jobs that start run profiles on MAs. I know others have experienced the same issues. What are some things people are doing in attempts to prevent WMI from becoming corrupt on FIM servers, if anything?
First issue: ILM namespace disappeared or became corrupt
Resolution: - Open a command window
- Browse to the installation\bin folder (default: C:\Program Files\Microsoft Identity Integration Server\Bin)
- Run "mofcomp mmswmi.mof" to recompile the mof file and add the namespace to wmi (source: http://social.technet.microsoft.com/Forums/en/identitylifecyclemanager/thread/2a4c8f42-4123-4297-aa35-29a96956946e)
Second Issue: WMI repository became corrupt
Failed to initialize all required WMI classes.
Win32_Processor. WMI: Invalid namespace
Win32_WMISetting. WMI: Invalid namespace
Win32_OperationSystem. WMI: Invalid namespace
Resolution: -
Stop the WinMgmt service. Then run the following commands:
1 - "C:\WINDOWS\system32\wbem> for /f %s in ('dir /b *.dll') do regsvr32 /s %s" (without quotation marks)
2 - "C:\WINDOWS\system32\wbem\Repository>for /f %s in ('dir /b *.dll') do regsvr32 /s %s" (without quotation marks)
3 - Rename the existing C:\WINDOWS\system32\wbem\Repository to C:\WINDOWS\system32\wbem\OLDRepository.
4 - Start WinMgmtand allow WBEM to rebuild the repository again in C:\windows\system32\wbem\repository.
5 - Stop Service via Services snap-in or net stop winmgmt, and register the files in the rebuilt c:\windows\system32\wbem\repository folder
6 - Rebuild ILM namespace
7 - Issue should be be resolved.