When binding values between ES and AS or two AS, it will show Unresolved.
EcoStruxure Building Operation
- Binding between ES and AS or two AS
- Failure of communication has occurred for one of the following reasons:
- Firewall exists between the ES and the AS
- IP address of the ES as seen in the (ES) Server > Communication tab is not the assumed/required IP address
- In 1.4 and 1.5 the server name contains the & symbol
- SmartStruxure fails to recognize the binding path with the name of AS or ES containing character "&".
For Firewall Issues:
Ensure the Windows firewall on the Enterprise Server PC is set up correctly, see SmartStruxure Workstation or editors can't get license when using firewall (errors -15 or -96) for help with the firewall settings.
Problems with firewall settings can arise if the Enterprise Server PC is removed during the commissioning process and the firewall settings swap between Private Networks and Public Network.
- All the Automation Servers may appear online, but the "Unresolved" bindings issue may be seen.
- Automation Servers cannot be restored via the Enterprise Server
Also check the IP setting in the Communications tab for all Servers (AS & ES) are set correctly
For 1.4 or 1.5 Servers with a name containing the "&" symbol:
Ask for Product Support for Hotfix R126.96.36.19901 (or later version) for version 1.4 and R188.8.131.521 (or later version) for version 1.5.
For other Causes:
Follow these troubleshooting steps in order until the issue has been resolved.
- Check that the ES IP address is the same as the PC IP address. All ports must be open between the ES and AS. If they do not match, follow How to set the Enterprise Server IP address to change the ES IP. If the address of the ES is a domain name, try using the IP address instead.
- The ES is assuming the address of a wireless adaptor, VMware virtual adaptor or VirtualBox adaptor when checked in the Server > Communication tab. When it should be using the NIC adaptor. Either follow the link in item 1 or disable the network adaptors.
- Right click on the ES and select Advanced > Repair Server Communication. This should update the Communication tables of the servers.
- Detach the automation servers from the enterprise server and delete them. Then add the automation servers back. Follow Unable to add an Automation Server underneath an Enterprise Server.
- Select each AS and click on the Communication Tab. If communication is valid, it should list the ES and every AS
- To determine if this is a local firewall issue, disable the firewall on the ES PC, then repeat step 2. Wait a few minutes, then re-check each AS communication Tab.
- You can re-enable the firewall then add excepts to allow communication.
- Set up inbound and outbound rules for the Windows Firewall on the Enterprise Server. Follow Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP p....
- Try to disable network monitor function of the anti-virus software on the computer. If Schneider laptop is used, try to uncheck the monitor functions by right click on the McAfee anti-virus software. If this can help, try to ask IT to set the exception for the monitoring according to Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP p... so that the monitor function can be back to work.
If using the previous 184.108.40.2067 release, a hotfix that can be provided by contacting product support and referencing this article needs to be installed first. This fix is in the later releases (like 1.3).
Depending on the Building Operations version that is running, a custom domain may need to be set up. In that case follow these steps.
How to setup a custom domain:
(If using 220.127.116.117 and have applied the hotfix then setup a custom domain)
- Create new domain.
- Create user groups (You cannot copy from Local) and setup permissions.
- Create Work-spaces (You cannot copy from Local)
- Select all users in the Local domain and drag to users folder in the custom domain.
- Assign users to groups
- Assign work spaces to groups.
And in the future they log into the system with the user in the custom domain.
If the problem persists, remove all StruxureWare domains from the ES and all AS. Remove the AS and read, then rebuild the domains.