Hi All,
Lurky - which version of ArcServe are you running? If you're running AE/WG 7.0, on a Win2K server or above, you might want to apply ArcServe SP5. Accoring to CA, it's supposed to fix this issue amoungst others. You can find it at
The file is called Q)49312.CAZ - you'll need CAZIPXP to unzip it. If you don't have it, you can get it at
In terms of your database problem, have you tried going in to ArcServe Server admin and reinitializing the database? Yes, it will clean absolutely everything - which means that you'll have to merge tapes manually if you're doing any restores from them, but it should help clean things up.
If you don't want to apply SP5 right away, you should be able to get rid of your jobs that are showing active and uable to be stopped by doing the following:
Find the directory called 00000001.QSD and open it. This directoy contains listings for all of your jobs. Normally, there should only be the following files in this directory: 1. Files with the name 0000000x.job where x is a number corresponding to the job's queue ID.
2. QSYS.QUF and QSYS.QJF which are specific to this folder becasue they keep track of the job data.
If you see any files with a .chk extension, they'll probably match your stuck jobs. To clear them out, do the following.
1. Go to ArcServe Server Manager and stop all services.
2. Go back to the 00000001.QSD directory and delete all jobs that have .chk files associated with them. Don't forget to delete the .chk files as well.
3. Go back to Server Manager and restart the services.
When you re-open ArcServe Manager, you should see that your jobs have been removed from the queue.
Syl
