Error Message

Merge1 Importer logs show the error below:

DEBUG Merge1.Core.Importer - Retry attempt 1. Exception type: Merge1.Targets.Base.ConnectionException.

WARN  Merge1.Targets.EVTarget.EVTarget - Message #2770 sending attempt (1) on connection #1 failed: Failed to get Archive due to: 'Enterprise Vault is not running.'.. Retrying in 3200 milliseconds...

If the Enterprise Vault server is functioning as expected, the issue is observed due to failure in communicating with EV server from Merge1 server. This is due to the required ports not being open between EV and Merge1. 

Merge1 uses Enterprise Vault API to communicate with the EV Server and ingest the data into EV Archive. It requires the RPC 135 and the dynamic ports to be open between EV and Merge1 for successful DCOM Communication.

The range of dynamic ports can vary between servers. To check the configured range on a Windows machine, use the following command:

netsh int ipv4 show dynamicport tcp

If the dynamic port ranges differ between the Enterprise Vault (EV) server and the Merge1 server, it can affect which dynamic ports are used during communication. This becomes particularly important when firewall rules are configured to permit only a specific port range. In such cases, you must ensure that the firewall allows traffic within the dynamic port range used by each server, and that the necessary ports are open for bidirectional communication.

If there's a mismatch or restriction in port availability, you may observe connection issues in a network trace. Specifically, after the RPC connection is initiated between the EV and Merge1 servers, the trace may show the absence of TCP SYN-ACK responses and repeated retransmissions indicating that the expected ports are being blocked or unavailable.

Please refer to the article below (Section: Enterprise Vault server) for the list of required ports to communicate with EV Server. 

Destination ports required by Enterprise Vault

Please refer below technote to open the required ports on the EV Server and create firewall rules to allow DCOM communication between Merge1 and EV Server:

How to setup the Enterprise Vault Distributed COM (DCOM) services to function through a Windows 2003 / 2008 / 2012 Firewall