Cannot see job logs in DB view

[tbeeber]

I think this one is permissions related, but I can't figure out the details.

W2K server, Arcserve 2000, SP3. I have updated the service account permissions to all the recommended levels, and updated the Job and Tape Engines to log in with the service account. (I tried setting up the DB engine to login with that account, but kept getting errors "3073 Unable to logon as user. (USER=user, EC=PRIVELEDGE NOT HELD)" so I set that back to the system account. But that may or may not be a separate problem.)

Here is my problem. The job logs keep coming up empty when I try to view them from the Database view. If I open a job from the job status view, I can see the log of the latest run, but if I look at the job from the database view, there is no log file apparent, just a blank space where I woudl expect the log to appear. No error messages, either.

Here's what else - If I try looking at the logs from a different system with the ARCserve manager, I can see them fine. They are just blank when looking at them on the backup server itself.

I only have this issue on the 1 W2K server we are running, other NT4 servers are fine.

As I said, I'd be willing to bet this is some sort of permissions issue, I just haven't figured out how to fix it.

Any thoughts?

 

[ARCserveGuru]

You may want to make sure the account in question has the advanced rights mentioned previously. Especially the log on as a service advanced right for the job engine. I've seen this before and it was because I forgot to add that advanced right. But that was only the w3073 error. The problem with viewing the database is news to me.

guru

 

[Bostik]

I had the same problem until I added full control rights for the Arcserve system account to the Arcserve share on the system drive. Arcserve set up this share, and rights for local backup operators etc, but didn't do the same for the specified Arcserve system account.
I also found that monifying and resubmitting the jobs after this change worked.

 

[tbeeber]

Both good suggestions...

Guru - that permission was set. The other engines run off that account without a problem, but for some reason, the DB engine flags that error.

Bostik - I put that permission back into the share. (It was there before, but had somehow got removed in some permissions changes.) Unfortunately, still no improvement.

Back to the drawing board...