Job putting itself on hold

[jwpbwt1]

Here is a good one...
Arcserve 2000 NT4sp6a
Local job
custom schedule
at 5pm the job was in a ready state, came in this morning and the job was on hold, (it never ran). Nothing in arcserve.log to indicate a change was made.

CA has no clue.
Any thoughts would be appreciated

Thanks in advance

 

[davidmichel]

Perhaps someone selected to Modify the job.

Jobs are automaticly put on hold when Modify is selected.

 

[jwpbwt1]

nope. No one went to modify. Even after you modify, the job goes back to a ready state.

 

[mohamdr]

There are patches related to this issue in support.cai.com
Go there and check them

Is sp4 is applied

 

[lzcwsq]

If modify is selected and then arcserve is shut down without exit from modify the job will stay on hold.

We have multiple users accessing via a terminal server and this happens regularly.

 

[jwpbwt1]

mohamdr,

Then why does this not happen all the time, if we are not patched up to latest (and greatest) CA patch?
We are VERY SLOW to implement any new patches that CA says "need" to be installed. Previous experience is that these fixes cause other issues to happen.

 

[jwpbwt1]

lczwsq,
Thanks but this did not happen. Job was never modified.

 

[kilimanjaro]

I'm having the same problem with the jobs going on hold by themselves. It is definitely not a result of modifying the job. Seems to happen after the job runs. Nothing to indicate why this happens in any of the arcserve logs or event log. Running win2k, sp4 and arcserve 2000. Job is also set to reoccur in 7 days but the date doesn't change either.

 

[jwpbwt1]

Welcome to the club of UNEXPLAINABLE (By CA) Arcserve issues.....

 

[ARCserveGuru]

So.... What service pack are you on then? And what patches are applied?

g

 

[CokeandSushi]

Something to check.

Modify the job

On the Submit Job screen make sure Submit Job on Hold is NOT selected.

jwpbwt1 nice one ;-)

 

[jwpbwt1]

Nope... that option is greyed out

 

[kilimanjaro]

I found a possible fix for this (at least it worked for me). Put the db engine on hold, browse to the the arcserve\database folder. There are a number of files in that folder that start with r followed by a string of letters. Delete these files and restart the db engine.