cancel
Showing results for 
Search instead for 
Did you mean: 

Exchange agent access is denied on backup selection

Ross_Hamilton
Not applicable
Hello,

Ever since we have installed backupexec and rolled out the exchange agent we have not managed to backup exchange. When i go to job setup and make a job and go to backup selection and select the exchange agent, i get a access denied message. Now i have tried everything to get this work. The account i am using has full control on exchange with delegated access. I have also checked the exdata folder and the account has full control all across. The account i am using has local admin rights on the exchange server. Also is the service account and the account is a member of enterprise admin and domain admin groups.

Here is the exact error message i get with access denied

"Logon account "DOMAIN\USERNAME Default Account" failed to access "SERVER\Microsoft Mailboxes". Access is Denied"

This error message comes up when i try and connect to "microsoft Exchange Mailboxes" and "Microsoft Exchange Public Folders". The funny thing is i can connect to the Microsoft Information Store.

I am currently running Backupexec 10D with service pack 2

We have all the latest updates for windows 2003 aswell.

So any suggestions would be very greatful.

Regards,

Ross
1 REPLY 1

shweta_rege
Level 6
Hello,


1. Ensure that the logon account used to connect to the Exchange mailboxes has Exchange Full Admin rights.

Set the default account in Backup Exec under Network | Logon Accounts to the account that has full rights to Exchange.

2. Ensure the mailbox is not hidden - The mailbox must be seen in the GAL (Global Address List). This can be tested by composing a new mail message in outlook and clicking the 'To:' field. Should you not see the display name in this list it is hidden.

3. The Backup Exec service account must have its own mailbox that has been tested with Outlook prior to configuring mailbox backups. If the mailbox has not had mail traffic, it can be flagged as "Inactive" by Exchange. This can be corrected by simply sending this account mail.

4. When configuring mailbox backups, always log on as the Backup Exec service account.

5. The Backup Exec service account's mailbox must be unique to the organization. No other mailbox can share the first 5 characters in common with this mailbox in the entire organization. This can be tested by composing a new mail message and then in 'To:' field type the first 5 characters of the mailbox display name, then press , this should resolve the name, if a menu pops up, then there are multiple accounts which share these first 5 characters. The matching names should be changed or the BESA mailbox name should be changed to something unique.

6. Stop and re-start the Backup Exec services after making any of the above changes. Let us know the results of the steps performed. If the issue persists, then create a new account. Give this account Domain Admin and Exchange Full Administrator rights.

In order to back up and restore individual Exchange mailboxes and public folders, use System Manager utility to grant the Exchange Administrator role to the user account at the Administrative Group level (for all Administrative Groups if there is more than one).

At Backup Exec GUI, go to Network | Logon Accounts and add the new account. Use this account to connect to the Exchange mailboxes.



Related Documents:

Logon Account " " failed to access "\\SERVER\Microsoft Exchange Mailbox". Access Denied

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

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

How to configure a Microsoft Exchange 5.5 & 2000 individual mailbox backup: A comprehensive overview

http://support.veritas.com/docs/249456

When attempting to back up mailboxes, an error was encountered because the mailbox that is used to attach is not unique.

http://support.veritas.com/docs/262707

How to confirm that an Exchange mailbox name is unique within the Exchange organization when configuring VERITAS Backup Exec (tm) to back up Exchange mailboxes

http://support.veritas.com/docs/256537


Thank You,

Shweta