SAP Alerts displaying incorrect time

SAP Alerts displaying incorrect time

Problem :
The time shown for SAP Alerts under Alarms tab in SAP monitor is incorrect.


Solution :
  1. Enter the time difference (in hours) in <AppManager_Home>\conf\SAP.properties file am.sap.alerttime.offset key. For example, in the above screenshot the time in Applications Manager is recorded 5:30 hours later than the actual SAP alert time. So the entry in SAP.properties file should be am.sap.alerttime.offset=5.5.
  2. Restart Applications Manager.


      New to ADSelfService Plus?

      Start your free trial

        Resources

            • Related Articles

            • No Data in SAP Server monitor/ Unable to add SAP monitor

              Problem:  In Appmanager_home/logs/nms/stdout.txt , the error message "SAPDataCollector : Host information not found for server" is found. Solution:  Add entry for IP Address and SAP Instance name in etc/hosts file of Applications Manager server and ...

            • Frequently asked questions - SAP monitor

              1. SAP monitor's Health is always critical/warning state along with "System Error occurred" alert message. What should I do? These alerts are triggered when Applications manager receives Alerts from the SAP server itself. The same can be viewed under ...

            • SAP HANA Troubleshooting

              If you face connectivity issues with your SAP HANA DB instance in Applications Manager: 1. Verify if the correct SQL port (indexserver port) has been provided in Applications Manager.  2. Verify the JDBC connection to SAP HANA DB via HANA Client ...

            • How to execute SAP Debug script

              1. Steps to execute troubleshooting script SAPDebug.bat/sh: Open command prompt/terminal with administrator privileges. Navigate to <AppManager_home>\bin\troubleshooting folder. Execute the script file SAPDebug.bat or SAPDebug.sh Usage: SAPDebug.bat  ...

            • Failed login alerts for some domains

              Error: Failed Login alerts are received for some specific domains. Solution: For Windows WMI monitoring, failed login alerts are received for some domains because Kerberos authentication is done first, followed by NTLM. This can be avoided by ...