Deploy, Don’t Destroy: Wonderware Troubleshooting

This blog post was written by Deanna Foreman.

Many developers encounter a common issue during the deployment of their system when upgrading or creating a new Wonderware System Platform galaxy. Before calling support or throwing your computer into a fire, there are steps that should be taken on all servers including the Galaxy Repository Server, the Application Object servers, the Terminal servers, Historian server, and all fat clients.


Step 1

The first step is to run the Change Network Account utility. All settings in this tool such as whether it’s a domain account or local machine account, User Name, and password need to match across all servers and computers. If you do not have an administrator account already created, select the “Create Local Account” checkbox. If it asks to create the account or to update the account with the new password, accept the changes. This step requires a reboot.


Step 2

The next step is to make sure the Windows Firewall is disabled.

Step 3

Verify the versions of Wonderware are identical. This can be checked in the Control Panel. If Patch 01, Update 01 has been installed on the Galaxy Repository but no other servers, the deployment will fail.

Step 4

Set the User Account Control Settings to Never Notify.

Step 5

Verify that you have a Local Area Connection named ArchestrA. This NIC needs to be first in the binding order. To set this order, open the Network and Sharing Center. Browse to Change Adapter Settings. In the menu header, select Advanced and then Advanced Settings. In the Connections list, ArchestrA should be first.

If you are checking this on the Application Object servers, they need to have a heartbeat NIC named RMC. This should be listed second in the binding order. If you add another NIC at any point, verify the binding order again.


Step 6

The RMC and ArchestrA NICs also need to have the IPV 6 disabled.


Step 7

Run the OSConfigurationUtility.exe located Program Files (86x)\common files\Archestra\. After running this tool, a reboot will be required.

If you are still having issues during deployment, run through tech note tn876.

After all these steps have been verified and there are still issues deploying, rerun the Change Network Account Utility. This may seem like a Hail Mary; but if any of the settings listed above had to be reconfigured, it may be necessary.

When the thought of throwing the computer out the window seems like a brilliant idea, remember to walk through these steps and deploy, not destroy!