Some content on this site is available only to logged-in subscribers. Contact Us for information on becoming a subscriber.

InSource.Solutions | InSource Training | InSource Client Portal
InSource Solutions Logo
Log In Sign Up
InSource.Solutions InSource Training InSource Client Portal Log In Sign Up
  • Home
  • AVEVA Application Server
  • AVEVA Application Server Tech Notes

How to Resolve Failed to Connect SR Node Warnings

Last updated: August 27th, 2025

Description

  • Author: Rich Brooks
  • Published: August 27th, 2025

Details:

This tech note is for AVEVA System Platform 2023R2 SP1 and higher.   There is potentially a problem when a platform by itself (with no cascade) takes a long time to deploy.  The platform takes as much as 15 minutes to deploy.  Messages may be found in the Log Viewer such as the following. 

One thing to check is the ArchestrA Services.  Run the ArchestrA Services utility to check for issues.  This may be run from C:\Program Files (x86)\Common Files\ArchestrA\Services\aaServiceConfiguration.exe

Type in the name of Repository Node and Solution Name.  Leave the default as localhost if running from the GR node.  Click on the Connect button.


Select the Nodes tab at the bottom left.  The icons for MxDataProvider and Authentication indicate the services are not deployed to the platform.

The MxDataProvider and Authentication services will display icons indicating they are not deployed.  

Check and enable TCP Port 808 to and from the remote platform and the GR node.  

The Microsoft PortQryUI may be used to check the port to verify the port has been opened on the firewall.  

Right-click on each of the platforms to select Deploy from the dialog.

The services will deploy now enabling a much faster platform deployment.

resolve connect
Give feedback about this article

Recommended articles

[ISS Support Case] WindowViewer Initialization Failure

Client reached out as when user is attempting to launch WindowViewer they are receiving a prompt to convert the application version which has already been converted, but when selecting either option WindowViewer fails to launch. This is a managed application. Prompt states the following: "Application developed with older InTouch. Run WindowMaker to Convert?"

Read More

[ISS Support Case] lost connection to PLC

PLC L33er- compact logix is able to ping the PLC

Read More

[ISS Support Case] PLC Communication Failure

Client reached because after user migrated the Galaxy none of the tags are communicating.

Read More
Support Icon

CONTACT SUPPORT

How to reach us

10800 Midlothian Turnpike Tpke, Suite 209, Richmond, VA 23235

1.877.INSOURCE

Technical Support - 1.888.691.3858

Contact Us

  • InSource Solutions
  • InSource Training
  • InSource Client Portal
  • Log In
InSource Solutions Logo

© 2025 InSource Solutions. All Rights Reserved.

Knowledge Base Software powered by Helpjuice

Expand