Jobs Ready but Not Running? v7 on Netware 5.1

[Shelbyville]

Here was the problem. Jobs would sit in the queue, showing Ready but never running. Scheduler (at server console) would show time as one hour ahead of actual server and workstation time. I saw a note here that mentioned running a restore by going into Scheduler and manually changing the time.
well turns out that will work for submitted jobs also. If you've tried everything (reinstall server and manager components, etc) and jobs still just sit int he queue. Go to the Scheduler, select the job and manually change the time to the correct server time. Then save (F2) and the job should run. (As a side note, scheduler will continue to show an incorrect (+one hour) time, but the job should run. (At least that my experience so far.)

Anyone know where Scheduler gets its time? I've looked at all the INI and CFG files I can find and so far nothing?

dave

 

[hounslow]

We are having the same problem with AS7.

Are you still experincing this problem ? If so, have you tried to re-create the AS queue and manager objects in the NDS ?

Let me know how you get on.

Thanks.

 

[ivykar]

I am having a problem that sounds the same (could be user error as I am new to this backup stuff;-)).
I have ARCserve 2000 v.7 and I have submitted three jobs.
Job 1: I submitted to the "Group" and it was a full back up of the C drive on the machine to "Run Now".
Job 2: I submitted to tape 1 of the "Group" and it was a full back up of the C drive on the machine to "Run Now".
Job 3: I submitted the next morning to the "group" and it was a full back up of the C drive on the machine to "Run at a specified time" of 10:30am.
All are currently sitting in the READY state and none have run.
No error messages.
I checked the date and time on the machine and it is correct and the same date and time that is running on the ARCserve software...
I have no idea how to fix this...
Any suggestions?

 

[Denda]

One thing to look at is if your smdr.nlm & tsa.nlm (or gwtsa.nlm, if you have GroupWise on the server also) are loading correctly. You can verify that by checking your console.log. I had something like this happen with our gwtsa after the v9.01 upgrade, I had to do the following:
astop
unload gwtsa
unload smdr
smdr new -> then answer the questions it asks afterwards. It seems to be humming along now.