Undeploying Stuck WinPlatforms using SQL

Description

This article from InSource discusses a potential solution to undeploying “stuck” WinPlatforms.

• Author: James Rochester
• Published: 6/28/2025
• Applies to: System Platform 

Details

When attempting to undeploy/deploy a WinPlatform you may observe one of the following errors or some variation of these errors:

“Remote Node's UserID/Password don't match GR Node's”

“Failed to deploy, Platform ID already in use.”

“Can not deploy because another platform is already deployed to this computer.”

If you have already tried the normal means of undeploying the WinPllatform you can attempt this additional method which will also mark the Platform as undeployed in the Runtime Database and should reset the Platform ID depending on the number of deployed Platforms within your Galaxy. 

This should be performed in SQL Server Management Studio with an Administrative account or with an account that has Sysadmin privilege's in SQL.

Query to Locate the Platform ID: 

SELECT * FROM gobject WHERE tag_name = '<objectname>' 

Replace object name with the literal name of the WinPlatform. (i.e WinPlatform001)

After you have located the problem Platform you can utilize the following query to mark it as undeployed:

UPDATE gobject SET deployed_package_id = 0, last_deployed_package_id = 0, deployed_version = 0 WHERE gobject_id = 9878

The gobject_id represents the Platform ID in the runtime database.

After performing this the Platform should be marked as undeployed within the IDE and not be present within the Platform manager in the Operations Control Management Console on the target node.

Note: If you continue to experience deployment issues when attempting to redeploy the Platform please review the attached technical notes. These technical notes also contain other means to resolve “stuck” WinPlatforms such at the Platform manager.

TN 1283 Troubleshooting Deployment Failures

Common Platform Errors During Deployment