Scheduled Job does not change. A new one is created

Has anyone had the following scenario?

I created a job to run Weekly for inventory.

After running it for a while, I decided to change the schedule and run it at a different time. I changed the criteria and saved it.

A week later, the job started at its old time! Then, wonder of wonders, it started again at the new prescribed time.

After looking in the schedule list in NCM and finding nothing wrong, I looked in the Windows Started Task (job run schedule) list and found that the OLD job was still there. It was never changed or deleted.

I have deleted several jobs that were erroneously there.

Please comment and advise. Thanks

Find more posts tagged with

scheduled_job

inventory

job_run_schedule

Accepted answers

All comments

byrona

I am having a similiar set of problems that includes the problem that you mention with both Orion NCM and Orion NPM for any scheduled job.

I have noticed that if I touch a job in the Windows Task Scheduler that I have created in either Orion NPM or NCM that I am no longer able to make changes to them in Orion NPM or NCM. The frustrating part is it "looks" like they have been changed in the NPM/NCM but when you look in Windows Task Scheduler it hasn't been changed.

I am having the added problem of any job that I schedule in NPM/NCM doesn't run at all because in the Windows Task Scheduler it is set to "run only when user is logged in".

Which Windows version are you running this on? I am on a Windows Server 2008 system.

chris.lapoint

There is a known issue on Windows 2008 systems where the schedule task defaults to "run only when user is logged in". The workaround is to go into the Windows scheduled tasks and manually edit to check the box to allow running when not logged in.

byrona

That workaround was my original plan but what I found out is that when I touch a job in the Winows Task Scheduler, any furhter attmpts to edit that job through the Orion software are unsuccessful.

I have an open ticket on all of this right now and your support folks seem to think there is a permission issue somewhere but we have been unable to locate one.

Thoughts?

mhh351

I'm thinking that the permissions issue is not the culprit. I believe it is the CREATOR issue where the app is not looking for the correct job or possibly the version. When you touch the WT list, Orion is now not in synch and it can't find the old "job". The real issue for me was the fact that NCM didn't delete or alter the initial job, it just merrily created another one, leaving the original to run without deleting it as would be expected.