Orion Report Scheduler Issues

Do you by chance have McAfee on that server?  If so check the Virus Scan Console>View Log and see if it is blocking SMTP port 25 traffic.

when you look at your Scheduler are your jobs IDLE or have some other status?

when i first started using this Report Scheduler had a lot of problems too but what i ended up doing and its been running like a top since is these two things.

and i don't know if this will help your case, but i hope it might. its my two cents worth...so to speak.

1) any report which is going to be emailed resides in a common folder - that is - i created a folder by the name of C:\Program Files\SolarWinds\Orion\Reports\EmailReports

(this is for when i fill in the TAB - URL Information)

2) i created an Orion account and named it EMAILER and assigned this account to the TAB - Orion Web Login info in the Scheduler.

but like i said after i did these two things it runs like a top every day seven days a week...good luck

Two of the jobs are showing a 'Running' status right now (but they're scheduled to run in the mornings - at 6 AM), while the rest are idle.  Is there an easy way to stop them without having to stop all services? 

 To answer John's question, we don't have McAfee installed on this server.  From what I can see, our Symantec Antivirus isn't interferring either. 

Thanks. 

All of your scheduled reports are really just scheduled tasks.  If you open Scheduled Tasks in the Control Panel, you should be able to right click the tasks that are running and select End Task.

Actually I have a similar issue with NPM 9 sp1, scheduled reports that were working just sit in the running state now.

When you look at in the Windows Task Scheduler at the job that you have setup, is it set to "run only when the user is logged in"?  That is a problem that I am having.

I ran into a similar problem. Jobs would simply sit there in a running state and checking both the Scheduled Tasks log and RunOrionJob.log showed nothing helpful. I had a feeling it might be a permissions issue with the account and sure enought if the account being used to run the report does not have permissions to RunOrionJob.EXE the scheduled task kicks off and just hangs there. Once I made sure that the ReportScheduler account that I created had the appropritate permissions to that executable everything runs fine. All reports are running smoothly. The file is located in C:\Program Files\Solarwinds\Orion

I just wanted to chime in late and say that Tom's solution solved my problem.

These two things were required for the scheduled task to run:

- Local Security Policy >  Log On as Batch Job
- Modify permissions for the SolarWinds Orion folder (the service account already had read access to RunOrionJob.exe)

After changing these permissions, the scheduled task started working.

Thanks!

I have been struggling with report scheduling for awhile now.  My jobs used to run and work fine and then some upgrade broke them but I can't recall which one.  We are currently on 10.1.2.

When I set up a new job, I specify a service account to run the job.  However when I open the job again, it has my own account listed as the "run as" account.  Is that normal?  I want to make sure it's using the correct account to run the job and that I'm giving the correct account the permissions that are mentioned in the last post.

Thanks!

klc2009