Exchange job message errors

In no particular order, here are various Exchange errors we'll run into and their solutions.


Symptom

  • Backup contains the error MBXBackup Fatal: MAPIInitialize failed : MAPI_E_CALL_FAILED

Resolution

  • Download and Install ExchangeMapiCdo.exe from www.microsoft.com

Sympton
  • Backup contains the error MBXBackup Fatal: FAILED TO CREATE MESSAGE SERVICE (in MAPI 1.0) : This information service is not installed on your computer. To install it, use the Mail And Fax icon in the Control Panel. : MAPI_E_NOT_FOUND

Resolution

  • This seems to happen right after installing the ExchangeMapiCdo file. Try restarting the bacula service (our agent) or perhaps rebooting the Exchange server.

Symptom

  • Backup contains error MBXBackup Fatal: Unable to open message store (in Microsoft Exchange Server Information Store) : The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. : MAPI_E_FAILONEPROVIDER

Resolution

  • A reboot of the Exchange server has worked in internal testing.

Symptom

  • Backup contains error MBXBackup Fatal: Failed to Configure Message Service. Networking error Check server name:EXCHANGEAD : MAPI_E_NETWORK_ERROR
  • This error is likely to occur on Exchange 2007 or 2010 running on Windows 2008. This is much less likely to be seen on a fully up-to-date Exchange 2010 running on Windows 2008 R2.

