Problem Note 58444: An "illegal instruction" error and application crash occur when you are using SAS/ACCESS® Interface to ODBC to connect to Microsoft SQL Server
An "illegal instruction" error condition and system crash might occur when you are using SAS/ACCESS Interface to ODBC. The problem occurs when you connect to Microsoft SQL Server and the CONNECTION= option is set to UNIQUE (the default). An initial connection from SAS/ACCESS Interface to an ODBC data source is successful, but a subsequent connection fails.
The issue occurs because SAS frees the SQL dictionary memory on the failed connection that is reusing the SQL dictionary pointer from the initial successful connection. The next time you try to free the memory, the crash and traceback occur.
A potential workaround is to set the CONNECTION= option to something other than the default of UNIQUE. However, doing so might adversely impact performance.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to ODBC | Microsoft Windows Server 2012 Datacenter | 9.3 TS1M2 | |
Microsoft Windows Server 2012 R2 Datacenter | 9.3 TS1M2 | |
Microsoft Windows Server 2012 R2 Std | 9.3 TS1M2 | |
Microsoft Windows Server 2012 Std | 9.3 TS1M2 | |
Microsoft Windows XP Professional | 9.3 TS1M2 | |
Windows 7 Enterprise 32 bit | 9.3 TS1M2 | |
Windows 7 Enterprise x64 | 9.3 TS1M2 | |
Microsoft Windows Server 2008 | 9.3 TS1M2 | |
Microsoft Windows 8.1 Pro 32-bit | 9.3 TS1M2 | |
Microsoft Windows 8.1 Enterprise x64 | 9.3 TS1M2 | |
Microsoft Windows 8.1 Enterprise 32-bit | 9.3 TS1M2 | |
Microsoft Windows 8 Pro x64 | 9.3 TS1M2 | |
Microsoft Windows 8 Pro 32-bit | 9.3 TS1M2 | |
Microsoft Windows 8 Enterprise x64 | 9.3 TS1M2 | |
Microsoft Windows 8 Enterprise 32-bit | 9.3 TS1M2 | |
Microsoft Windows Server 2008 for x64 | 9.3 TS1M2 | |
Microsoft Windows Server 2008 R2 | 9.3 TS1M2 | |
Microsoft Windows Server 2003 for x64 | 9.3 TS1M2 | |
Microsoft Windows Server 2003 Standard Edition | 9.3 TS1M2 | |
Microsoft Windows Server 2003 Enterprise Edition | 9.3 TS1M2 | |
Microsoft Windows Server 2003 Datacenter Edition | 9.3 TS1M2 | |
Microsoft Windows 8.1 Pro x64 | 9.3 TS1M2 | |
Microsoft® Windows® for x64 | 9.3 TS1M2 | |
Windows 7 Home Premium 32 bit | 9.3 TS1M2 | |
Windows 7 Home Premium x64 | 9.3 TS1M2 | |
Windows 7 Professional 32 bit | 9.3 TS1M2 | |
Windows 7 Professional x64 | 9.3 TS1M2 | |
Windows 7 Ultimate 32 bit | 9.3 TS1M2 | |
Windows 7 Ultimate x64 | 9.3 TS1M2 | |
Windows Vista | 9.3 TS1M2 | |
Windows Vista for x64 | 9.3 TS1M2 | |
64-bit Enabled AIX | 9.3 TS1M2 | |
64-bit Enabled HP-UX | 9.3 TS1M2 | |
64-bit Enabled Solaris | 9.3 TS1M2 | |
HP-UX IPF | 9.3 TS1M2 | |
Linux | 9.3 TS1M2 | |
Linux for x64 | 9.3 TS1M2 | |
Solaris for x64 | 9.3 TS1M2 | |
*
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.
An error condition and system crash occur when you use SAS/ACCESS Interface to ODBC to connect to Microsoft SQL Server and CONNECTION= is set to the default setting of UNIQUE.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2016-06-24 14:01:46 |
Date Created: | 2016-06-20 09:52:12 |