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

Exception thrown while calculating minimum poll lauch rate - Informational Message

jtimes

Has anyone seen this message before?

Running Orion V8.0.2 with all patches and hot fixes

Polls per second tuning is up to date on all polling engines also...

6/1/2007 05:46 AM

Exception thrown while calculating minimum poll lauch rate. Defaulting to 10 Detail- Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Found it on an SLX polling engine, that does not have any Custom Polling definitions. In fact I never deployed any in my production environment...

Windows Event viewer:

Event Type: Information
Event Source: OrionCustomPollingService
Event Category: None
Event ID: 0
Date:  06/01/2007
Time:  5:46:56 AM
User:  N/A
Computer: XXXXXXXXX
Description:
Exception thrown while calculating minimum poll lauch rate. Defaulting to 10 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 http://go.microsoft.com/fwlink/events.asp.

AND

Event Type: Information
Event Source: AlertingEngine
Event Category: None
Event ID: 0
Date:  06/01/2007
Time:  5:46:37 AM
User:  N/A
Computer: XXXXXXXXX
Description:
2007-06-01 05:46:37,878 [AlertCheckingThread] WARN Error - Error in UpdateRowsThatAreTriggered() - GetNetObjects
EXCEPTION STACK: --> Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. : .Net SqlClient Data Provider :    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
   at sw?.?();;;

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

Find more posts tagged with

Accepted answers

jtimes

I'll give it a shot this weekend.

Thanks again

All comments

mark_wiggans

One suggestion is to try increasing the SQL timeout in the SWNetPerfMon.DB file.

jtimes

Thanks Mark,

What would SW recommend? and should I perform the same action on all polling engines?

Current:

!
! Connection timeout in seconds
Timeout=20

!
! Database Command timeout in seconds
CommandTimeout=90

mark_wiggans

Just try one first by increasing them in 10 second intervals and see if you notice any differences. I know in the past some have bumped it up to 120

jtimes

I'll give it a shot this weekend.

Thanks again