Troubleshooting Wonderware Application Server Bootstrap Communications

Schneider Electric Software
Knowledge & Support Center
Doc Type Tech Notes
Doc Id TN482
Last Modified Date 08/28/2015
Troubleshooting Wonderware Application Server Bootstrap Communications

LEGACY TECH NOTE #
876
SUMMARY
This Tech Note outlines general troubleshooting steps to address communication issues between a remote node and an Wonderware Application Server Galaxy.
This Tech Note augments TN 461 Troubleshooting Industrial Application Server Bootstrap Communications.
SITUATION
Application Versions
Wonderware Application Server 3.5 (2012). Please check the compatability matrix at the Wonderware Tech Support site for supported operating systems.
This Tech Note uses Windows Server 2008 for the examples.
Note: If you are having trouble opening the SMC logger from a client node or the Server node, please see Tech Note 437: Unable to Open Logger Under Windows XP SP2 and Windows 2003
SP1.
Wonderware Configuration Tools

Use the following Wonderware Configuration tools when troubleshooting the application.
Wonderware Change Network Account Utility
Ensure that the ArchestrA Network Admin Account is the same on all machines in the Galaxy (or wish to interact with nodes in the Galaxy).
1. Launch the Change Network Account utility from Start/All Programs/Wonderware/Common/Change Network Account.
Figure 1: Change Network Account Utility Interface

2. Ensure that the local machine name does not have any unusual characters such as a tilde ( ~ ) or underscore. These characters can cause communication errors.
Wonderware O/S Configuration Utility
Use the OS Configuration Utility to add TCP/UDP ports and application authorization to the Windows Firewall exclusion list, in order to allow Wonderware products to operate as designed on
Windows XP SP2 , Windows 2003 SP1 or greater, Windows Vista, Windows 2008, and Windows 7.
The OS Configuration utility is delivered with ASP 3.5 (2012).
You can also download the utility from the GCS support site.
To run the Wonderware O/S Configuration Utility
1. Navigate to <RootDrive>\Program Files\Common Files\ArchestrA.

2. Run the application named OSConfigurationUtility.exe.
For a list of what the utility does, please refer to the Tech Article Security Settings for Wonderware Products.
3. Reboot the machine after running the O/S Configuration Utility.
The Schneider Electric industrial software business and AVEVA have merged to trade as AVEVA Group plc, a UK listed company. The Schneider Electric and Life
Is On trademarks are owned by Schneider Electric and are being licensed to AVEVA by Schneider Electric.
Terms of Use | Privacy Policy
Copyright © 2018 AVEVA Group Plc. All rights reserved

Verify Wonderware Application Versions
Ensure that the version of Wonderware Application Server installed on the remote node is the same as the version of the Wonderware Application Server Galaxy.
1. Verify the version by going to Control Panel / Programs / Programs and Features. Verify the Wonderware Application Server 2012 version on the Galaxy Repository (GR) Node and
on the remote nodes.
Note: If the Version column is not visible, right click on a column name then click More. You can then see the Version column.
Figure 2: Verify Program Version
Figure 2 (above) shows Wonderware Application Server 2012 -- 3.5 Patch 01.
Checking Windows DCOM Configuration

The DCOM Ports used by the Bootstrap are:
Port 135
Port 139
Port 445
Ports 1024 to 65535
For additional info see:
http://support.microsoft.com/kb/832017
http://www.linklogger.com/TCP135.htm
Complete the following tasks to ensure DCOM settings are correct.
DCOM – Checking Wonderware-Compatible Security Settings

1. Run dcomcnfg.exe from Start/Run.
This is the editor you use to make local DCOM changes to DCOM security levels on the computer.
2. Expand the branches as follows:
Component Services/Computers/MyComputer/DCOM Config.
3. Check the following packages.
The first package is WWPim (aka Wonderware Platform Information Manager)

Right click WWPim, then click Properties (Figure 3 below).

Figure 3: WWPim DCOM Service Properties
In the General tab panel, make sure the Authentication Level is None (Figure 4 below).
Figure 4: WWPim Authentication Level
Click the Location tab and make sure the Run application on this computer box is checked.
Note: On x64 operating systems this option may be grayed out/disabled. The workaround is to use the 32-bit version of DCOMCNFG by using the following command line:
C:\WINDOWS\SysWOW64>mmc comexp.msc /32.
Figure 5: Run Application on this Computer
Click the Security tab.
Under each Security grouping, ensure that the security settings are set similar to those shown in the following graphics. These are the minimum settings needed.

Figure 6: Security Properties Tab Panel
Figure 7: Security Settings for Access Permissions
Figure 8: Security Settings for Launch and Activation Permissions

Figure 9: Security settings for Configuration Permissions
Click the Identity tab.
The This user option shown below should be the ArchestrA Network Admin account defined using the Wonderware Change Network Account Utility.
Figure 10: This User Identity Option
The Endpoints tab panel should look similar to the following graphic (Figure 11 below).
Figure 11: DCOM Default System Client Protocols

Click OK.
Ensure that all the same settings used for WWPim are applied for the DCOMTransport.
From the Component Services window, right-click My Computer then click Properties.
Figure 12: My Computer / Properties
Ensure the Enable Distributed COM on this computer option is checked (Figure 13 below).
Figure 13: Default Properties Configuration
Windows Configuration – Checking Local Security Settings

Note: These settings may be overridden by an enforced Group Policy Object from an MS Active Directory setup if the machine is part of a domain.
Configure local security settings from the Control Panel.
1. Click Administrative Tools/Local Security Policy (Figure 14 below):
Figure 14: Local Security Policy
2. Expand the Local Policies folder , then click Security Options.

