Receiving Unknow Error in Events Log

Is anyone familiar with the following event that shows up twice every hour in my event log?

Error Opening MainTaskDataReader Incorrect syntax near ')'. Incorrect syntax near ','. Incorrect syntax near ')'. Incorrect syntax near ')'. Incorrect syntax near ','. Incorrect syntax near ')'. Statement(s) could not be prepared.

Find more posts tagged with

event_log_statement

Accepted answers

All comments

rubber_jonnie

Orion V8.1.3 with all hotfixes applied, SQL 2005 Express all on the one box.

We also get these entires every hour.

I've been told the fix is to upgrade to version 8.5, but this isn't a fix in my book and is extremely annoying since it worked perfectly for quite some time until recently.

I've also been told, and seen on Thwack, that it can be safely ignored. I still don't like seeing it.

Our supplier did ask me 'Did you delete anything', which of course we had due to server moves/upgrades, but I would be quite dismayed if something as routine as deleting a node or interface would do this.

We also have an instance on another site of Orion 8.0, which has seen far more deletes in it's lifetime and has never generated this error.

Please help if you have seen this and fixed it.

Network_Guru

I did a search for "Incorrect syntax near" and came up with this post, which sounds like a similar problem.
This may fix it for you.

I agree, upgrading to a newer release is not a fix, when it worked fine before.
V8.5.1 also has bugs (memory leaks, etc.) so "upgrading" is not really an option for me.
I need stability more than I need new features.

I wish SW would release a SP for V8.1 which would address all these known issues which were fixed in 8.5.1.

rubber_jonnie

Before I saw your reply, I'd just re downloaded the V8.1 hotfixes and reapplied all of them, and I'm currently watching over the events log to see if the errors come back, which they haven't yet. I'll post again when I've given it sufficient time to see the outcome.

Incidentally I had another issue at around the same time, which I thought at first may not be related.

A server had been decomissioned so I needed to remove the switchport from monitoring, so deleted it using Orion System Manager.

I looked the next day, and the interface was still present on the website, but did not exist in Orion System Manager.

I decided to re add the interface, then delete again. When I re added it, the website showed 2 instances of the same interface, and the Orion System Manager only showed 1 instance.

I looked at the table in the database (dbo.interfaces) and sure enough there were 2 entries for the same interface.

I finally fixed it by adding the interface again, waiting about 2 hours and then deleting again, follwed by a reboot. Since then all has been well, but it became apparent the Main TaskDataReader error was still there, so it was then I downloaded and re ran the hotfixes.

I suspect if it is going to error again it will do so within the next 20 minutes or so, so I'll post again shortly.

Network_Guru

I'm running V8.1 and did have those errors in my event log.
I ran the fix in the post I mentioned and the errors cleared.
I have not seen them since.

rubber_jonnie

It has now been over an hour since I reapplied all of the V 8.1 hotfixes, having first removed a spurious interface from Orion, and I have not yet had a repeat of the MainTaskDataReader errors that normally come in pairs once an hour.

I still think it is too early to say 'This is fixed', so I will post again tomorrow when I do my morning checks to see if all is still well.

rubber_jonnie

Having just logged on to do my daily check routine, I can see that the MainTaskDataReader error is now gone.

It has now been 18 hours since I removed the spurious interface I had and reapplied the v8.1 hotfixes, and where my log would normally be full to the brim with these errors it is completely clear.

I can't say for certain that the spurious interface was part of the problem, but I can say that since I downloaded a fresh copy of the hotfixes and reapplied, the errors are now gone.

It may not work for you, but it is certainly worth a try.