TN - AppSrv260323001 Troubleshooting using ArchestrA Services

Last updated: March 23rd, 2026

Description

Author: James Rochester
Published: March 23rd, 2026

Details:

Description

This article from InSource discusses the use of the aaServiceConfiguration Application to troubleshoot various System Platform issues. This utility provides inside into the core ArchestrA services that are responsible for deployment ,data transmission and authentication.

Author: James Rochester
Published: 11/11/2025
Applies to: System Platform 2023 and higher

Details

The ArchestrA Service utility can be located in C:\Program Files (x86)\Common Files\ArchestrA\Services. This utility should be run as an administrator.

When configuring the Application you must configure two items:

The Repository node: This should be the hostname of the PC that host your Galaxy Repository. In this example the Galaxy repository is hosted locally.

The Solution Name: This should be the name of the Galaxy that you wish to connect to. In this example the Galaxy name is HairGel.

Each of these services serves a unique purpose.

•GRBrowse

•One instance of this service runs per Galaxy on the GR Node even if GR Platform is not deployed for that Galaxy

•IOMBLSService

•One instance of this service runs per Galaxy on the GR Node even if GR Platform is not deployed for that Galaxy

As an example if a remote development node is failing to connect to a GR node from a remote node you can attempt to undeploy and redeploy this service in order to verify the connection to the GR node is valid.

•MxDataProvider

•One instance of this service runs on every deployed node in the Galaxy

•Gets deployed automatically as part of platform deployment

•Provides the Galaxy Attribute Data to local OMI application

•Provides the license to local OMI application

As an example if a ViewApp is not receiving data you can attempt to undeploy and redeploy this service in order to verify that the service is in a valid running status in order to provide tag value data to the ViewApp.

•Authentication

•One instance of this service runs on every node in the Galaxy

•Gets deployed automatically as part of platform deployment

As an example if a user is failing to connect to login to the Galaxy from a remote node or into a ViewApp you can attempt to undeploy and redeploy this service in order to verify that the service is in a valid running status in order to validate the user has the necessary permissions for the function they are attempting to accomplish.

Give feedback about this article

Recommended articles

[ISS Support Case] lost connection to PLC

PLC L33er- compact logix is able to ping the PLC

[ISS Support Case] HMI Communication Loss

Client reached out due to two of several HMI nodes loosing communication intermittently. When reviewing the logs I observed several instances of Suitelink suspend and resume messages. This indicates an overload condition generally. SuiteLink handles the possible over-flooding of its write buffer in the above condition by posting a message to itself every one hundred milli-second by default. This message estimates the depth of the message queue. If the message queue is too deep then SuiteLink generates SUSPEND events message on all connected clients and servers. When the message queue falls to a minimum depth, SuiteLink sends a Resume event message to its clients and servers. If a PC or network gets busy for any reason and can not handle the suitelink traffic, a suspend event will occur and suitelink is supposed to stop sending data until it receives a resume event.

[ISS Support Case] PLC Communication Failure

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

TN - AppSrv260323001 Troubleshooting using ArchestrA Services

Description

Details:

Description

Details

Recommended articles

[ISS Support Case] lost connection to PLC

[ISS Support Case] HMI Communication Loss

[ISS Support Case] PLC Communication Failure

CONTACT SUPPORT