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 AppSvr100 Handling Deployment Mismatch

Last updated: March 19th, 2025

Description

  • Author: Brian Schneider
  • Published: March 19th, 2025

Details:

Description

In the IDE you will see your platforms in the galaxy and whether or not they are deployed. Sometimes what is shown in the galaxy is not accurate due to PC replacement, running the platform killer, or restoring a galaxy backup. The following steps describe how to resolve this.

Archestra IDE says that a platform is either deployed or undeployed, but the user knows that this is incorrect and need to change this status.

Note: This assumes that you know better than the IDE. Doing these steps on machines which do not require it can cause problems in your galaxy.

  • Author: Dillon Perera
  • Published: 10/9/2014
  • Applies to: Application Server

Instructions

Marking a Platform as Undeployed:

Situation:

A platform in the IDE is showing up as Deployed, but this needs to be changed. This may occur after replacing a failed PC and needing to redeploy it, or after running the Platform Killer/Remover. When trying to undeploy the software says it cannot find the target PC on the network, or that there is a communications error.

Solution:

  1. In the IDE select the platform that should show up as undeployed.
  2. Right-click on the platform and select Undeploy.
  3. In the options for the undeploy select On Failure Mark as Undeployed. (This option says that even though the undeploy fails, go ahead and set the platform and objects as undeployed in the galaxy)
  4. Hit OK
  5. The undeploy will be attempted as normal, and will give errors saying that it is failing. When the undeploy completes, because of the option selected in step 3, the objects will be set to an undeployed status.

Marking a Platform as Deployed:

Situation:

A platform in the IDE is showing up as undeployed, but this needs to be changed. This may occur after restoring a galaxy backup, or if a network problem occurs causing the objects to deploy but not get marked as deployed in the galaxy.

Note: In both of the above situations, though these steps will make the IDE recognize the objects as deployed, you will likely want to do an undeploy afterwards and try to deploy normally. If you are unable to deploy normally, you would want to address those issues first, as opposed to working around the issue with the steps below.

Solution:

  1. In the IDE select the platform that should show up as deployed.
  2. Right-click on the platform and select Deploy.
  3. In the options for the deploy select Mark as Deployed. (This option says that even though the deploy fails, go ahead and set the platform and objects as deployed in the galaxy.)
  4. Hit OK
  5. The deploy will be attempted as normal, but even if errors occur the objects will be marked as deployed in the galaxy. If there is a larger issue, such as being unable to communicate with the remote platform entirely, the IDE will likely still display the platform in an undeployed state.
deployment mismatch
Give feedback about this article

Recommended articles

TN 1394 Error when Deploying: Remote Node's UserID/Password don't match GR Node's

Read More

TN 1366 Managing your Standalone InTouch Application in the Galaxy

Read More

Resolving "Open: Memory on the computer is low. New editor can't be launched."

Read More

TN 1040 No Alarms in Window Viewer

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