| Product(s): | APM Implementation and Performance Management | ||
| Version(s): | 7 | ||
| Environment: | N/A | ||
| Area: | N/A | ||
| Subarea: | N/A |
Problem Description
When APM is updated the Smart Client instances installed on end-user computers become obsolete and cannot connect to the Application Servers because their version does not match the Servers version of APM. As part of the normal update process, the Smart Clients are repackaged using the Smart Client Packager tool and deployed to the original deployment location, in most cases this is the deployment page found via the Server Manager. When the smart client instances are next run they will automatically check their deployment source page to see if there is an updated smart client package deployed. If there is a newer packaged smart client in the deployment share the local client will prompt the end-user to accept the updated package and will not launch the client until the update is accepted.
In this case the end-user was being blocked from accessing the deployment share / website by an internal security software package and was not able to install the update and was then failing to connect with the server.
Solution
The user needed to contact their internal security team to whitelist the APM deployment share and also needed to update their local permissions to allow for them to update the Bentley APM install folders.