Problem Note 69367: SAS® Metadata Server might become unresponsive after you apply Hot Fix E2A004
 |  |  |  |  |
After you apply the hot fix in SAS Note 66904, SAS Metadata Server might become unresponsive in rare circumstances. The behavior is random and unpredictable.
If SAS Metadata Server debug logging is enabled, the log might contain the error "IOM call failed. Internal server exception: access violation" or a traceback that starts with the following lines might occur:
/sas/prod/software/SASFoundation/9.4/sasexe/tkiomsvc.so(tktracex+0x2e) [0x7f7ac3d9c09e]
/sas/prod/software/SASFoundation/9.4/sasexe/tkiomsvc.so(+0xd949) [0x7f7ac3d20949]
/sas/prod/software/SASFoundation/9.4/sasexe/tkmk.so(bktExcept+0x62) [0x7f7ae96aa472]
/sas/prod/software/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f7ae96aaac4]
/lib64/libpthread.so.0(+0xf630) [0x7f7aeacd3630]
/sas/prod/software/SASFoundation/9.4/sasexe/tkmk.so(skrUnlockRes+0x32) [0x7f7ae96d2312]
/sas/prod/software/SASFoundation/9.4/sasexe/tkoms.so(FOMSsecuritymanagerBuildCredFromGlobalCache+0x483) [0x7f7ab37e6f43]
/sas/prod/software/SASFoundation/9.4/sasexe/tkoms.so(FOMSsecuritymanagerBuildCredentialsForContext+0xb1) [0x7f7ab37e4641]
/sas/prod/software/SASFoundation/9.4/sasexe/tkoms.so(FOMSsecuritymanagerInitSECcontext+0x2ee) [0x7f7ab3839f4e]
/sas/prod/software/SASFoundation/9.4/sasexe/tkoms.so(FOMScontextSetup+0x373) [0x7f7ab37cf3a3]
/sas/prod/software/SASFoundation/9.4/sasexe/tkoms.so(FOMScookiejarGetCookie+0x75) [0x7f7ab38684a5]
/sas/prod/software/SASFoundation/9.4/sasexe/tkomi.so(omiDoRequest+0x233) [0x7f7ac0a9ccc3]
/sas/prod/software/SASFoundation/9.4/sasexe/tkiomsvc.so(+0xd949) [0x7f7ac3d20949]
/sas/prod/software/SASFoundation/9.4/sasexe/tkmk.so(bktExcept+0x62) [0x7f7ae96aa472]
/sas/prod/software/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f7ae96aaac4]
/lib64/libpthread.so.0(+0xf630) [0x7f7aeacd3630]
/sas/prod/software/SASFoundation/9.4/sasexe/tkmk.so(skrUnlockRes+0x32) [0x7f7ae96d2312]
/sas/prod/software/SASFoundation/9.4/sasexe/tkoms.so(FOMSsecuritymanagerBuildCredFromGlobalCache+0x483) [0x7f7ab37e6f43]
/sas/prod/software/SASFoundation/9.4/sasexe/tkoms.so(FOMSsecuritymanagerBuildCredentialsForContext+0xb1) [0x7f7ab37e4641]
/sas/prod/software/SASFoundation/9.4/sasexe/tkoms.so(FOMSsecuritymanagerInitSECcontext+0x2ee) [0x7f7ab3839f4e]
/sas/prod/software/SASFoundation/9.4/sasexe/tkoms.so(FOMScontextSetup+0x373) [0x7f7ab37cf3a3]
/sas/prod/software/SASFoundation/9.4/sasexe/tkoms.so(FOMScookiejarGetCookie+0x75) [0x7f7ab38684a5]
/sas/prod/software/SASFoundation/9.4/sasexe/tkomi.so(omiDoRequest+0x233) [0x7f7ac0a9ccc3]
Once you encounter this issue, you must restart SAS Metadata Server.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Metadata Server | z/OS | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 |
| Microsoft® Windows® for x64 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows 8 Enterprise 32-bit | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows 8 Enterprise x64 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows 8 Pro 32-bit | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows 8 Pro x64 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows 8.1 Enterprise x64 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows 8.1 Pro 32-bit | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows 8.1 Pro x64 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows 10 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2008 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2008 R2 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2008 for x64 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2012 Datacenter | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2012 R2 Std | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2012 Std | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2016 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2019 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Windows 7 Enterprise 32 bit | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Windows 7 Enterprise x64 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Windows 7 Home Premium 32 bit | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Windows 7 Home Premium x64 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Windows 7 Professional 32 bit | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Windows 7 Professional x64 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Windows 7 Ultimate 32 bit | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Windows 7 Ultimate x64 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| 64-bit Enabled AIX | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| 64-bit Enabled Solaris | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| HP-UX IPF | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Linux for x64 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
| Solaris for x64 | 9.4_M6 | 9.4_M8 | 9.4 TS1M6 | 9.4 TS1M8 | ||
A fix for this issue for Threaded Kernel Metadata Component 9.4_M7 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/J5A.html#69367A fix for this issue for Threaded Kernel Metadata Component 9.4_M6 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/E2A.html#69367| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2022-11-29 16:06:16 |
| Date Created: | 2022-07-04 05:24:44 |