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

TN - AppSrv2604271017 - Remove platform that is stuck in platform manager

Last updated: May 15th, 2026

Description

  • Author: Josh Andrade
  • Published: May 15th, 2026

Details:

 

 

Author:  Joshua Andrade
Applies to Version(s):  2023 R2 
 Latest Revision Date : 5-15-2026
Document Version: 001

Description

Platform shows up in Platform Manager as part of a Galaxy, but that machine actually belongs to a completely separate galaxy.

Problem Description:

There are times when platforms do not properly undeploy, which causes the Platform folder to not delete. These should remove themselves when a platform is undeployed.

In this case, the platform was undeployed, the platform object was deleted from the galaxy, but it still showed up in OCMC:

 

We knew for a fact, that this platform belongs to another galaxy:

Solution Details

Solution Steps:

Open up Registry Editor, and go to -

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ArchestrA\Framework):

 

You’ll end up finding a Platform folder that where the “Machine” row will show the Computer Name:

 

 Take a backup of this Platform folder, and delete it. After that, the machine reference will be removed from OCMC Platform Manager..

__________________________________________________________________________________________________________________________

platformremover uninstall
Give feedback about this article

Recommended articles

[ISS Support Case] Platform Deployment Failure

Client reached out as when user was attempting to deploy WinPlatform user was receiving the following error: "Cannot find the target PC on the network OR target PC can not communicate back to the Galaxy Repository using the NIC that is top in the binding order."

Read More

[ISS Support Case] Platform Deployment Issue

Client was unable to deploy platform receiving error message that stated: "Error:Failed to deploy Platform_Backup: Cannot find the target PC on the network OR target PC can not communicate back to the Galaxy REpositorey using the NIC that is top in the binding order. "

Read More

[ISS Support Case] Platform deployment failing

LM, CDP both latest

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

© 2026 InSource Solutions. All Rights Reserved.

Knowledge Base Software powered by Helpjuice

Expand