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

strange error events

eric

There are lots of strange error events in my Orion event.

Who can tell me where are these error event come from?

Thanks a lot.

event_0522p.jpg

Find more posts tagged with

Accepted answers

All comments

Mithrilhall

Are all of these errors related to one specific node or multiple? What are/is the node?

BryanBecker

I get a similar error "Error Opening MainTaskDataReader A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) ".

BB

eric

I don't know which node?

I couldn't find which nodes caused this error events?

eric

Hi BB ,

how do you solve this?

could you give me a hand?

thanks

jtimes

Those errors are comming from the polling engines trying to update records in the database that are currently in a rocord lock state, you wouldn't happen to have nodes on multiple polling engines would you?

The "ID #" int the message is the node or interface ID in the table.

I've seen this one time when the DB is running behind comitting information from memory to disk very long diskque length, and a big outage was occuring (like a spanningtree event) and I am in the DB (Enterprise Manager) monkeyin around in write mode... Thats only my QA Orion though...

support

The MainTaskDataReader event is just informing you that a DB timeout has occurred. This could happen for many reasons and should not be a concern unless the application is not performing as expected.

One suggestion would be to try changing the Collation order from case sensitive to case insensitive in the SQL Manager

eric

Hi John Times,

Thanks for your help.

Actually, there also be a standby engine in the network.

eric

support,

Thanks.

And how to change the Collation order from case sensitive to case insensitive in the SQL Manager ?

BryanBecker

The MainTaskDataReader event is just informing you that a DB timeout has occurred. This could happen for many reasons and should not be a concern unless the application is not performing as expected. One suggestion would be to try changing the Collation order from case sensitive to case insensitive in the SQL Manager

How exactly do you change this?

BB

jtimes

I'm not even going to try to play with this, but here is the link to the changing SQL Collation...

http://msdn2.microsoft.com/en-us/library/ms144260.aspx