Troubleshoot IDAS connections

This section will help you resolve some common issues you may encounter with IDAS connections.

Issue: The remote IDAS stops communicating with the Historian after IDAS configuration information is imported on the Historian node

After you import configuration information on a Historian node (see Import a configuration) existing remote IDAS nodes may be unable to connect to the Historian. This is caused by the existing connection token for the remote IDAS becoming invalid when the IDAS configuration is updated on the Historian node.

To resolve this issue, perform the following steps:

1. On the IDAS node, stop the AVEVA Insight Supervisor service (aahSupervisor.exe).

2. On the IDAS node, delete the existing *.dat files from C:\ProgramData\ArchestrA\Historian\IDAS\Configurations.

3. On the Historian node, launch the Operations Control Management Console (OCMC). Locate the IDAS node in the Configuration Editor section, right click the IDAS node, then select Properties.

   The IDAS Properties dialog displays.

4. Select the Advanced tab.

5. Click Generate new connection token, then click OK to close the dialog and apply the change.

6. Right-click the IDAS node and select Commit Pending Changes... if it is enabled.

7. On the IDAS node, start the AVEVA Insight Supervisor service.

   The IDAS restarts, retrieves the configuration information from the server, and connects to the Historian.

Issue: The remote IDAS fails to connect to the Historian and logs a RemoteCertificateNameMismatch error

When the remote IDAS attempts to connect to the Historian using a trusted connection, the connection may fail and log a message indicating a RemoteCertificateNameMismatch error has occurred. If the host name indicated in the error message matches the host name of the Historian node, then the remote IDAS node may be unable to resolve the Historian's host name via DNS.

To resolve this issue, ensure the remote IDAS node can correctly resolve the Historian node's host name. You can temporarily work around this issue by adding an entry to the hosts file on the remote IDAS node.

8. On the IDAS node, locate the hosts file in C:\Windows\System32\drivers\etc and open it in a text editor.

9. Add a line to the hosts file consisting of the Historian node's IP address, followed by the host name. For example, if your Historian node's IP address is 192.168.1.75, and the host name is HISTSRV01, add the following line to the hosts file on the IDAS node:

   192.168.1.75 HISTSRV01

10. Save the changes to the hosts file.

    The IDAS should now connect successfully to the Historian.

Important: After the DNS issue is fixed and the Historian node's host name can be correctly resolved via DNS, remove this entry from the hosts file to prevent future connection errors.