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
Store

Issues monitoring AD after dcpromo /forceremoval

Had a USN Rollback issue with one of our Domain Controllers. I managed to fix it by running the dcpromo /forceremoval, removing metadata and then promoting it to a DC again. All seems well and the DC is replicating correctly now.

The downside of all this is that rather than having the initial single error listed in SolarWinds I now have 15 or so. They all seem to be RPC calls to performance counters but I must admit that this is all somewhat new to me and every step I have tried seems to have fialed to make any change at all.

A thread here suggest wmiadap /F while others have suggested removing the repository directory and running wmimgmt /resyncperf but so far nothing has made a difference. I even ran wmidiag but have a feeling this is not really designed for server 2008 as it complains it cannot find some dll files but these exist in the system32 directory (whereas previously, from what I have read they used to be placed in system32\wbem).

The error I get on the counters is: "Bad input parameter. Category does not exist".

Does anyone have any help or some steps I can try to bring the monitoring back online?

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

It's likely the Windows Performance Counters have become corrupted. I recommend running "lodctr /R" from the command line of the server being monitored. This should rebuild the performance counters. If that doesn't resolve the issue try accessing these same counters using Perfmon.exe. If the counters don't exist in Perfmon.exe then APM will also be unable to monitor them. Your options at that point would be to contact Microsoft to determine why these counters are missing. As an alternative you could try monitoring these counters using WMI instead.

If the counters do show up in perfmon.exe with valid statistic information and you're still having a problem monitoring them with APM, I would recommend opening a case with support so we can troubleshoot this further.

talexander

Thanks for that. I ran what you suggested but there was no change.

I looked at perfmon and I can find all the keys listed under DirectoryServices counters so something is there but for some reason solarwinds is not seeing it. They are reporting figures as well and not just null values.

I will do as you suggest and open a case with solarwinds and see what happens

danielleh

talexander--

Would you please post back with the support ticket # and any answers you receive from support?

Much appreciated,
DH

talexander

Will do. Have been having issues trying to log the call through the support portal but we have phone support so will try that this afternoon.

Interestingly it looks as if the use of Win32_Perfrawdata_NTDS_NTDS is no longer used in server 2008 and instead the DirectoryServices counters need to be used. Wondering if there is a new version of the template that we need to download for APM. Could not find the KB article in english but Google translate handles it pretty well:

http://translate.google.co.uk/translate?hl=en&sl=zh-TW&u=http://support.microsoft.com/kb/946391/zh-tw&ei=Abm7TsKpCYuWOuv3jLQJ&sa=X&oi=translate&ct=result&resnum=2&ved=0CCoQ7gEwAQ&prev=/search%3Fq%3Dkb946391%26hl%3Den%26safe%3Dactive%26biw%3D1680%26bih%3D873%26prmd%3Dimvns

talexander

Seems to have allowed me to log the issue this morning so I must have been doing something wrong yesterday!

Case #285711