• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 365
  • Last Modified:

Veritas Backup Exec 9.1 unable to connect to Exchange 2000 Mailbox Folders and Public Folders

Someone please help !!
We have been running exchange 2000 for well over three years and backing up to a remote server running veritas backup exec, everything has been ok for at least a year (since our last exchange outage) Last weekend the backups failed due to a tape not being loaded but since then the service account is no longer able to connect to the mailbox of public folders through Backup exec.

I have checked through all of the posts on here from people who have had similar problems but nothing seems to have worked. I will list what i have setup:
Exchange agent installed on backup server
Remote agent installed and running on Exchange server
Delegated control for the service account on the exchange system manager
service account is able to connect to any mailbox using the mapi client (outlook).

Anyhelp would be appreciated
1 Solution

As you say, it seems that a password got changed or something like that without updating the record in Backup Exec.  Here is a link to a document that shows you how to change the password to the current one.


Hope this helps,

hi there, i just had a similar problem on a clients server last week. You need to make sure that the service account being used has an Exchange mailbox assigned to it and that the mailbox is not hidden from the Exchange Global Address list. For example, if you are using the administrator account as the system account then naturally the administrator account has a mailbox associated with it, but if you've hidden the administrator account mailbox from Exchange address lists, then backup exec sees it as not being there. Alternatively, if you have created a custom service account for Backup Exec, then make sure it has an exchange mailbox associated with it.

If this doesn't work, you could try creating a new job and seeing if you can connect then, or you could uninstall Backup Exec completely (including the remote agents) and then re-installing them.
Wallerp2006Author Commented:
Thanks for the posts Guys,

I had tried everything but completely uninstalling the BE and removing the existing remote agents.
I did this, after i had reinstalled Server 2000 on the Veritas server (it was running 2003 which i thought was stupid seeing as we run a 2000 exchange system) and re-installed the new remote agents on the Exchange cluster and hey presto back in business

Top work kgreeneit have 500 points ;-)

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now