Tips to Check Connection Between Online Server and AspenWatch Servers
Download as pdf :
Products:
Aspen DMC3, Aspen Watch Performance Monitor
Last Updated:
05-Oct-2021
Last Updated:
05-Oct-2021
Versions:
Article ID:
000099040
Article ID:
000099040
Primary Subject:
Problem Statement
This solution frames a couple of points to check when there is a connection problem (or suspect a connection problem) between Online Server and AspenWatch Server
Solution
1.- The messages display on AW Maker Run Status can give a few hints about a further problem. some of them can include:
Not Licensed:
This problem can occur when AW is not capable to reach the License Server, or it could wait for the validation of the license before the change to Success. The Not Licensed message also could indicate that there is a problem with the Aspen APC Performance Monitor Data Service. In such a case Verify that the service is running, verify that the service is running with an administrator account, or restart the service to check if this can solve the problem. Further, the message can appear if one of the applications is not started and requires the process controller process to be running for the status to change. Finally, if the problem exists for ACO application is possible that some of the controller features as adaptive modeling require a separated license key that may not be in your current License file. This features normally can be disable from the CCF by going into DMCplus Build and then check the general section from the option menu
CIM-IO Connection Failed:
This problem can be fixed by restarting the DMCplus context service on the Online Server.
2.- Verify that the connections are properly set between the AW server and the Online Server. This can be easily done by going to AW Maker ----> Actions ------> Online Host Connections (Opening this could take a few minutes). Healthy communication should show all the RTE and DMCplus nodes in green. If one of the Nodes is yellow verify that the Server name is correct, verify that there is no firewall between ports that could be interrupting the communication, and check through a ping test that the communication between servers is enabled on both sides (the ping test should be done on both server AW and Online the communication should successful for both cases). If the ping test fails in any of both ways, It may be necessary to check for further network problems.
3.- Verify that the Controllers (RTE or ACO) are running with any further problem (License Validation, ONREQ going success), also check that the RTE Service and DMCplus context service are running fine on the Online Server. Otherwise, The AW Maker Run status could hang on initial or any of the other messages described above.
4.- Verify that IP21 Manager is running fine. This includes checking that all the tasks from the IP21 manager have run fine since the start of the IP21 manager. (Is a good practice to enable the option Startup @ Boot). Also, make sure that before rebooting the AW server the IP21 Administrator is stopped, otherwise, this could lead to further problems on the Database.
5.- In the case of the RTE Controllers, we suggest stop the collection before rebooting the server and restart the collection afterward.
Keywords
AspenWacth Server, AspenWatch Maker, Online Server