Recipe Management Resolving Failure to Configure Server Components

Description 

This article from InSource provides methods to correct Recipe Management Server Components Configuration failures.

• Author: James Rochester
• Published: 9/30/2025
• Applies to: Recipe Management Plus 2023 +

Details

Scenario 1:

When attempting to configure Recipe Management Server Components tab , if you encounter 

"Failed to get registered client id [MachineName\Recipe Manager Plus]. Reason(s): One or more errors occurred, Not Found " message in the logger.  

Corrective Actions: 

Verify System Management Server (SMS) is configured and pointing to the correct Node Name on Recipe Management Server Node. 

 Aveva Identity Manager (AIM) Service running on SMS Node..

 Verify AIM Host pointing to the System Management Server Node Name as shown below:

Scenario 2:

When attempting to configure Recipe Management Server Components tab if you encounter the following error message in the Configurator configuration messages and you are utilizing RMP integrated with Application server as shown below.

"Failed to connect to Configuration Service on node <SMS Host Name>.

Corrective Actions:

Ensure sure that a Galaxy Winplatform is deployed on the AVEVA Recipe Management node before configuring the Event Service in AVEVA Recipe Management Server. 

For example, if you install the ArchestrA Galaxy Repository + AVEVA Recipe Management IDE Extensions on node 1 and AVEVA Recipe Management Server on node 2, then the WinPlatform has to be deployed on Node 2 from Node 1 before configuring Event Service in AVEVA Recipe Management Server.
If the Galaxy is not deployed, the following warning message is logged in the logger:
 

Failed to connect to Configuration Service on node: <GR Node Name>