Resolving Domain Based Deployment Errors

Description

This article from InSource discusses a potential reason for Platform Deployment Failures.

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

Details

When deploying a WinPlatform you may observe one of the following errors:

"Failed to create a remote interface with the version information from Bootstrap."

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

"Remote activation was necessary but server name was not provided".

“Cannot find the target pc on the network.”

In order to verify if the deployment issue is Domain related you should begin by running the following command as an Administrator in command prompt on the target node.

Nltest /sc_verify:[ <DomainName>] 

(Checks the status of the secure channel that the NetLogon service established. If the secure channel does not work, this parameter removes the existing channel, and then builds a new one. You must have administrative credentials to use this parameter.)

If the test fails this indicates that the servers secure channel to the Domain is corrupt and you can proceed to running the following command.

If the test is successful please refer to one of these Deployment Troubleshooting Technical notes. 

TN 1283 Troubleshooting Deployment Failures

Common Platform Errors During Deployment

Run as an administrator in command prompt on the target node.

Nltest /sc_reset:[ <DomainName>]

(Removes, and then rebuilds, the secure channel that the NetLogon service established. You must have administrative credentials to use this parameter.)

After successfully running the commands you can reattempt to deploy the affected WinPlatform. 

Note: It is possible to experience this same type of Domain issue on the development server where you are deploying. However this would lead to deployment issues with any Win Platform and not a specific instance. If you believe your development node is currently experiencing this issue the same steps apply.