Troubleshooting the ESI Exchange Integration

This section provides known problems and limitations for troubleshooting the Exchange Integration.


Prevention, resolution, or workaround

Mounting a database task fails and the "Failed to execute given scriptblock 'Mount-Database -Identity…" and "Couldn’t mount the database that you specified…" errors appear.

The error indicates that ESI is unable to mount the database because the edb files are missing.

If you used ESI to create a database, but the wizard only completed part of the task, such as creating transaction log files, then the log files need to be removed or replaced before you can mount the database.

When you create a mailbox database in ESI and use a cluster disk as the mount path, the "operation SetMountPath faulted on Vds proxy" error message occurs.

Because clustered mount paths can come and go on any individual node in the cluster, this configuration is not supported by ESI. To avoid this error when creating a mailbox database in ESI, do not mount a non-cluster disk to a mount path that is hosted by a cluster disk.

Failover or switchover operations failed.

For the ESI Exchange HA Extension, the Exchange mailbox servers may not be added to the Exchange Organization Management Security Group.

In the Exchange Management console, add the applicable Exchange mailbox servers as members of the Exchange Security Group that is named Organization Management.

If you add an Exchange mailbox server to the Exchange Organization Management Security Group after installing the ESI Exchange HA Extension, you must stop and restart the extension to apply the change. Stopping and restarting the extension has more details.

During discovery of Exchange DAGs, mailbox servers, or mailbox databases, the "assignment statements are not allowed in a restricted language mode or data section" error appears.

On the Exchange mailbox server that  connects to ESI, you might need to set an application setting for Windows PowerShell.

  1. On the Exchange mailbox server, open the Internet Information Services (IIS) Manager for Windows PowerShell and in the Application Settings, and set the PSLanguageMode to FullLanguage.

  2. After changing the IIS setting, restart IIS to apply the change. To restart IIS on the server, click Start > Run, type IISReset, and click OK.

Cannot locate the EDB file disk ID or log folder disk ID.

Confirm that ESI can discover the storage LUNs by adding the mailbox server as a host system in ESI and enumerating host volumes with mount points as EDB file and log folders.

If the storage LUN information is not discovered, then the storage system may need to be reconnected or the connection refreshed in ESI.

The "Get-EmcExchangePrimaryActiveManager cmdlet: Unable to find mailbox server in DAG acting as Primary Active Manager” error appears.

  • If running this cmdlet on an Exchange DAG in third-party replication mode, ensure that the ESI HA Extension is installed and set up on each mailbox server in the DAG. Installing and setting up ESI Exchange HA Extension provides instructions.

  • The HA extension may not be reachable because you are using this cmdlet on a native Exchange DAG. This cmdlet is not supported on native DAGs.

If you are using the ESI Exchange Integration with a third-party DAG on an Exchange 2013 server and an error that begins with the following appears:

"New-PSSession: [hostname] Connecting to remote server <hostname> failed with the following error message : The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer <hostname> returned an ‘access denied’ error.”

If this error appears, the “Workaround for Microsoft Exchange 2013 with third-party DAG when using EMC Storage Integrator version 3.0.1 for Windows Suite” article on EMC Online Support provides a workaround for this Microsoft Exchange 2013 issue.

  • After you restart a mailbox server that is running the ESI Exchange HA Extension, the extension does not correctly start, which might cause a database failover or a switchover failure.

  • In the extension log file, the following error appears near the end of the log: “ClusterRegCreateKey failed: The remote server has been paused or is in the process of being started.”

Try restarting the extension. Stopping and restarting the extension. provides instructions.

Note: The EsiExchangeMonitorService.log file (extension log file) is located on the mailbox server in the %PROGRAMDATA%\EMC\ESI\Service\ folder.

When you use the Activate Mailbox Database Copy wizard, a "Database move request failed: Unable to activate any mailbox database copies..." error appears or a general failure error occurs.

This error can occur when the cluster group is taken offline for the first time, which might be a timing issue. Go to the Failover Cluster Manager in Windows and locate the cluster group. If the group is in a failed status, right-click the cluster group and select to Bring the service or application online. After the group is back online, resume the task in ESI.