When you install DPM 2010, right after the prerequisites verification you receive an error “Verify that Windows Management Instrumentation (WMI) Service is running. if…
in order to fix this issue, you need to reinstall WMI , this is how to do it
From an elevated Command Prompt
1. Disable and stop the WMI service.
sc config winmgmt start= disabled
net stop winmgmt
2. Rename the Repository folder under C:\Windows\System32\wbem to Repository.old
3. Run the following commands.
Winmgmt /salvagerepository %windir%\System32\wbem
4. Re-enable the WMI service and then reboot the server to see how it goes.
sc config winmgmt start= auto
This question came from Momo my DBA Friend, I have SCOM 2012 installed , what kind if maintenance Plan I need to run, Momo meant DBCC check, Index rebuild etc..
my answer nothing , you don’t need to run any maintain on SCOM DBs and the reasons are the following :
1- there is a rule name “Optimize Indexes” that execute a daily database maintenance it calls a Store Proc name “p_OptimizeIndexes” , by default the rule runs once a day at 2:30 AM , you can change the time (Configuration Tab,View DS ),
the index optimization Store Proc has the following
There is always something new , in the System Center area, there is a new SQL Server Analysis Services released early January 2014
it supports the following :
1- SCOM 2012 and later
2- Virtualized SSAS instances
3- Clustered SSAS instances
Download the MP
From Microsoft web site :
1- SSAS Instance monitoring
2- SSAS Database monitoring
3- SSAS Partition monitoring
Health Rolls Up :
a well detailed article please visit Oleg’s Blog
The Issue started with the ldm threshold reached and we had to delete all the protection group and recreate then.
Due to this mass deletion of protection group. The pressure on the garbae collection job mounted as it had to delete lot of objects from sql database.
Now whenever the garbage collection job ran it increased the size of the tempdb which would consume almost all the space on the drive.
In order to find what query the garbage collection gets stuck we used this script.
the result Was:
Ran the garbage collection job along with this script and waited for tempdb to grow abnormally.
We got following output from the powershell script.
to fix the issue :
A huge credit to Abhishek from the DPM Support Team
this is just a snapshots , from the resolution , if you get this error , don’t try to run the query on your own, i really recommend to contact MSFT support