nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Trap Service errors in Event Log

pguenther

My Solarwinds event log is being flooded by the following errors.

Event Type: Warning
Event Source: TrapService
Event Category: None
Event ID: 1023
Date: 3/5/2007
Time: 4:36:56 PM
User: N/A
Computer: VCOLSW01
Description:
An Exception was thrown while updating the varbinding information.
Error Detail-Prepared statement '(@TrapID bigint,@TrapIndex tinyint,@OID varchar(1000),@OIDName v' expects parameter @OIDName, which was not supplied.

For more information, see Help and Support Center at go.microsoft.com/.../events.asp.

Event Type: Information
Event Source: TrapService
Event Category: None
Event ID: 0
Date: 3/5/2007
Time: 4:36:56 PM
User: N/A
Computer: VCOLSW01
Description:
The OID Class could not open MIBs.cfg.
Copy the MIBs.cfg file to C:\Program Files\SolarWinds\Common to correct this problem
Could not use ''; file already in use.

For more information, see Help and Support Center at go.microsoft.com/.../events.asp.

I get a couple of thousand of these messages every day. I have tried reinstalling the MIB database to correct with no change. Can anyone help?

Find more posts tagged with

Accepted answers

All comments

mark_wiggans

Are you using an event forwarder?

Mark Wiggans
SolarWinds Support

pguenther

This is the Solarwinds event log on the Orion machine. So not it is not forwarding event logs anywhere, but there are machines that are forwarding its logs to this machine.

FormerMember

I'm getting a similar error that is causing the alerting engine to not send some alerts or resets. All my alerts are setup as advanced alerts and each is set to write to the event log & syslog, and send out a trap.

Event Type:       Warning
Event Source:    TrapService
Event Category: None
Event ID:           1023
Date:                5/1/2008
Time:                12:01:53 AM
User:                N/A
Computer:         ORION-POLLER
Description:
An Exception was thrown while updating the varbinding information.
Error Detail-Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

For more information, see Help and Support Center at go.microsoft.com/.../events.asp.

klomper2007

Any word on this issue? I'm still getting it while running version 9 with SP1.

dohc3si

We are getting the same error message and it practically locks up the box. We have the Trap Service stopped right now to alteast be able to use Solarwinds. Should I open a ticket?

dperdue

Yes, opening a ticket with support will allow us to work with you to get more information.

reheindel

Any response to this case? We are also seeing the same issue.

Thanks,

Bob

FormerMember

Same issue here.

Any solution yet?

Yesterday we moved our SQL DB to a dedicated server (before, it was located on the same host where SW Apps are, but we had performance issues so we decided to separate them).
We moved the DB, used the Database Configuration Utility to connect to the new server and the Orion Website came back online.

We are not receiving Notifications for events anymore.

FormerMember

Are you still seeing the issue with NPM 9.1?

reheindel

Yes we are seeing it in 9.1

Our environment:

APP Server-1 houses appliations: NCM 5.0 SP1 & NPM 9.1

DB Server 1 houses NCM database

DB Server 2 houses NPM database

FormerMember

Do you have any alert supressions in use on your alerts or do you have an inane amount of syslog packets coming in? This issue for us was that we were alerting via SNMP traps on certain syslog events, the problem was improperly formed syslog packets coming from different vendors. While the Toolset was able to handle the packets, Orion could not. This was fixed in 9.0 for the syslog piece. In the alert supression's we found one that was changed in the upgrade that caused the non-alerting; once we fixed that, everything worked again.

reheindel

Thanks for the response.

All syslog events are from a single vendor (well known network vendor), not more than 3-5 messages every 15 seconds.

We are not doing any event supression, but we do alerts based upon basic things like interface/device up/down.

We only do alerting within Orion (email notification, etc).