Problem Note 68922: A Segmentation Violation or Read Access Violation might occur when data is bulk-loaded to a Microsoft Azure Synapse database
 |  |  |  |  |
When you attempt to insert data into an Azure Synapse database, a Segmentation Violation or Read Access Violation might occur, and SAS® then exits.
The SAS log might show messages that are similar to the following for the APPEND procedure:
22 OPTIONS AZURETENANTID="azure-tenant-id";
23 LIBNAME libref SQLSVR DSN='dsn-name' USER='user-name' PASSWORD="password"
24 SCHEMA='schema-name'
25 BULKLOAD=YES
26 BL_APPLICATIONID="application-id"
27 BL_ACCOUNTNAME="account-Name"
28 BL_FILESYSTEM='file-system-name'
29 BL_IDENTITY='Shared Access Signature'
30 BL_SECRET='secret';
31 PROC APPEND BASE=libref.sample_table DATA=sashelp.class ; RUN ;
23 LIBNAME libref SQLSVR DSN='dsn-name' USER='user-name' PASSWORD="password"
24 SCHEMA='schema-name'
25 BULKLOAD=YES
26 BL_APPLICATIONID="application-id"
27 BL_ACCOUNTNAME="account-Name"
28 BL_FILESYSTEM='file-system-name'
29 BL_IDENTITY='Shared Access Signature'
30 BL_SECRET='secret';
31 PROC APPEND BASE=libref.sample_table DATA=sashelp.class ; RUN ;
NOTE: Appending SASHELP.CLASS to libref.sample_table.
NOTE: There were 19 observations read from the data set SASHELP.CLASS.
NOTE: 19 observations added.
NOTE: The data set libref.sample_table has . observations and 5 variables.
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [APPEND]
ERROR: Read Access Violation APPEND
Exception occurred at (68B6968B)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
00007FFD68B6968B 000000AD6C5F6160 sasiosrv:tkvercn1+0x5864B
00007FFD68B68E48 000000AD6C5F7550 sasiosrv:tkvercn1+0x57E08
00007FFD68B1D357 000000AD6C5F8090 sasiosrv:tkvercn1+0xC317
00007FFD44F87703 000000AD6C5F8098 sasxdbi:tkvercn1+0x466C3
00007FFD44F468EB 000000AD6C5F9220 sasxdbi:tkvercn1+0x58AB
00007FFD434A1D87 000000AD6C5F9228 sasyoio:tkvercn1+0xD47
00007FFD4283853B 000000AD6C5F9FF8 sasqutil:tkvercn1+0x474FB
00007FFD427FDA16 000000AD6C5FEF90 sasqutil:tkvercn1+0xC9D6
00007FFD4280FA3E 000000AD6C5FF360 sasqutil:tkvercn1+0x1E9FE
00007FFD48A9F100 000000AD6C5FF368 sasxshel:tkvercn1+0x4E0C0
00007FFD4284976D 000000AD6C5FF480 sasqutil:tkvercn1+0x5872D
00007FFD427F1499 000000AD6C5FF570 sasqutil:tkvercn1+0x459
00007FFD3754F5A8 000000AD6C5FF578 sashost:Main+0x15268
00007FFD375559CC 000000AD6C5FF8A0 sashost:Main+0x1B68C
00007FFDBA457C24 000000AD6C5FF8A8 KERNEL32:BaseThreadInitThunk+0x14
00007FFDBB12D721 000000AD6C5FF8D8 ntdll:RtlUserThreadStart+0x21
NOTE: There were 19 observations read from the data set SASHELP.CLASS.
NOTE: 19 observations added.
NOTE: The data set libref.sample_table has . observations and 5 variables.
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [APPEND]
ERROR: Read Access Violation APPEND
Exception occurred at (68B6968B)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
00007FFD68B6968B 000000AD6C5F6160 sasiosrv:tkvercn1+0x5864B
00007FFD68B68E48 000000AD6C5F7550 sasiosrv:tkvercn1+0x57E08
00007FFD68B1D357 000000AD6C5F8090 sasiosrv:tkvercn1+0xC317
00007FFD44F87703 000000AD6C5F8098 sasxdbi:tkvercn1+0x466C3
00007FFD44F468EB 000000AD6C5F9220 sasxdbi:tkvercn1+0x58AB
00007FFD434A1D87 000000AD6C5F9228 sasyoio:tkvercn1+0xD47
00007FFD4283853B 000000AD6C5F9FF8 sasqutil:tkvercn1+0x474FB
00007FFD427FDA16 000000AD6C5FEF90 sasqutil:tkvercn1+0xC9D6
00007FFD4280FA3E 000000AD6C5FF360 sasqutil:tkvercn1+0x1E9FE
00007FFD48A9F100 000000AD6C5FF368 sasxshel:tkvercn1+0x4E0C0
00007FFD4284976D 000000AD6C5FF480 sasqutil:tkvercn1+0x5872D
00007FFD427F1499 000000AD6C5FF570 sasqutil:tkvercn1+0x459
00007FFD3754F5A8 000000AD6C5FF578 sashost:Main+0x15268
00007FFD375559CC 000000AD6C5FF8A0 sashost:Main+0x1B68C
00007FFDBA457C24 000000AD6C5FF8A8 KERNEL32:BaseThreadInitThunk+0x14
00007FFDBB12D721 000000AD6C5FF8D8 ntdll:RtlUserThreadStart+0x21
SAS WTABORT (APPEND) The SAS System has detected an abort condition. An Exception occurred during wthtrm().
Please Contact Technical Support.
Please Contact Technical Support.
The log could also display information that is similar to the following for the SQL procedure:
31 PROC SQL ;
32 INSERT INTO libref.sample_table (name, sex, age, height, weight)
33 SELECT name, sex, age, height, weight
34 FROM sashelp.class
NOTE: 19 rows were inserted into libref.sample_table.
32 INSERT INTO libref.sample_table (name, sex, age, height, weight)
33 SELECT name, sex, age, height, weight
34 FROM sashelp.class
NOTE: 19 rows were inserted into libref.sample_table.
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [SQL]
ERROR: Read Access Violation SQL
Exception occurred at (4373968B)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
00007FFD4373968B 000000ACA07FAFC0 sasiosrv:tkvercn1+0x5864B
00007FFD43738E48 000000ACA07FC3B0 sasiosrv:tkvercn1+0x57E08
00007FFD436ED357 000000ACA07FCEF0 sasiosrv:tkvercn1+0xC317
00007FFD434D7703 000000ACA07FCEF8 sasxdbi:tkvercn1+0x466C3
00007FFD434968EB 000000ACA07FE080 sasxdbi:tkvercn1+0x58AB
00007FFD35ED1D87 000000ACA07FE088 sasyoio:tkvercn1+0xD47
00007FFD3D99864E 000000ACA07FEE58 sassqx:tkvercn1+0x3760E
00007FFD3D99739B 000000ACA07FF3C0 sassqx:tkvercn1+0x3635B
00007FFD3D9963D9 000000ACA07FF460 sassqx:tkvercn1+0x35399
00007FFD44FA146C 000000ACA07FF468 sassql:tkvercn1+0x42C
00007FFD3723F5A8 000000ACA07FF528 sashost:Main+0x15268
00007FFD372459CC 000000ACA07FF850 sashost:Main+0x1B68C
00007FFDBA457C24 000000ACA07FF858 KERNEL32:BaseThreadInitThunk+0x14
00007FFDBB12D721 000000ACA07FF888 ntdll:RtlUserThreadStart+0x21
Please contact technical support and provide them with the following traceback information:
The SAS task name is [SQL]
ERROR: Read Access Violation SQL
Exception occurred at (4373968B)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
00007FFD4373968B 000000ACA07FAFC0 sasiosrv:tkvercn1+0x5864B
00007FFD43738E48 000000ACA07FC3B0 sasiosrv:tkvercn1+0x57E08
00007FFD436ED357 000000ACA07FCEF0 sasiosrv:tkvercn1+0xC317
00007FFD434D7703 000000ACA07FCEF8 sasxdbi:tkvercn1+0x466C3
00007FFD434968EB 000000ACA07FE080 sasxdbi:tkvercn1+0x58AB
00007FFD35ED1D87 000000ACA07FE088 sasyoio:tkvercn1+0xD47
00007FFD3D99864E 000000ACA07FEE58 sassqx:tkvercn1+0x3760E
00007FFD3D99739B 000000ACA07FF3C0 sassqx:tkvercn1+0x3635B
00007FFD3D9963D9 000000ACA07FF460 sassqx:tkvercn1+0x35399
00007FFD44FA146C 000000ACA07FF468 sassql:tkvercn1+0x42C
00007FFD3723F5A8 000000ACA07FF528 sashost:Main+0x15268
00007FFD372459CC 000000ACA07FF850 sashost:Main+0x1B68C
00007FFDBA457C24 000000ACA07FF858 KERNEL32:BaseThreadInitThunk+0x14
00007FFDBB12D721 000000ACA07FF888 ntdll:RtlUserThreadStart+0x21
SAS WTABORT (SQL) The SAS System has detected an abort condition. An Exception occurred during wthtrm().
Please Contact Technical Support.
Please Contact Technical Support.
The only workaround is to use the BULKLOAD=NO option.
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/ACCESS Interface to Microsoft SQL Server | Microsoft® Windows® for x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 |
| Microsoft Windows 8 Enterprise 32-bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8 Enterprise x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8 Pro 32-bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8 Pro x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8.1 Enterprise x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8.1 Pro 32-bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8.1 Pro x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 10 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 11 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2008 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2008 R2 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2008 for x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2012 Datacenter | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2012 R2 Std | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2012 Std | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2016 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2019 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2022 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Enterprise 32 bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Enterprise x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Home Premium 32 bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Home Premium x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Professional 32 bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Professional x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Ultimate 32 bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Ultimate x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| 64-bit Enabled AIX | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| 64-bit Enabled Solaris | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| HP-UX IPF | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Linux for x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Solaris for x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
A fix for this issue for SAS/ACCESS Interface to Microsoft SQL Server 9.45 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/J6Q.html#68922
When you use SAS/ACCESS® Interface to Microsoft SQL Server, with the BULKLOAD=YES option for an existing table, a Segmentation Violation or Read Access Violation might occur.
| Type: | Problem Note |
| Priority: | high |
| Topic: | Data Management ==> Data Sources ==> External Databases ==> MS SQL Server SAS Reference ==> Procedures ==> APPEND SAS Reference ==> Procedures ==> SQL |
| Date Modified: | 2022-04-04 14:04:55 |
| Date Created: | 2022-02-15 08:44:09 |