SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 70913: The SAS® Environment Manager agent fails to start after applying the SAS® Private JRE build 1.8.0_402 in SAS® 9.4M7 (TS1M7) environments

DetailsHotfixAboutRate It

On Microsoft Windows, the SAS Environment Manager agent might fail to start with the following error in the wrapper.log:

INFO   | jvm 2    | 2024/03/25 16:31:16 | # A fatal error has been detected by the Java Runtime Environment:
INFO   | jvm 2    | 2024/03/25 16:31:16 | #
INFO   | jvm 2    | 2024/03/25 16:31:16 | #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fff1d0b394c, pid=15204, tid=0x0000000000006370
INFO   | jvm 2    | 2024/03/25 16:31:16 | #
INFO   | jvm 2    | 2024/03/25 16:31:16 | # JRE version: OpenJDK Runtime Environment (Zulu 8.76.0.18-SA-win64) (8.0_402-b06) (build 1.8.0_402-b06)
INFO   | jvm 2    | 2024/03/25 16:31:16 | # Java VM: OpenJDK 64-Bit Server VM (25.402-b06 mixed mode windows-amd64 compressed oops)
INFO   | jvm 2    | 2024/03/25 16:31:16 | # Problematic frame:
INFO   | jvm 2    | 2024/03/25 16:31:16 | # C  [ADVAPI32.dll+0x1394c]
INFO   | jvm 2    | 2024/03/25 16:31:16 | #
INFO   | jvm 2    | 2024/03/25 16:31:16 | # Core dump written. Default location: C:\SAS\Config\Lev1\Web\SASEnvironmentManager\agent-5.8.0-EE\wrapper\sbin\hs_err_pid15204.mdmp
INFO   | jvm 2    | 2024/03/25 16:31:16 | #
INFO   | jvm 2    | 2024/03/25 16:31:16 | # An error report file with more information is saved as:
INFO   | jvm 2    | 2024/03/25 16:31:16 | # C:\SAS\Config\Lev1\Web\SASEnvironmentManager\agent-5.8.0-EE\wrapper\sbin\hs_err_pid15204.log
INFO   | jvm 2    | 2024/03/25 16:31:16 | #
INFO   | jvm 2    | 2024/03/25 16:31:16 | # If you would like to submit a bug report, please visit:
INFO   | jvm 2    | 2024/03/25 16:31:16 | #   http://www.azul.com/support/
INFO   | jvm 2    | 2024/03/25 16:31:16 | # The crash happened outside the Java Virtual Machine in native code.
INFO   | jvm 2    | 2024/03/25 16:31:16 | # See problematic frame for where to report the bug.
INFO   | jvm 2    | 2024/03/25 16:31:16 | #

This issue might occur if you applied the SAS Private Java Runtime Environment (JRE) build 1.8.0_402 in a SAS 9.4M7 environment on Windows 11 or Windows 2022. 

Click the Hot Fix tab in this note to access the hot fix for this issue.

Note: A similar problem occurs when applying JRE updates. For more information, see SAS Note 68578, "SAS® Environment Manager fails to start with "EXCEPTION_ACCESS_VIOLATION" after applying the SAS Private Java Runtime Environment (JRE) update."



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Environment ManagerMicrosoft® Windows® for x642.5_M49.4 TS1M7
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.