I am scanning my nodes for several applications and several times in the results I have seen the following...
Status: Unassigned Failure reason: SchedulerError
What does SchedulerError mean and what is causing them?
Byron,
Some detailed information about your network/servers would better help us research your issue. In the meantime, I did find something you may want to try. The issue mentioned here is somewhat similar, to a degree, to your issue and may yield positive results.
------------------------------------------------------------------------------------------------------------------------------------------------
The following is the workaround if you have a job scheduler service that keeps stopping and starting in the Orion Service Manager and causes the following error in the event viewer: This is due to the Job Engine database file is corrupted or grown too large: EventType clr20r3, P1 swjobschedulersvc.exe, P2 1.1.0.238, P3 486c94d4, P4 system.data.sqlserverce, P5 9.0.242.0, P6 458ab5e5, P7 145, P8 7b, P9 system.data.sqlserverce.sqlce, P10 NIL.
-or-
C:\Documents and Settings\All Users\Application Data\SolarWinds\JobEngine\Data\JobEngine.sdf
JobEngine.sdf
If this does not help, please submit a ticket and we'll do what we can. Thanks.
What detailed information about my network/servers would be of help?
I didn't see the log that you reference anywhere on either of my polling systems. How large is too large for that file?
Also, if it's possible for that file to get too large wouldn't it make sense to have the system watch this and somehow auto-resolve the issue on it's own versus just letting the system break?
Size isn't really an issue, but it does occasionally get corrupt. The steps posted are for Job Engine v1 - for APM v4.x, you'll want to reinstall Job Engine v2.Your best bet is to open a support ticket - then we can investigate the problem more thoroughly.
www.solarwinds.com/.../
Hi Byron--
You likely know this so apologies for the repeat.
When you open a support ticket, could you:
--Reference this thread to Support.--Post back here with a case number.--Post any solutions you get from Support.
Many thx,
M