An attempt to connect to an Acronis Agent fails with "Active Directory is not available for the specified user. Cannot create MAPI profile. Probably, the user does not have a mailbox or Microsoft Exchange MAPI and CDO are probably out of date."

How to resolve the situation when Acronis Recovery for Microsoft Exchange Management Console hangs or errors when connecting to an Acronis Agent remotely

Add the NETWORK SERVICE user to security policies to solve the issue

Add Acronis processes to the list of exceptions

Delete the contents of HKEY_CURRENT_USER\Software\Acronis\CredStorage and reattempt the connection

Choose a different location or assign Local Administrator rights to Acronis Agent User

Remote connection from Acronis Management Console to a machine booted from Acronis Backup & Recovery WinPE is not supported

To resolve the issue, remove the "My Web Sites on MSN" folder from "My Computer" in Windows Vista or from "My Network Places" in Windows XP

Description of how to establish a proper connection to Acronis Agent on Microsoft Exchange Server from Acronis Recovery for Microsoft Exchange Management Console

You attempt to connect to the Web Console that runs as a Virtual Appliance on your ESX(i) Host. The connection will not be established or it takes several minutes in order to load the UI of the Web Console. You can reinstall the Virtual Appliance or one specific log to solve this issue.

Disable or update Bytemobile software on the machine to eliminate the issue. Also attempt to fix your LSP Layer or reset your winsock cache.

Wait 10 minutes after service start, clean up databases

This article applies to:

  • Acronis Backup Advanced 11.5

A short overview of the network connections between Acronis OS Deploy Server and Acronis Snap Deploy Agent during image deployment process

Remove Acronis Storage Node from Acronis Management Server and add it back to fix the issue

When connecting to RHEV Manager, make sure you include domain in the user name


The MassTransit Log may display the following error: "Connection Closed because remote protocol was incompatible" This error results from an unsupported version of MassTransit calls another MassTransit, e.g. if MassTransit 2.x calls MassTransit 4.1


This article describes how to resolve the "Failed to Connect to server; FILES COMMAND not found" error that occurs with MassTransit plugin. This error only occurs when MTWeb is running on HTTPS. Additionally the error is encountered only when using Internet Explorer on Windows.



Users receive "Failed to connect to server; FILES COMMAND not found" error after logging into MTWeb using Internet Explorer on Windows.



MassTransit servers and clients may report an inability to connect to a remote destination that is configured to use an IP address reserved for private internets (networks).


Organizations that require network connectivity internally, but do not require network layer connectivity outside of that organization may choose to use IP addresses that have been reserved for private internets. As indicated in RFC 1918, the Internet Assigned Numbers Authority (IANA) has reserved three specific blocks for such private internets. These blocks include: