This section provides useful help and tips over and above the formal support manual sections 2 through 18.
Did you install OBM on the Exchange server with mailbox role? Important: For version 6.9.2.0 or above, OBM must be installed on the Exchange server hosting the database (e.g. Exchange server with mailbox role).
Did you assign full control permission of the corresponding administrative group to the system account for backup? Confirm on the security setting of the account. Perform the following procedure:
Did you assign the system account for backup to the correct security group? The account must be a member of the Enterprise Admins and a Domain Admins security group. Perform the following procedure:
Have you restarted the affected computer recently? After any permission change, reboot the MS Exchange Server in order for the changes to take effect immediately:
Note: If you have multiple domain controllers in the forest, you may also have to wait for directory replication to complete.
Is the account for backup mailbox enabled? Perform the following procedure:
Note: A mailbox-enabled user is a Windows Active Directory user that has one or more Exchange Server mailboxes associated with it. http://support.microsoft.com/kb/275636/en-us.
Are the Exchange related Windows services running properly? Ensure that all MS Exchange related services have been started. Pay close attention to the 'MS Exchange Information Store' and 'MS Exchange System Attendant' services:
Is the MAPI profile in use configured properly? The Messaging Application Programming Interface (MAPI) profile is use by OBM when a mail level backup job is performed, ensure that the profile setting is correctly configured. Perform the following procedure:
C:\Windows\system32\drivers\etc\hosts (Updated) |
Copyright (c) 1993-1999 Microsoft Corp. This is a sample HOSTS file used by Microsoft TCP/IP for Windows. ... IP_address Hostname |
Important: Perform this step only if the Exchange server hostname cannot be resolved.
Note:For domain environment with multiple Exchange servers, enter the IP address of the Exchange with Client Access Role.
In some instances, you can resolve the issue by re-creating the MAPI profile. Try deleting, then re-creating the profile. Perform the following procedure:
Did OBM crash while you were trying to create the backup set? If the software crash when you are trying to create a mail level backup set, restart OBM in debug mode to confirm if there is any Java crash error displayed. Refer to 1.5 How to start OBM / ACB in debug mode? for instruction. Important: For instruction on how to properly setup your MS Exchange mail level backup, refer to Section 16 for details.
Did you install OBM on the Exchange server with mailbox role? Important: For version 6.9.2.0 or above, OBM must be installed on the Exchange server hosting the database (e.g. Exchange server with mailbox role).
Did you granted full mailbox access to the system account for backup? Confirm on the mailbox access permission of the account. Perform the following procedure:
Exchange Server 2007 >Get-MailboxServer | Add-ADPermission -User "%os_username%" -AccessRights GenericAll -ExtendedRights ms-exch-store-admin,receive-as,send-as -InheritanceType All Exchange Server 2010 >Get-Mailbox | Add-MailboxPermission -User "%os_username%" -AccessRights FullAccess Note: %os_username% is the username of the operating system account for backup.
Did you assign the system account for backup to the correct security group? The account must be a member of the following security groups:
Perform the following procedure:
Security group setting of Exchange Server 2007
Security group setting of Exchange Server 2010
Is the Remote Exchange Management Shell enabled for account for backup? Important: This requirement only applies to Exchange 2010 Server. Perform the following procedure:
Note: Remote Shell in Microsoft Exchange Server 2010 enables you to manage your server running Exchange 2010.
Is the account for backup mailbox enabled? Perform the following procedure:
Note: A mailbox-enabled user is a Windows Active Directory user that has one or more Exchange Server mailboxes associated with it (http://support.microsoft.com/kb/275636/en-us).
Have you restart the affected computer recently? After any permission change, reboot the MS Exchange Server in order for the changes to take effect immediately:

Note: If you have multiple domain controllers in the forest, you may also have to wait for directory replication to complete.
Is the Public Folder Database available and mounted? Ensure that the Public Folder Database is available and mounted in the Exchange Management Console Important: This requirement only applies to OBM version pre-6.9.2.0. Perform the following procedure:
Have you installed Collaboration Data Objects (CDO) 1.2.1 on the corresponding Exchange server? CDO must be installed on the Exchange server for the mail level backup job to work properly. Download and install CDO with the following installer:
Did you install the latest version of Collaboration Data Objects (CDO) on the corresponding Exchange server? Perform the following procedure:
The version of all dll files must be the aligned. If an older version of CDO is in use, re-installing the newest version of MapiCdo (e.g. Windows 2008 Server is only supported in the later release of the MapiCdo). MapiCdo can be downloaded at: http://www.microsoft.com/en-us/download/details.aspx?id=39045
Are the Exchange related Windows services running properly? Ensure that all MS Exchange related services have been started. Pay close attention to the 'MS Exchange Information Store' and 'MS Exchange System Attendant' services:
Is the MAPI profile in use configured properly? The Messaging Application Programming Interface (MAPI) profile is use by OBM when a mail level backup job is performed, ensure that the profile setting is correctly configured. Perform the following procedure:
|
C:\Windows\system32\drivers\etc\hosts (Updated) |
| Copyright (c) 1993-1999 Microsoft Corp. |
| . |
| This is a sample HOSTS file used by Microsoft TCP/IP for Windows. |
| ... |
| IP_address Hostname |
Important: Perform this step only if the Exchange server hostname cannot be resolved.
Note: For domain environment with multiple Exchange servers, enter the IP address of the Exchange with Client Access Role.
In some instances, you can resolve the issue by re-creating the MAPI profile. Try deleting, then re-creating the profile. Perform the following procedure:
Are there any existing MAPI profile for application such as Outlook or BlackBerry on the affected Exchange server? In some cases, MAPI profile of Outlook or BlackBerry MAPI profile may affect the backup operation if they are created before the OBM's MAPI profile. Remove the corresponding MAPI profiles temporarily, then re-create the MAPI profile for OBM with the steps provided above.
What version of OBM are you using?Ensure that the latest version is installed. The latest release includes fixes for known bugs and may resolve the issue you are experiencing.
Did OBM crash while you were trying to create the backup set? If the software crash when you are trying to create a mail level backup set, restart OBM in debug mode to confirm if there is any Java crash error displayed. Refer to 1.5 How to start OBM / ACB in debug mode? for instruction. Important: For instruction on how to properly setup a MS Exchange mail level backup set, refer to the Section 16 for details.
Did you install OBM on the Exchange server with mailbox role? Important: OBM must be installed on the Exchange server hosting the database (e.g. Exchange server with mailbox role).
Please ensure the latest version of the OBM is installed. You can download the latest version from Section 1.1, and install over any existing installation.
Did you grant full mailbox access to the system account for backup? Confirm on the mailbox access permission of the account. Perform the following procedure:
Did you assign the system account for backup to the correct security group? The account must be a member of the following security groups:
To check on the current settings:
Is the Remote Exchange Management Shell enabled for the account used to backup? To check on the settings:
Is the account for backup mailbox enabled? Refer to the following article from Microsoft for more details on how to check if an account is mailbox enabled: http://technet.microsoft.com/en-us/libr ... 50%29.aspx
Have you restarted the affected computer recently? After any permission change, reboot the MS Exchange Server in order for the changes to take effect immediately.
Did you install the latest version of Collaboration Data Objects (CDO) on the corresponding Exchange server? Un-install the existing CDO installation, and then re-install the newest version of MapiCdo, which can be obtain at: http://www.microsoft.com/en-gb/download ... x?id=42040
Are the Exchange related Windows services running properly?
Ensure that all MS Exchange related services have been started. Pay close attention to the 'MS Exchange Information Store' service:
What is the LAN Manager authentication level configured on the Exchange server? To check on the setting:
Confirm on the connection to the Exchange Management Shell (EMS) or Exchange Management Console (EMC). Ensure that the HTTP binding on the Default Web Site in Internet Information Services (IIS) is correctly configured:
Is the .NET Framework 3.5 Features installed? To install the feature:
Is Windows PowerShell 2.0 Engine installed? To install the feature:
Is the MAPI profile in use configured properly? Pay attention to the 'PR_PROFILE_RPC_PROXY_SERVER' property, ensure that the property is not corrupted or empty. Perform the following procedure:
Are there any existing MAPI profile for application such as Outlook or BlackBerry on the affected Exchange server? In some cases, MAPI profile of Outlook or BlackBerry MAPI profile may affect the backup operation if they are created before the OBM's MAPI profile. Remove the corresponding MAPI profiles temporarily, then re-create the MAPI profile for OBM with the steps provided above.
In some instances, you can resolve the issue by re-creating the MAPI profile. Try deleting, then re-creating the profile. Perform the following procedure:
Did OBM crash while you were trying to create the backup set? If the software crash when you are trying to create a mail level backup set, restart OBM in debug mode to confirm if there is any Java crash error displayed. Refer to 1.5 How to start OBM / ACB in debug mode? for instruction.