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

Solarwinds Job Scheduler and Orion Module Engine Keep Stopping

I have opened support case# 105136. Both services keep stopping/restarting since 9.5 upgrade. I have reinstalled everything multiple times. Ran through the config wizard. Re-installed .Net....nothing is resolving the issue. Also, IPAM scans haven't run for over 2 weeks now (since upgrade).

7/13/2009 5:16 AM

IPAM Service [CRP676] is unable to communicate with Job Engine. Network Scanning is offline.

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date:  7/13/2009
Time:  7:36:27 AM
User:  N/A
Computer: CRP676
Description:
EventType clr20r3, P1 swjobschedulersvc.exe, P2 1.3.0.143, P3 49dfbdf0, P4 system.data.sqlserverce, P5 3.5.1.0, P6 486140a5, P7 df, P8 17, P9 system.data.sqlserverce.sqlce, P10 NIL.

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date:  7/13/2009
Time:  7:36:37 AM
User:  N/A
Computer: CRP676
Description:
EventType clr20r3, P1 solarwinds.businesslayerhost.exe, P2 9.5.0.2009, P3 4a096db1, P4 solarwinds.npm.businesslayer, P5 9.5.0.2152, P6 4a42507a, P7 339, P8 11c, P9 exception, P10 NIL.

Find more posts tagged with

Accepted answers

FormerMember

pduxbury, make sure you've cleared the read-only attribute from the newly copied .sdf file, otherwise you'll run into problems.

Scott, you had asked about diagnostics. You'll just want to run the 'Orion Diagnostics' application under 'SolarWinds Orion\Documentation and Support' from the start menu.

All comments

Capt._Obvious

Do the engine ID's in your Engines Table Coincide with the EngineID's referenced in your nodes table?

If there are any negitave integers or "rogue' engine Id's this behavior can occur.

scott.skalny

I just verified that all entities have an EngineID value of either 1, 2 or 3.

bshopp

And you both are running the latest SP2?

JosephRLee

I am experiencing the exact same thing both my two pollers. They ran smooth on 9.5 SP2 for a week or so and then one day started erroring out on the same two services. DMP files even filled the boot drive and crashed the system. I have done everything short of a reinstall/repair due to the nightmare of install to begin with.

I did open up a ticket with Solarwinds.

scott.skalny

yes, I am running SP2 on all 3 polling engines. I have not performed an uninstall, but I've done several repairs and gone throught the Configuration Wizard. Since the re-installs I also have the problem of no wireless APs showing up in the Wireless view.

pduxbury

i am also having this issue with a newly installed system.

i found that if i stop the job scheduler service i can successfully start the orion module service and it stays up. as soon as i start the job scheduler the orion module service stops.

i have tried to replace the file jobengine35.sdf located in C:\Documents and Settings\All Users\application data\SolarWinds\JobEngine\Data with the blank one but this only then stops the job scheduler from starting.

does anyone have any ideas ?

thanks

paul

FormerMember

pduxbury, make sure you've cleared the read-only attribute from the newly copied .sdf file, otherwise you'll run into problems.

Scott, you had asked about diagnostics. You'll just want to run the 'Orion Diagnostics' application under 'SolarWinds Orion\Documentation and Support' from the start menu.

scott.skalny

Casey,

Thanks so much for the clear read-only suggestion. I had replaced the JobEngine35.sdf about a week ago but never cleared read-only attribute. The services have not restarted in over and hour, and with a restart of the IPAM process, I am not successfully scanning subnets again. This issue seems to be resolved.

-Scott