- SQL Broker Service is not running
This is the most common cause why the Discovery Wizard keeps on running without showing any result. How to identify it and how to solve it, is to be found on these web pages:
- SPNs aren’t set correctly
SPNs need to be set correctly in order for the Discovery process to run properly. Sometimes they can get corrupted as time goes by. Check these postings how to go about it:
- Health Service Store on the RMS has gone corrupt
I have never seen this myself, but a person I know bumped into this issue. On his RMS the HealthService store (~:\Program Files\System Center Operations Manager 2007\Health Service State\Health Service Store\HealthServiceStore.edb) had gone corrupt. The file itself had grown to a size of +700 MBs and many log files were found as well. So he recycled it and afterwards all was fine again. I have contacted Microsoft about this issue and as it turns out, there is an issue with the Jet DB Engine, present on any kind of Windows Server OS. In order to solve this a hotfix has been released by Microsoft: http://support.microsoft.com/default.aspx?scid=kb;en-us;981263.
How to recycle it? Just stop the Health Service on the RMS, RENAME the folder ~:\Program Files\System Center Operations Manager 2007\Health Service State to (~:\Program Files\System Center Operations Manager 2007\Health Service State_OLD (so there is always a way back!!!) and start the Health Service again.
Thursday, August 5, 2010
Discovery Wizard is running for ever
When the Discovery Wizard is running for ever, there are multiple possible causes for it. This posting is about how to identify these causes and how to solve them.
Labels: Discovery Wizard