Issue
A License Violation alarm is triggered without displaying a License Violation banner.
Alarm reactivates after acknowledgment, approximately every 10 minutes.
Product Line
EcoStruxure Building Operation
Environment
- Building Operation Enterprise Server
- Building Operation Enterprise Central
- Building Operation Automation Server
- Building Operation Automation Server Premium
- Building Operation Automation Server Bundled
Cause
Potential communication issue, possibly related to return path or port configuration.
An incorrect ES port may be in use, contributing to the issue.
The Communication Tab [Communication View] and Server List in xbk Analyzer show only the ES, indicating limited server visibility.
Resolution
-
Verify Communication Path
- Ensure the ES is defined as using the same ports across all servers.
- Confirm that the ports are correctly configured and open on all relevant servers.
-
Review the Communication Tab [Communication View] and Server List
- Check that all expected servers are listed and actively communicating.
- If only the ES is visible, investigate potential network or configuration issues.
- See article for additional information: Updating a Enterprise Server IP Address - Schneider Electric Community
-
Check AS Logs
- Log in to the Automation Servers to identify any communication errors.
- These errors may not be visible from the ES alone.
Next Steps
- If the above steps do not resolve the issue or the root cause remains unclear:
- Refer to the article for possible communication-related troubleshooting options: Enterprise Server and Automation Server Bindings show Unresolved - Schneider Electric Community
- Refer to the article for additional license troubleshooting options: Troubleshooting EBO license violation issues - Schneider Electric Community
- Contact your local support organization for further assistance.