You are currently reviewing an older revision of this page.
When a user without the correct Bentley Registry permissions launches APM from a thick-client, APM will go into expiry mode eventually. When the expiry happens the SAP Connectivity, as well as potentially other modules, will deselect the next time that user launches APM. This in turn clears the related Site settings. For example the SAP Gateway (Interoperability Settings) > SAP Details > Plants attributes will be blank. If the SAP connectivity module is eventually restored, these settings remain blank and need to be repopulated.
Note, this causes the users to lose the SAP Interoperability functionality but also can cause the lost of the FLOC and Equipment Dataloader.
This issue was reported as a bug, VSTS #210338 - License expiry turns off SAP Connectivity and SAP Gateway settings. It is related to bug VSTS#6043 - License expiry turns off modules and resets some site settings in EAM.
Workaround - find all instances where APM thick-clients are used, typically these should be limited to servers only but there are exceptions. Find each server running a service. For all of these thick-clients and services, the Bentley registry permissions need to be granted for all of the End Users who use those machines to access APM, all Network Users who run services, all Local Services and for the Machine Name for all local system installed services. For instructions on granting permissions for the users and services see the APM Installation guide, "To Grant User Permissions for SELECTserver Licensing" section.
Once this has been done, your application administrator will need to manually update the SAP Gateway settings in APM to restore the functionality.
https://communities.bentley.com/products/assetwise/asset_performance_management/w/internal_support_solutions/35435/select-license-renewal-process-sometimes-results-in-site-modules-being-disabled