Access Denied to database

[Guessboy]

i've been currently having errors while doing the backup on my server.

I've been receiving errors:
Job ended: Friday, January 21, 2005 at 1:02:02 AM
Completed status: Failed
Final error: 0xa0008488 - Access is denied.

Final error category: Security Errors

Errors
Access denied to database ....
Database or database element is corrupt

Backup - \\server\Microsoft Information Store\First Storage Group
Warning: ''\\server\Microsoft Information Store\First Storage Group\Engineering'' is a corrupt file.
This File cannot be verify.

The thing is that we began to get this problem after defragmenting our e-mail database but also we are having this errors only on 2 database on 7 database. Could anyome help me in this case thanks in advance for your help!!!

[SANDEEP_PILLAY]

This may be caused by different versions of ESEBCLI2.dll
To resolve:
1. Perform a search for esebcli2.dll on the Exchange server
2. You should find two, the first located in windows\system32 and the second in Exchsvr\bin
3. Rename the esebcli2.dll to .old in the windows\system32 directory.
4. Copy the esebcli2.dll from the Exchsvr\bin directory to the windows\system32 directory.
3. Stop and start all the Backup Exec servic

We hope this will help.

[Dipti_Chinchole]

"Access is denied" error occurs due to insufficient rights to the account that you are using. The user account used to connect to the media server should have rights equivalent to the Backup Exec service account.




To resolve the issue, grant Domain Administrator equivalent right to the user account. Alternatively, grant the rights equivalent to the Backup Exec service account. Refer the following technote's for the same:



Technote:



http://seer.support.veritas.com/docs/266075.htm


Technote:



http://seer.support.veritas.com/docs/266178.htm




Additional Information:


Technote:


http://seer.support.veritas.com/docs/256313.htm



Technote:


http://seer.support.veritas.com/docs/245186.htm

[Sagar_Kamat_2]

Please let us know whether the issue is resolved. If not, please get back to us.

[wstahn]

Hello,
we have EXACTLY the same problem here with BackupExec 9.1 Rev 4691. It also began after defragmenting the Exchange-DB (Exchange 2003) using eseutil /d. Further testing with eseutil /k revealed that the databases are fine, but BackupExec still reports this error.
Any ideas?
Wolfgang

[wstahn]

... after trying all the things mentioned here and in the web, i've got the solution..

Two weeks ago I deleted a user in the AD. The Exchange mailbox of this user still persists disconnected for a default of 30 days and can be seen in Exchange System Manager marked with a tiny red symbol. So far so good... Yesterday I ran a DB defragmentation using eseutil with the /d option. Obviously, this disconnected mailbox lead to a DB access problem for BackupExec. My very last try was to purge this mailbox in System Manager - and after that the misleading BackupExec error message was gone...

What do we learn? After running a DB defragmentation with eseutil we have to manually delete disconnected mailboxes before BackupExec can backup that Information Store...

Hey folks from Microsoft and Veritas, you should publish a KB/Technote article about that...

Bye,
Wolfgang