Resolution

  • The problem is due to some Exchange services not registering to listen on ports in the IPv6 stack, but only on IPv4. We found a [related issue](http://msexchangeteam.com/archive/2008/06/20/449053.aspx){:target=\_blank} involving Outlook Anywhere. Using those instructions relevant to our backup scenario, we found a pretty simple fix:
     1) Notepad > Run as Administrator 2) File > Open > "C:\Windows\System32\drivers\etc\" > [All Files] > "hosts" > Open Comment out the line "::1 localhost" Add the following two lines:     An example might look like: 127.0.0.1 localhost #::1 localhost 10.10.10.4 exchange-server 10.10.10.4 exchange-server.your-domain.com [PLEASE DOUBLE CHECK THE ABOVE] </pre> 3. Reboot the Exchange server for this change to take effect
    4. Run a backup
    </li> </ul>
    NOTE: could also be an issue with the Public Store being full or an issue with split roles. Please see the KB article "MAPI_E_NETWORK_ERROR MBXBackup Fatal: Failed to Configure Message Service. Networking error" or " How to Properly Configure Exchange 2007/2010 Mailbox Backups with Split Roles" for more information.

    Symptom

    • Backup contains the error: ESEBackup: ReadFile error c7ff0fa4 Functions called in an invalid sequence. /Unknown error

    Resolution

    • The message: "ReadFile error c7ff0fa4 Functions called in an invalid sequence" indicates that the logs are out of sync and so a restore would not be possible to a certain point. The recommendation is to run a full backup as soon as possible.

    Here are a few additional suggestions that may or may not apply to the above case (best practices):

    When we run incremental or differential backups we are capturing only the log files, the idea being that in a restore, you would restore the latest full and then reply any subsequent logs to rebuild the database.

    • 1. Edit this client to run a Weekly schedule. It is not advisable to mix both differential and incremental backups for an Exchange client.
    • 2. In the RVXConfig tool on the Exchange server, confirm that you are not truncating logs after a differential or an incremental. By default, we only truncate after a full.
    • 3. Confirm that no other backups are running that might be affecting or otherwise truncating the logs.

    Symptom

    • Problem setting property 67480014 : MAPI_E_NO_ACCESS
      • This error message was seen on a message restore in Exchange 2010.

    Resolution

    • unknown cause
    • It seems that despite this disconcerting message, the email items are actually restored.
    • This may be cleared up by running the latest agent version

    Symptom

    • Failed open: 8004011c CTUHPP-FileIO JobId 742: MBXBackup Fatal: Unable to open message store (in Microsoft Exchange Information Store) : Your profile is not configured. : MAPI_E_UNCONFIGURED
      • this message was reported by one single customer with Exchange 2007

    -------

    Symptom:
    Mailbox jobs fail with completely blank message logs. Event Logs indicate only "Nanny: process exited - restarting".
    Resolution:
    Unknown. Have customer make sure all service packs and exchangemapicdo are up to date as well as the client. Customer may need to unmount the databases and use eseutil to run an integrity check.
    *[AES]: Advanced Encryption Standard *[AESs]: Advanced Encryption Standards *[API]: application programming interface *[APIs]: application programming interfaces *[AWS]: Amazon Web Services *[AWSs]: Amazon Web Servicess *[BMR]: BareMetal Restore *[BMRs]: BareMetal Restores *[CAB]: Cloud Application Backup *[CABs]: Cloud Application Backups *[CB]: Cloud Backup *[CBs]: Cloud Backups *[CBT]: Changed Block Tracking *[CBTs]: Changed Block Trackings *[CFA]: cloud failover appliance *[CFAs]: cloud failover appliances *[CIFS]: Common Internet File System *[CIFSs]: Common Internet File Systems *[DC]: data center *[DCs]: data centers *[DDFS]: deduplication file system *[DDFSs]: deduplication file systems *[DDFS-AR]: DDFS-assisted replication *[DDFS-ARs]: DDFS-assisted replications *[DPS]: Data Protection Server *[DPSs]: Data Protection Servers *[DR]: disaster recovery *[DRs]: disaster recoverys *[DRaaS]: Disaster Recovery as a Service *[DRaaSs]: Disaster Recovery as a Services *[EULA]: end-user license agreement *[EULAs]: end-user license agreements *[GCP]: Google Cloud Platform *[GCPs]: Google Cloud Platforms *[ICAB]: Infrascale Cloud Application Backup *[ICABs]: Infrascale Cloud Application Backups *[ICB]: Infrascale Cloud Backup *[ICBs]: Infrascale Cloud Backups *[ICMP]: Internet Control Message Protocol *[ICMPs]: Internet Control Message Protocols *[IDR]: Infrascale Disaster Recovery *[IDRs]: Infrascale Disaster Recoverys *[IPMI]: Intelligent Platform Management Interface *[IPMIs]: Intelligent Platform Management Interfaces *[JVM]: Java virtual machine *[JVMs]: Java virtual machines *[LVM]: logical volume management *[LVMs]: logical volume managements *[MFA]: multi-factor authentication *[MFAs]: multi-factor authentications *[MSP]: managed services provider *[MSPs]: managed services providers *[N/A]: Not applicable *[N/As]: Not applicables *[NAS]: network-attached storage *[NASs]: network-attached storages *[NAT]: network address translation *[NATs]: network address translations *[NFS]: Network File System *[NFSs]: Network File Systems *[NIC]: network interface controller *[NICs]: network interface controllers *[NTP]: Network Time Protocol *[NTPs]: Network Time Protocols *[NTPD]: Network Time Protocol Daemon *[NTPDs]: Network Time Protocol Daemons *[OBRM]: Online Backup and Recovery Manager *[OBRMs]: Online Backup and Recovery Managers *[ODX]: Offloaded Data Transfer *[ODXs]: Offloaded Data Transfers *[PBKDF2]: Password-Based Key Derivation Function 2 *[PBKDF2s]: Password-Based Key Derivation Function 2s *[POSIX]: Portable Operating System Interface for Unix *[POSIXs]: Portable Operating System Interface for Unixs *[RAID]: Redundant Array of Independent Disks *[RAIDs]: Redundant Array of Independent Diskss *[RCT]: resilient change tracking *[RCTs]: resilient change trackings *[ROM]: read-only memory *[ROMs]: read-only memorys *[SDK]: software development kit *[SDKs]: software development kits *[SMB]: Server Message Block *[SMBs]: Server Message Blocks *[SMTP]: Simple Mail Transfer Protocol *[SMTPs]: Simple Mail Transfer Protocols *[SNMP]: Simple Network Management Protocol *[SNMPs]: Simple Network Management Protocols *[UCAR]: unique content addressable repository *[UCARs]: unique content addressable repositorys *[UDP]: User Datagram Protocol *[UDPs]: User Datagram Protocols *[UEFI]: Unified Extensible Firmware Interface *[UEFIs]: Unified Extensible Firmware Interfaces *[UNC]: Universal Naming Convention *[UNCs]: Universal Naming Conventions *[UPS]: uninterruptable power supply *[UPSs]: uninterruptable power supplys *[vCFA]: virtual cloud failover appliance *[vCFAs]: virtual cloud failover appliances *[vCPU]: virtual central processing unit *[vCPUs]: virtual central processing units *[vNIC]: virtual network interface controller *[vNICs]: virtual network interface controllers *[VM]: virtual machine *[VMs]: virtual machines *[VNC]: Virtual Network Computing *[VNCs]: Virtual Network Computings *[VPN]: virtual private network *[VPNs]: virtual private networks *[VSS]: Volume Shadow Copy Service *[VSSs]: Volume Shadow Copy Services