3. Double-click Network access: Sharing and security model for local accounts.

Figure 15: Network Access: Sharing and security model for local accounts
4. Ensure that the selected option is Classic and not Guest only.
Figure 16: Classic Security Setting
5. Click OK to save the setting.

6. Select User Rights Assignment under Local Policies then double-click Log on as a service.
Figure 17: Log on as a Service Setting
7. Ensure that the ArchestrA Network Admin account is listed here. In Figure 18 (below), it is wwuser.

Figure 18: Logon as a Service Security Property
8. Similarly check if the Archestra Network Admin Account is added in the following policies:
Log on as a batch job
Deny log on locally
Deny log on through Remote Desktop Services
Act as part of the operating system. (While it is not generally required, in some specific cases adding the ArchestrA Network admin account to this policy may resolve
communication issues. Click the following link for information on Act as part of the operating system property.)
9. Double-click Deny logon as a service.
Figure 19: Deny Logon as a Service
10. Ensure that the ArchestrA Network Admin account (referenced above) is not listed here (Figure 20 below).
Figure 20: Deny Logon as a Service Security Property
11. Click OK.

Windows Configuration – Checking Computer Management
The following items must be checked as a part of troubleshooting Bootstrap communication.
Local Users and Groups
Make sure the ArchestrA Network Admin account is a member of the Administrators group on the local machine, regardless if it is a local or domain account.
Note: The user logged on to the desktop of the remote machine that is trying to launch an IDE for remote GR access must be an Administrator of the remote machine. Administrator
permissions are necessary to allow proper DCOM and similar communication.
Shared Folders – Shares
Make sure the following folders are shared on the local machine and that the ArchestrA Network Admin account has permissions to read and write to the folders.
aaFileRepository
aaSF$
ArchestrA Galaxy Data
Wonderware$
Figure 23: Shared System Folders
Windows Configuration – Folder Options

1. In the Microsoft Windows Explorer main menu, click Tools/Folder options.
Note: If the Tools menu is not visible, press F10 to see the menu.
Figure 24: Windows Explorer Folder Options

2. Uncheck the Use Sharing Wizard (Recommended) option.
Figure 25: Disable Simple File Sharing

Windows Configuration – Regional Settings
Ensure that the regional settings of the remote and GR nodes are set to English (United States).
Verify the settings using the Regional and Language Options dialogue box from the Control Panel/Clock, Language, and Region/Region and Language.

Troubleshooting Wonderware Application Server Bootstrap Communications

Uploaded by

Copyright:

Available Formats

Troubleshooting Wonderware Application Server Bootstrap Communications

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Troubleshooting Wonderware Application Server Bootstrap Communications

Uploaded by

Copyright:

Available Formats

Schneider Electric Software

Knowledge & Support Center

Doc Type Tech Notes

Last Modified Date 08/28/2015

Troubleshooting Wonderware Application Server Bootstrap Communications

Wonderware Configuration Tools

Wonderware Change Network Account Utility

Figure 1: Change Network Account Utility Interface

Wonderware O/S Configuration Utility

The OS Configuration utility is delivered with ASP 3.5 (2012).

To run the Wonderware O/S Configuration Utility

1. Navigate to <RootDrive>\Program Files\Common Files\ArchestrA.

Terms of Use | Privacy Policy

Copyright © 2018 AVEVA Group Plc. All rights reserved

Figure 2: Verify Program Version

Checking Windows DCOM Configuration

For additional info see:

Complete the following tasks to ensure DCOM settings are correct.

DCOM – Checking Wonderware-Compatible Security Settings

Component Services/Computers/MyComputer/DCOM Config.

3. Check the following packages.

The first package is WWPim (aka Wonderware Platform Information Manager)

Terms of Use | Privacy Policy

Copyright © 2018 AVEVA Group Plc. All rights reserved

Figure 4: WWPim Authentication Level

Figure 5: Run Application on this Computer

Click the Security tab.

Terms of Use | Privacy Policy

Copyright © 2018 AVEVA Group Plc. All rights reserved

Figure 7: Security Settings for Access Permissions

Figure 8: Security Settings for Launch and Activation Permissions

Terms of Use | Privacy Policy

Copyright © 2018 AVEVA Group Plc. All rights reserved

Click the Identity tab.

Figure 10: This User Identity Option

Figure 11: DCOM Default System Client Protocols

Terms of Use | Privacy Policy

Copyright © 2018 AVEVA Group Plc. All rights reserved

Figure 12: My Computer / Properties

Figure 13: Default Properties Configuration

Windows Configuration – Checking Local Security Settings

Configure local security settings from the Control Panel.

1. Click Administrative Tools/Local Security Policy (Figure 14 below):

Figure 14: Local Security Policy

2. Expand the Local Policies folder , then click Security Options.

Terms of Use | Privacy Policy

Copyright © 2018 AVEVA Group Plc. All rights reserved

Figure 16: Classic Security Setting

5. Click OK to save the setting.

Figure 17: Log on as a Service Setting

Terms of Use | Privacy Policy

Copyright © 2018 AVEVA Group Plc. All rights reserved

Figure 19: Deny Logon as a Service

Figure 20: Deny Logon as a Service Security Property

11. Click OK.

Terms of Use | Privacy Policy

Copyright © 2018 AVEVA Group Plc. All rights reserved

Local Users and Groups

Shared Folders – Shares