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.
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...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.