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

Event Log Error 4001

Running NCM ver. 6.0

Every now and then i get an error in the event log -

Event Type: Error
Event Source: NCMSyslogService
Event Category: None
Event ID: 4001
Date:  8/8/2010
Time:  12:54:02 PM
User:  N/A
Computer: ********

Description:
Service was unable to open new database connection when requested.
Exception Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Connection string - Data Source=*******;Initial Catalog=Orion-ConfigMgmt;User ID=SolarWindsCM;Password=*******;Connect Timeout=20;Load Balance Timeout=120;Application Name="Orion NCM Syslog Service";Workstation ID=*******

The problem is that it seams as if when the error occures NCCM will not try to connect again. It just cease to function. Is there a fix for this error? Some sort of configurtstion that can be modified?

Thanks

Find more posts tagged with

Accepted answers

All comments

christineb

Hey Cmiller - If you could open a support ticket on this we can look into it a bit more.

--Christine

skittles

Was this resolved? I have had the same error, NPM version 10.1.1

Thanks, Sharon

MarieB

Hi Sharon--

I checked our support logs and found a case where this error applied to NPM. Here was the solution from that case--give it a try and see if it will help you.

Note: this customer also had Orion NTA with the Syslog job stopping with an application hang.

If this doesn't work for you and you don't hear back, open a support ticket.

"We did the following for troubleshooting the issue with the syslog service stopping.

--Created a rule to discard informational and debug since there were so many coming in, they were causing backup to the database.

This also seemed to lighten the load on the memory being used. There are a lot of rules set up to write to files, so I suspect the memory may spike up. Keep an eye on that.

--We truncated the syslog table, reindexed it and compacted the database.

The warning messages in the event viewer probably does not have any direct bearing on the syslog server service stopping, but we will know tomorrow morning."

HTH,