With Historian 2020 I was able to acces the historian status tag from an other Intouch Nod. Since I have updated to 2023 the tags are not accessible.
The SLSping nodename aahiosvrsvc command does not reply.
In the 2020 historian I had to replace the aahiosvrsvc.exe from one from a hotfix. Do we still need to do this in 2023 ?
Hi Flix,
You should be able to use Suitelink (and slsping against the legacy Historian IO Server).
Reason for labeling it as legacy is that there has been some changes in 2023 R2 (not version 2023) but that was to introduce the new PCS driver for Historian allowing a new way for runtime retrieval of data from historian. This should anyways not effect your problem, just wanted to highlight this if you start looking in to settings and find this.
I'm not aware of any hotfix for 2023 related to the issue you describe, but I have tried to ping to both version using 2023 and 2023 R2 without any issues.
Just to make sure, it is not supported to apply hotfixes created for older versions, on newer versions of a installation.
There could be some challenges if you are using System Management Server that requires both involved nodes to be part of the same SMS , but that should be noted in the logger if it fails to connect.
Above configuration does not allow for 'legacy' non-encrypted SuiteLink connection.
You could of course try to open up for non-encrypted connections and try again to see if it resolves your issue, but it is of course advised to leave it as is.
Other than this I can only think of other network related things to try. such as normal ping, and verify that no firewalls are restricting access to the server and that your server and client does not identify your network as Public
Hi Flix,
You should be able to use Suitelink (and slsping against the legacy Historian IO Server).
Reason for labeling it as legacy is that there has been some changes in 2023 R2 (not version 2023) but that was to introduce the new PCS driver for Historian allowing a new way for runtime retrieval of data from historian. This should anyways not effect your problem, just wanted to highlight this if you start looking in to settings and find this.
I'm not aware of any hotfix for 2023 related to the issue you describe, but I have tried to ping to both version using 2023 and 2023 R2 without any issues.
Just to make sure, it is not supported to apply hotfixes created for older versions, on newer versions of a installation.
There could be some challenges if you are using System Management Server that requires both involved nodes to be part of the same SMS , but that should be noted in the logger if it fails to connect.
Above configuration does not allow for 'legacy' non-encrypted SuiteLink connection.
You could of course try to open up for non-encrypted connections and try again to see if it resolves your issue, but it is of course advised to leave it as is.
Other than this I can only think of other network related things to try. such as normal ping, and verify that no firewalls are restricting access to the server and that your server and client does not identify your network as Public
