Problem Note 63869: A segmentation violation might occur when you expand a metadata library from SAS® Enterprise Guide® or SAS® Studio or execute the DATASETS procedure
 |  |  |  |  |
A segmentation violation might occur in the workspace-server log in the following scenarios:
- You expand a metadata library.
- You access a data set from a metadata library.
- You run PROC DATASETS on the metadata library.
Here is a snippet from the message that occurs in the workspace-server log:
An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [DOSSCHT ]
Read Access Violation DOSSCHT
Exception occurred at(07B59A0C) Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
0000000007B59A0C 0000000006FBE5F0 sasiomet:tkvercn1+0x289CC
0000000007B3B910 0000000006FBE640 sasiomet:tkvercn1+0xA8D0
00000000064187B8 0000000006FBE648 sasyoio:tkvercn1+0x47778
0000000006776190 0000000006FBEA28 sassqxb:tkvercn1+0x5150
0000000006772AC5 0000000006FBEBD0 sassqxb:tkvercn1+0x1A85
0000000006469AEF 0000000006FBEBD8 sasesql:tkvercn1+0x8AAF
000000000653DCBC 0000000006FBEC38 sassqx:tkvercn1+0x3CC7C
00000000064688F7 0000000006FBECF0 sasesql:tkvercn1+0x78B7
00000000064C6B48 0000000006FBECF8 sasyr:tkvercn1+0x35B08
00000000064A9492 0000000006FBF0F0 sasyr:tkvercn1+0x18452
00000000064AF930 0000000006FBF1B0 sasyr:tkvercn1+0x1E8F0
00000000043362B6 0000000006FBF1B8 sasdosm:tkvercn1+0x5276
0000000004334AB1 0000000006FBFBE0 sasdosm:tkvercn1+0x3A71
00000000024EA346 0000000006FBFBE8 sashost:Main+0x11E86
00000000024F040D 0000000006FBFF50 sashost:Main+0x17F4D
00007FFD03928364 0000000006FBFF58 KERNEL32:BaseThreadInitThunk+0x14
00007FFD0452E851 0000000006FBFF88 ntdll:RtlUserThreadStart+0x21
ERROR: Generic critical error.
IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x8003c832
IOM LOGIC VOIMapWrcodeToWoiStatus() No wrcode mapping - using generic error (WOIRAISE): wrcode=0x8003c832
Please contact technical support and provide them with the following traceback information:
The SAS task name is [DOSSCHT ]
Read Access Violation DOSSCHT
Exception occurred at(07B59A0C) Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
0000000007B59A0C 0000000006FBE5F0 sasiomet:tkvercn1+0x289CC
0000000007B3B910 0000000006FBE640 sasiomet:tkvercn1+0xA8D0
00000000064187B8 0000000006FBE648 sasyoio:tkvercn1+0x47778
0000000006776190 0000000006FBEA28 sassqxb:tkvercn1+0x5150
0000000006772AC5 0000000006FBEBD0 sassqxb:tkvercn1+0x1A85
0000000006469AEF 0000000006FBEBD8 sasesql:tkvercn1+0x8AAF
000000000653DCBC 0000000006FBEC38 sassqx:tkvercn1+0x3CC7C
00000000064688F7 0000000006FBECF0 sasesql:tkvercn1+0x78B7
00000000064C6B48 0000000006FBECF8 sasyr:tkvercn1+0x35B08
00000000064A9492 0000000006FBF0F0 sasyr:tkvercn1+0x18452
00000000064AF930 0000000006FBF1B0 sasyr:tkvercn1+0x1E8F0
00000000043362B6 0000000006FBF1B8 sasdosm:tkvercn1+0x5276
0000000004334AB1 0000000006FBFBE0 sasdosm:tkvercn1+0x3A71
00000000024EA346 0000000006FBFBE8 sashost:Main+0x11E86
00000000024F040D 0000000006FBFF50 sashost:Main+0x17F4D
00007FFD03928364 0000000006FBFF58 KERNEL32:BaseThreadInitThunk+0x14
00007FFD0452E851 0000000006FBFF88 ntdll:RtlUserThreadStart+0x21
ERROR: Generic critical error.
IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x8003c832
IOM LOGIC VOIMapWrcodeToWoiStatus() No wrcode mapping - using generic error (WOIRAISE): wrcode=0x8003c832
This issue happens only when the library contains more than 3,000 tables.
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 | Solaris for x64 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 |
| Linux for x64 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| HP-UX IPF | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| 64-bit Enabled Solaris | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| 64-bit Enabled AIX | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Windows 7 Ultimate x64 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Windows 7 Ultimate 32 bit | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Windows 7 Professional x64 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Windows 7 Professional 32 bit | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Windows 7 Home Premium x64 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Windows 7 Home Premium 32 bit | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Windows 7 Enterprise x64 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Windows 7 Enterprise 32 bit | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2019 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2016 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2012 Std | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2012 R2 Std | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2012 Datacenter | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows 10 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows 8.1 Pro x64 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows 8.1 Pro 32-bit | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows 8.1 Enterprise x64 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Pro x64 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Pro 32-bit | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Enterprise x64 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Enterprise 32-bit | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft® Windows® for x64 | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| z/OS | 9.4_M6 | 9.4_M6 | 9.4 TS1M6 | 9.4 TS1M7 | ||
A fix for this issue for Base SAS 9.4_M6 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/D9T.html#63869
A segmentation violation might occur when you expand a metadata library or use clients such as SAS Enterprise Guide or SAS Studio to access a data set from a metadata library.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2019-05-16 10:50:20 |
| Date Created: | 2019-03-19 08:30:28 |