Troubleshooting: How to List Exchange Mailbox Users in BDRSuite Clients for Application and Databases

Troubleshooting: Unable to List Exchange Mailbox Users in BDRSuite Clients for Application and DBs

KB ID: 94
Issue:
When using the BDRSuite Client for Applications and DBs, users encounter an error message "Unable to list the Exchange mailbox users." This error suggests ensuring that the user account running the BDRSuite service has sufficient permissions.
Solution:
Step 1: Check if a new user has been created, and not an existing user.
Step 2: Ensure the new user created is a member of only the following three groups: Administrators, Domain Users, and Domain Admins. Provide "Full Control" for "Administrators" and "Domain Admins" on the user account in Active Directory Users and Computers (ADUC).
Step 3: Create a new mailbox in Exchange Server for the newly created user via Active Directory Users and Computers.
Step 4: Grant full access permissions to the new user on all mailboxes present in all storage groups using Exchange Management Shell help document.
Step 5: Download and install Microsoft's 32-bit MAPI client component 
Step 6: After downloading "ExchangeMapiCdo.EXE," run it as an administrator to extract the files. Locate "ExchangeMapiCdo.MSI" within the extraction folder and install it.
Step 7: Save the Exchange Mailbox Configuration by entering the correct profile name in the exchange configuration page (http://localhost:6060/xchangeoptions.sgp?xopt=18). Refer to the tooltip icon for more information on entering values.
Step 8: Use the new account as the BDRSuite service's logon account, ensuring it looks like an email ID (e.g., backupuser@domain) and not in "domain\backupuser" or any other form.
Step 9: Verify the following on the profile configuration page:
The Profile mailbox name should be specified as the display name of the created user.
For Exchange Server 2007, 2010, 2013, the server name should be a global catalogue server name.
  1. Check the "Connect public folder also" option only if the exchange server has a public folder database.
In an Exchange server 2013 environment:
  1. Configure GUID of the Exchange 2013 server name using the command "Get-Mailbox <backupuser> | fl ExchangeGUID."
  2. Configure FQDN name using the command "Get-OutlookAnywhere | fl host.
  3. The authentication type should be NTLM; verify using the command "Get-OutlookAnywhere | fl AuthenticationMethod."
Step 10: Copy the .dll files from C:\Program Files(x86)\ExchangeMapi to C:\Windows\System32 and C:\Windows\SYSWOW64.
Step 11: Copy the mapisvc.inf file from C:\Windows\SYSWOW64 to C:\Windows\System32.

    • Related Articles

    • SGEM0001 : Unable to fetch mailbox details.

      KB ID: 114 Cause: Insufficient permissions are assigned to the user account running the BDRSuite service. Solution: If you encounter an error accessing the "Add Exchange Mailbox Backup" page in the BDRSuite web console, follow the steps below to ...
    • No/New Modified Files Error in Exchange Mailbox Backup

      KB ID: 88 Issue: Exchange Mailbox backup encounters failure with the error message - "No/New modified files." Solution: Step 1: Copy ExchangeMapi Files 1. Navigate to “C:\Program Files (x86)\ExchangeMapi.” 2. Copy all the files from this location. 3. ...
    • Configuring Microsoft 365 User Mailbox Backup

      Configuring Microsoft 365 Backup includes the backup of user mailboxes, ensuring that emails, contacts, calendar entries, and other important mailbox data are securely protected. This enables seamless recovery of individual user data in case of ...
    • Microsoft Exchange Server Recovery

      You can perform granular recovery of Microsoft Exchange Server directly from the BDRSuite Backup Server. To begin, click on the Recovery tab on the BDRSuite Backup Server home screen and select Restore Backup Data. A list of all backup jobs will be ...
    • Configuring Microsoft 365 Group Mailbox Backups

      Configuring Microsoft 365 Backup includes the backup of group mailboxes, ensuring that all emails, calendar events, contacts, and other critical data within the group mailbox are securely protected. This enables smooth recovery of group data in case ...