Hi there
we had the same problem with one of our customers.
We had to investigate some hours until we found the problem that was causing the empty Job & Activity Log Views in the BAB Manager.
We have composed a 'small' bug report with possible workaround and sent it to CA tech support (they now could reproduce the BUG and are in going to fix it).
Here our bug report (sorry for non perfect english, but we are german speaking people in Switzerland).
Bugreport in ARCserve 9 NT/W2K
After running a generic job and restarting the BAB services (manually or running cstop) or rebooting the server, ARCserve Manager can not view any job log files (incl. Activity log) any more.
Error description
After running generic jobs (like tapecopy) and stopping the ARCserve 9 services (or rebooting the server) the ARCserve Manager can not display Log files any more (incl. the Activity Log). It just show empty windows.
Problem found
Generic jobs (like tapecopy) place their Log files into the folder \as9\LOG\cas_user_logs\ instead of \as9\LOG\cas_user_logs\caroot because they have no owner. The location is updated into the file \as9\LOG\users, when the ARCserve 9 services are being stopped or the server is getting rebooted. Unfortunately the file is updated with a wrong path so when a user afterwards wants to look at the job log of the generic job, any other job or even the activity log, then the caloggerd.exe goes into DRWATSON and the problem of not visible job logs and activity logs remains even after rebooting the server.
Reproduction / Workaround
After running the first generic job, its job log tab is still visible until you close the manager.
Just to show that the problem does not appear until running cstop or stopping the ARCserve 9 services manually or rebooting the server; start the manager again and click on the generic job. Switch to the job log tab. Close manager.
Only after running cstop, the \as9\LOG\users file is updated incorrectly (check content).
Now you have to correct the wrong entries in the users file manually (replace the empty space at the beginning with caroot and the double backslash with just one backslash to reflect the correct path to the logfile) and save your changes to the \as9\LOG\users file BEFORE you run cstart again.
run cstart
start manager
switch to the job log tab of the generic job
WARNING: If you do not correct the users file content before cstart, then this happens:
cstart
start manager
in job status click on the generic job
in lower right panel switch to job log
The caloggerd.exe process will now go into a DRWATSON
The job log tab remains empty and just shows you "the job log is not available"
Also activity log is empty
You will not be able to see any job log's until you cstop, correct the users file and cstart again !!!
Hope this helps
David A. Marton, restorage gmbh, switzerland