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

NCM using all cpu resources

Hi,

We've been having an issue with NCM's ConfigMgmtJob.exe process sucking up all available cpu process on the server it runs on. It happens every day when a job to restart a specific (different) windows server runs at 6:00am. This job has been running for a while with no issues before a couple weeks ago. The problem started shortly after I turned up a job to download all the switch configs (approximately 38 of them) on a nightly basis, but that job didn't affect the cpu and ran at 2:00 am, taking approximately 5 minutes. To see if they were related, I turned off that job yesterday, and the problem persists. The windows server reboots like it should - the job log says the job runs - doesn't take long, but as soon as the job fires off, the cpu pegs at 100% and stays there until I get into the NCM server and kill the configmgmtjob.exe process.

The NCM server (Windows 2003, SP2) is running NCM 5.1, but the database is a SQL database that resides on a different server. I also have IPMonitor (v10.0) running on the same server as NCM. Any ideas where to look for the problem would be appreciated.

Thanks,

Jim

Find more posts tagged with

Accepted answers

All comments

ynchan38

I have the same problem. After I kill the job, it is running fine for a while and then the problem return. I am also having the DB running on an separate SQL2005 server. NCM version is 6.0.

fcaron

Similar issue in this thread. Might be related:

I recommend contacting support.

grodech

In reviewing the job with Tech Support, we found another job that was firing off at 6:00am as well which turned out to be the job that was hogging the cpu. We've turned off the job and will see what happens...