Академический Документы
Профессиональный Документы
Культура Документы
Table of contents
1. Problem
2. Solution
Problem
"Failed to deploy WAWINHMI01_Platform: Can not communicate with remote node - Failed to create
a remote interface for the version information from Bootstrap."
OS_SP: SP2
Solution
There are a lot of possible causes for a failure to deploy accompanied by the warning you mentioned in
your email, but in this case many have been ruled out with a successful ping by IP and node name. Is it
possible that someone has changed the IP address on the target node since the Platform was initially
con gured? It might be worth checking the IP address for which the Platform is con gured. The next
thing How canis we
to check helpsure
to make you?
that anti virus software or a re wall is blocking the deploy. The easiest
ting to do would be to temporarily disable any antivirus software Make sure that any real time virus
https://knowledge.insourcess.com/Support_Tickets/Industrial_Application_Server/Installation%2F%2FConfiguration/026863_-_"Failed_to_deploy_<Pla… 1/3
10/13/2019 026863 - "Failed to deploy <PlatformName>: Can not communicate with remote node" - InSource KnowledgeCenter
ting to do would be to temporarily disable any antivirus software. Make sure that any real time virus
protection is disabled from the Task Manager also. Wonderware has an excellent document on
Security and Wonderware products available on the Wonderware support site. If the anti virus
software or a re wall do not resolve a solution, you should next check to make sure that the exact
same version and patch level of IAS are installed on the GR node and the remote platform to which the
deploy is being attempted. Are the GR node and the remote Platform node both running under the
exact same username or domain username and password? A quick check is to run the Change Network
Account utility from Start > Programs > Wonderware > Common on *both* nodes. Enter in the
administrative account name and password and reboot. Next thing to check would be to make sure
that there's not a problem with DCOM. Go to Start > Run >DCOMCNFG - MyComputer (rightclick)
Properties > Default Properties > and make sure that "Enable Distributed COM on this computer" is
enabled. Does the Wonderware log viewer in the System Management Console reveal any further
clues? IAS uses a proprietary protocol called LMX and NMX to manage all ArchestrA processes and
communications. NMX and LMX keep all of the Galaxy components and remote components such as
Platforms organized and in sync. It possible to have a relatively benign network issue where there is
enough stability for aping to be successful, but get in the way of successful NMX (Network Messaging
Exchange) operation. Take a look at your Wonderware Logger and especially the operating system's
System, Application , and Security logs in the Event Viewer under Administrative Tools in the Control
Panel.
Back to top
Recommended articles
There are no recommended articles.
IT Article Class:
NetSuite
Tags:
This page has no tags.