Problem Note 65245: Read Access Violation errors or a warning occur when you route output to ODS destinations in a DBCS environment and a custom translation table is used
 |  |  |  |  |
If you use custom translation tables and you route procedure output to an Output Delivery System (ODS) destination in a SAS® session encoding that uses double-byte character set (DBCS) encoding, Read Access Violation errors that are similar to the following can appear in the SAS log:
135 options trantab=(,,,,,,,,,custtab);
NOTE: User DBCS translation table CUSTTAB registered.
138 proc print data=sashelp.class;
139 run;
NOTE: User DBCS translation table CUSTTAB registered.
138 proc print data=sashelp.class;
139 run;
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [PRINT]
ERROR: Read Access Violation PRINT
Exception occurred at (07E1DA47)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
0000000007E1DA47 000000002EA7CA20 sasxkern:tkvercn1+0x5C9F7
0000000007E1D9D2 000000002EA7CA60 sasxkern:tkvercn1+0x5C982
000000000F3A5620 000000002EA7CA68 sastags:tkvercn1+0x845D0
000000000F27C024 000000002EA7CD18 sasxml:tkvercn1+0xAAFD4
000000000F1D269A 000000002EA7CE10 sasxml:tkvercn1+0x164A
000000000A4EB750 000000002EA7CE18 sasods:tkvercn1+0x35A700
000000000A31B07C 000000002EA7D430 sasods:tkvercn1+0x18A02C
000000000A303B8E 000000002EA7D850 sasods:tkvercn1+0x172B3E
000000000A4EB750 000000002EA7D8E0 sasods:tkvercn1+0x35A700
000000000A2538AA 000000002EA7E170 sasods:tkvercn1+0xC285A
000000000F784D97 000000002EA7E178 sasprint:tkvercn1+0x3D47
000000000F78111B 000000002EA7FB60 sasprint:tkvercn1+0xCB
0000000005C76225 000000002EA7FB68 sashost:Main+0x26F35
0000000005C80954 000000002EA7FF50 sashost:Main+0x31664
00007FFE695737E4 000000002EA7FF58 KERNEL32:BaseThreadInitThunk+0x14
00007FFE6A92CB81 000000002EA7FF88 ntdll:RtlUserThreadStart+0x21
NOTE: The SAS System stopped processing this step because of errors.
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [PRINT]
ERROR: Read Access Violation PRINT
Exception occurred at (07E1DA47)
NOTE: There were 19 observations read from the data set SASHELP.CLASS.
NOTE: PROCEDURE PRINT used (Total process time):
real time 0.08 seconds
cpu time 0.04 seconds
140 ods html close;
Please contact technical support and provide them with the following traceback information:
The SAS task name is [PRINT]
ERROR: Read Access Violation PRINT
Exception occurred at (07E1DA47)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
0000000007E1DA47 000000002EA7CA20 sasxkern:tkvercn1+0x5C9F7
0000000007E1D9D2 000000002EA7CA60 sasxkern:tkvercn1+0x5C982
000000000F3A5620 000000002EA7CA68 sastags:tkvercn1+0x845D0
000000000F27C024 000000002EA7CD18 sasxml:tkvercn1+0xAAFD4
000000000F1D269A 000000002EA7CE10 sasxml:tkvercn1+0x164A
000000000A4EB750 000000002EA7CE18 sasods:tkvercn1+0x35A700
000000000A31B07C 000000002EA7D430 sasods:tkvercn1+0x18A02C
000000000A303B8E 000000002EA7D850 sasods:tkvercn1+0x172B3E
000000000A4EB750 000000002EA7D8E0 sasods:tkvercn1+0x35A700
000000000A2538AA 000000002EA7E170 sasods:tkvercn1+0xC285A
000000000F784D97 000000002EA7E178 sasprint:tkvercn1+0x3D47
000000000F78111B 000000002EA7FB60 sasprint:tkvercn1+0xCB
0000000005C76225 000000002EA7FB68 sashost:Main+0x26F35
0000000005C80954 000000002EA7FF50 sashost:Main+0x31664
00007FFE695737E4 000000002EA7FF58 KERNEL32:BaseThreadInitThunk+0x14
00007FFE6A92CB81 000000002EA7FF88 ntdll:RtlUserThreadStart+0x21
NOTE: The SAS System stopped processing this step because of errors.
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [PRINT]
ERROR: Read Access Violation PRINT
Exception occurred at (07E1DA47)
NOTE: There were 19 observations read from the data set SASHELP.CLASS.
NOTE: PROCEDURE PRINT used (Total process time):
real time 0.08 seconds
cpu time 0.04 seconds
140 ods html close;
Instead of an error, you might get this warning in the log:
WARNING: No output destinations active
In addition to the log errors or warning, no output is produced.
The following code example replicates this issue in either SAS® 9.4M5 (TS1M5) or SAS® 9.4 M6 (TS1M6). The HTML procedure output is not created.
data trantab;
pcms='8342'x; dec='b9b3'x;
run;
proc dbcstab
name=custtab
basetype=pcms
data=trantab
dbcslang=japanese
catalog=sasuser.dbcs
verify;
run;
pcms='8342'x; dec='b9b3'x;
run;
proc dbcstab
name=custtab
basetype=pcms
data=trantab
dbcslang=japanese
catalog=sasuser.dbcs
verify;
run;
options trantab=(,,,,,,,,,custtab);
filename myfile "c:\temp\test.html";
ods html file=myfile;
proc print data=sashelp.class;
run;
ods html close;
filename myfile "c:\temp\test.html";
ods html file=myfile;
proc print data=sashelp.class;
run;
ods html close;
As a workaround, you can route procedure output to the LISTING destination. If the LISTING destination is not already open, you can open it by submitting the following ODS statement:
ods listing;
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 | Base SAS | z/OS | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 |
| z/OS 64-bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft® Windows® for x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Enterprise 32-bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Enterprise x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Pro 32-bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Pro x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8.1 Enterprise x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8.1 Pro 32-bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8.1 Pro x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 10 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2008 | 9.4_M5 | 9.4 TS1M5 | ||||
| Microsoft Windows Server 2008 R2 | 9.4_M5 | 9.4 TS1M5 | ||||
| Microsoft Windows Server 2008 for x64 | 9.4_M5 | 9.4 TS1M5 | ||||
| Microsoft Windows Server 2012 Datacenter | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2012 R2 Std | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2012 Std | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2016 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Enterprise 32 bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Enterprise x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Home Premium 32 bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Home Premium x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Professional 32 bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Professional x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Ultimate 32 bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Ultimate x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| 64-bit Enabled AIX | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| 64-bit Enabled Solaris | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| HP-UX IPF | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Linux for x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Solaris for x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 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#65245A fix for this issue for Base SAS 9.4_M5 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/B6Q.html#65245
Read Access Violations might occur in the SAS® log when you route procedure output to an ODS destination in a DBCS environment and custom translation tables are specified in the TRANTAB system option.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2019-12-18 13:33:48 |
| Date Created: | 2019-12-11 15:56:49 |