Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Arcserve 2000 Won't STOP Job
- Thread starter PalmIdiot
- Start date
You can go into the task manager and make sure that ALL Arcserve processes are stopped....asmgr.exe etc...OR you can get the queue ID of the job from the job queue, then go into the arcserve folder, there is a folder I think called QSD...inside this folder should have the queue ID of the job that is still running...delete this file, exit out of the arcserve and then go back in....the job should now be stopped and will show a corrupted status. Be aware that using this method you MUST recreate the job. I hope this works for you.
- Thread starter
- #3
asrunjob.exe is running, but I can't stop it. Access is denied. I tried stopping and restarting all the Arcserve services from the services menu. Still no go. So I guess I will have to delete the Que, unless anyone has any other ideas????
- Thread starter
- #5
ARCserveGuru
Technical User
No wait.... hmmmmmm, Listen, you'll get an "access denied" on the process, if you want to kill it that desperately then you'll have to use the KILL.EXE command from the NT resource kit.
But that is not the only way to kill the job. Remember though, your job crashed for a reason and judging by the crash at 99% you have a database problem. Anyway, to kill the job find the queue ID number (on the job status screen) then go to the arcserve directory into the 00000001.QSD folder and delete the entry for that job (you will lose that jobs information as you are manually removing it from the queue!). Then stop the engines and restart. The job should now have dissappeared. As you job crashed, then there is a high chance of database corruption. You'll have to initialise the database and do some test backups to try to troubleshoot why the job crashed at 99% (i.e. when updating the arcserve database).
good luck,
guru
But that is not the only way to kill the job. Remember though, your job crashed for a reason and judging by the crash at 99% you have a database problem. Anyway, to kill the job find the queue ID number (on the job status screen) then go to the arcserve directory into the 00000001.QSD folder and delete the entry for that job (you will lose that jobs information as you are manually removing it from the queue!). Then stop the engines and restart. The job should now have dissappeared. As you job crashed, then there is a high chance of database corruption. You'll have to initialise the database and do some test backups to try to troubleshoot why the job crashed at 99% (i.e. when updating the arcserve database).
good luck,
guru
Howdy,
I had this problem once before, and there is a way to stop the process in Task Manager. BUT, you cannot open Task Manager by pressing Ctrl+Alt+Del or by typing taskmgr.exe in the Run box.
To make it work, open a command prompt, and then type:
"at 10:31 /interactive taskmgr.exe"
Type that of course without the quotes and substitute the time you want it to run, probably one minute in the future. Task Manager will then start and you can kill asrunjob.exe.
Hope this helps,
Rob
I had this problem once before, and there is a way to stop the process in Task Manager. BUT, you cannot open Task Manager by pressing Ctrl+Alt+Del or by typing taskmgr.exe in the Run box.
To make it work, open a command prompt, and then type:
"at 10:31 /interactive taskmgr.exe"
Type that of course without the quotes and substitute the time you want it to run, probably one minute in the future. Task Manager will then start and you can kill asrunjob.exe.
Hope this helps,
Rob
- Thread starter
- #9
Well I got the process to stop, but I had to reboot the server. But like mentioned in the earlier post, I think I may have a Database issue now. I have done 2 more full backups and both have hung on 99%. The only error I see is:
E8602 Failed to read from database (DBNAME=individual mailboxes\usename\inbox=backup agent error (359) Failed to read data block for attachment.
Any ideas???
E8602 Failed to read from database (DBNAME=individual mailboxes\usename\inbox=backup agent error (359) Failed to read data block for attachment.
Any ideas???
montanablue2
MIS
Your database may be corrupt. You can fix that by stopping the database service and deleting the database or database files, then repairing arcserve. Make note that you'll have to merge any previous backup jobs if you want to restore from them...
- Thread starter
- #11
ARCserveGuru
Technical User
Hang on, am I missing something here???
This is the error right?
E8602 Failed to read from database (DBNAME=individual mailboxes\usename\inbox=backup agent error (359) Failed to read data block for attachment.
INDIVIDUAL MAILBOXES, i.e. your exchange server.... now if you want to go and delete you exchange database, by all means go ahead. But I would advise against it.
This issue indicates there is something interfering with the agent, perhaps an antivirus?
Apply sp3 to arcserve 2000 and the exchange agent, then apply the qo06202 patch from the ca website. This should help with the e8602 issue.
Now for the ARCserve database, just do an initialise (from the server admin console, select the database engine tab, then click on the operation tab, and select initialise.)
this will clear out your arcserve database. If there is a problem with the ARCserve database then you'll find *.CAT files in your arcserve/temp directory. Do you have any?
guru
This is the error right?
E8602 Failed to read from database (DBNAME=individual mailboxes\usename\inbox=backup agent error (359) Failed to read data block for attachment.
INDIVIDUAL MAILBOXES, i.e. your exchange server.... now if you want to go and delete you exchange database, by all means go ahead. But I would advise against it.
This issue indicates there is something interfering with the agent, perhaps an antivirus?
Apply sp3 to arcserve 2000 and the exchange agent, then apply the qo06202 patch from the ca website. This should help with the e8602 issue.
Now for the ARCserve database, just do an initialise (from the server admin console, select the database engine tab, then click on the operation tab, and select initialise.)
this will clear out your arcserve database. If there is a problem with the ARCserve database then you'll find *.CAT files in your arcserve/temp directory. Do you have any?
guru
- Status