Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Status When Process is Not Running as 'Not Running' for RPC returns 'Down'

We have a memory issue with the Windows Modular Installer service but it's not always running and by the way the WMI is corrupted on this server. Lucky me right?

With WMI I know for a service I want to monitor and set the 'Status When Process is Not Running' to 'Not Running' instead of 'Down' so that I don't get a red dot on my dashboard.

I do the same thing with RPC and it's reporting as 'Down'.

Am I not doing something right here?

thanks

Find more posts tagged with

Accepted answers

Petr.Vilem

No, you just hit the bug in product. It is internally tracked as SAM-3803. Thank you for bringing this to our attention.

All comments

Petr.Vilem

No, you just hit the bug in product. It is internally tracked as SAM-3803. Thank you for bringing this to our attention.

arachenta

Great. Thank you for replying, Do you know a work around in the meantime?

aLTeReGo

The workaround in the meantime would be to change the fetching method for this component to use WMI rather than RPC. This would however entail repairing WMI.

winmgmt /verifyrepository
If the result is shown as inconsistent, go to step 2
winmgmt /salvagerepository
winmgmt /verifyrepository - to check again wmi repository had been repaired successfully

To fully rebuild the WMI Repository follow these steps:

Disable and stop the winmgmt service
Remove or rename C:\Windows\System32\wbem\repository
Enable and start the winmgmt service
Open a CMD prompt as Administrator
In the CMD prompt Navigate to C:\Windows\System32\wbem\
Run the following command:

‘for /f %s in ('dir /b *.mof') do mofcomp %s’Note: This will take a minute or so to complete.

Now run the command:

‘for /f %s in ('dir /b en-us\*.mfl') do mofcomp en-us\%s’

Restart the Data Collector service

Lastly, open PERFMON to verify that all counters can be loaded. If PERFMON generates a popup error, please follow this Microsoft KB to fix it:

http://support.microsoft.com/kb/2554336/en-us

arachenta

aLTeReGo thank you for this. I brought this up with an systems engineer and since this server is clustered, he's afraid it won't rejoin the cluster. I don't know how true that is, have you seen instances of that happening? We want to monitor the box properly but the bigger risk is if it won't rejoin. Thanks