SMO 3.4.2P5 fails to run the service on Windows 2019 after Windows Updates mid-2022
Applies to
- SnapManager for Oracle (SMO) 3.4.2P3, 3.4.2P4 and 3.4.2P5 for Windows
- SnapManager for SAP (SMSAP) 3.4.2P3, 3.4.2P4 and 3.4.2P5 for Windows
- Microsoft Windows 2019
Issue
- After a recent reboot, the SMO (or SMSAP) Service fails to start up normally.
- The event logs have shown some recent upgrades on Windows.
The
Additionally, it appears that the java process that the wrapper runs to start the SMO Service, crashes with a java core dump:
wrapper.log shows the following messages:ERROR | wrapper | <DATE_TIME> | JVM exited while starting the application.
FATAL | wrapper | <DATE_TIME> | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
FATAL | wrapper | <DATE_TIME> | There may be a configuration problem: please check the logs.
STATUS | wrapper | <DATE_TIME> | <-- Wrapper StoppedAdditionally, it appears that the java process that the wrapper runs to start the SMO Service, crashes with a java core dump:
INFO | jvm 5 | <DATE_TIME> | #
INFO | jvm 5 | <DATE_TIME> | # A fatal error has been detected by the Java Runtime Environment:
INFO | jvm 5 | <DATE_TIME> | #
INFO | jvm 5 | <DATE_TIME> | # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffd8c3570ec, pid=9384, tid=0x0000000000001664
INFO | jvm 5 | <DATE_TIME> | #
INFO | jvm 5 | <DATE_TIME> | # JRE version: Java(TM) SE Runtime Environment (8.0_281-b09) (build 1.8.0_281-b09)
INFO | jvm 5 | <DATE_TIME> | # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.281-b09 mixed mode windows-amd64 compressed oops)
INFO | jvm 5 | <DATE_TIME> | # Problematic frame:
INFO | jvm 5 | <DATE_TIME> | # C [ADVAPI32.dll+0x170ec]
INFO | jvm 5 | <DATE_TIME> | #
INFO | jvm 5 | <DATE_TIME> | # Core dump written. Default location: C:\Program Files\NetApp\SnapManager for Oracle\hs_err_pid<NUMBER>.mdmp
INFO | jvm 5 | <DATE_TIME> | #
INFO | jvm 5 | <DATE_TIME> | # An error report file with more information is saved as:
INFO | jvm 5 | <DATE_TIME> | # C:\Program Files\NetApp\SnapManager for Oracle\hs_err_pid<NUMBER>.login the native class implementation of a Windows SystemEvent access package, as seen from the
hs_err_pid<NUMBER>.log:Stack: [0x000000d748500000,0x000000d748600000], sp=0x000000d7485fec60, free space=1019k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [ADVAPI32.dll+0x171dc]
C [ADVAPI32.dll+0x16d36]
C [com_netapp_common_platform_windows_SystemEventNativeImpl.dll+0x131e]
C 0x000002c801119f4e