Symptoms

The system operates slowly, the processing of the tasks takes a lot of time and the task queue grows.

Cause

When we use Failover Cluster for FlexiCapture12 in Azure we have to turn off the option “Use Network Name for computer name” in the Processing Server cluster role settings.

If this option is active, the Processing Server will connect to the Application Server under the name of the clustered role (additional common name and additional IP address), and the use of the second IP address for VM does not work in Azure (If we add an additional IP address on the VM which is unknown to Azure the gateway will not respond to an ARP request containing an unknown destination. So that the sender's ARP request will fail and the error message "Destination host unreachable" shows up.).

We will get a lot of errors in the Windows event log on Application Server VM like: ABBYY FlexiCapture Webservices -> Error during connection to server station “clustered role name”. The RPC server is unavailable.

All tasks related to connecting to the Application Server will work very slow, Processing Station's cores will not be used efficiently and the task queue will increase.

Resolution

In order to resolve the issue, turn off the option “Use Network Name for computer name” in the Processing Server cluster role settings.