Learn about known issues and apply workarounds for Agentry Server.
| Issue # | Description |
|---|---|
N/A | Agentry Server 6.1 should report versioning information to a central
landscape management tool.
Workaround: Agentry Server stores the version information in a system file. A user can determine the Agentry Server version by navigating in File Explorer to the Agentry Server executable and right-clicking the file properties to determine the versioning information. |
RTC-440 | In an SAP Control Center cluster, if a server node is
restarted when an Agentry application is stopped (not disabled), then when
SAP Mobile Platform restarts, the node and Agentry Server
get into differing states. If you have an application stopped, not disabled, and a server node comes down, then when the node restarts, the Agentry server on that node starts and causes the nodes to be in different states. This causes all the “Start/Stop/Restart” buttons to become disabled. You must either restart the Agentry node or delete the application and start over. Workaround: None. |
RTC-435 | Status of Agentry Server is not updated correctly in
SAP Control Center. When one of the nodes that has Agentry Server in a cluster is shutdown, the server status in SAP Control Center is not updated and continues to show a status of started. Workaround: None. |