Problem Note 63744: The FILENAME EMAIL access method with the EMAILSYS MAPI option fails after you run an EXPORT or IMPORT procedure with certain DBMS= options
The FILENAME EMAIL access method with the EMAILSYS MAPI option for Microsoft Outlook 2016 might work successfully until you submit PROC EXPORT or PROC IMPORT with one of the following DBMS= options: EXCEL2000, EXCEL, ACCESS2000, or ACCESS.
After the PROC EXPORT or PROC IMPORT code runs successfully, any subsequent code for the FILENAME EMAIL access method fails. In your SAS log, you see errors that are similar to the following:
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [DATASTEP]
ERROR: Write Access Violation DATASTEP
Exception occurred at (F01F6277)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
00007FFBF01F6277 0000000044DED3C0 mso20win32client:Ordinal832+0x10B
00007FFBF01F639B 0000000044DED400 mso20win32client:Ordinal116+0xF
00007FFB2166E860 000000000F1DC7F8 mso99Lwin32client:Ordinal252+0x83004
00007FFB2158254D 000000000F1DCF30 mso99Lwin32client:Ordinal1716+0x2FD
00007FFB21582419 000000000F1DCFF0 mso99Lwin32client:Ordinal1716+0x1C9
00007FFB214F4C96 000000000F1DD040 mso99Lwin32client:Ordinal652+0x332
00007FFB21586B35 000000000F1DD070 mso99Lwin32client:Ordinal88+0x25
00007FFB316E973D 000000000F1DD078 olmapi32:HrEnsureFlights+0x2B9
00007FFB31635DFD 000000000F1DD3A0 olmapi32:MAPIInitIdle+0x1FD
00007FFB31635D83 000000000F1DD400 olmapi32:MAPIInitIdle+0x183
00007FFB31635D28 000000000F1DD430 olmapi32:MAPIInitIdle+0x128
00007FFB31635C37 000000000F1DD460 olmapi32:MAPIInitIdle+0x37
00007FFB310C1542 000000000F1DD468 contab32:ABProviderInit+0x86
00007FFB316351E5 000000000F1DD5B0 olmapi32:ScCopyProps+0xBE5
00007FFB31634C41 000000000F1DD6F0 olmapi32:ScCopyProps+0x641
00007FFB31633E3E 000000000F1DD830 olmapi32:FBadRestriction+0xA6E
00007FFB3162554C 000000000F1DD940 olmapi32:IsBadBoundedStringPtr+0x5FC
00007FFB31624DD8 000000000F1DD9D0 olmapi32:MAPILogonEx+0x168
00007FFB31A42DE1 000000000F1DDAE0 olmapi32:MAPIResolveName+0x10BD
00007FFB31A4314B 000000000F1DDB20 olmapi32:MAPILogon+0x2F
00007FFB3A5C7EE4 000000000F1DDB28 MSMAPI32:MAPILogon+0xA4
00007FFB3515D858 000000000F1DDB78 MAPI32:MAPILogon+0xB8
00000000095C22E4 000000000F1DDBE8 sasvmail:hxeinit_ui+0x18B24
00000000095A985A 000000000F1DDE70 sasvmail:hxeinit_ui+0x9A
00000000095A4EC4 000000000F1DDFE0 sasvmail:tkvercn1+0x3E84
00000000095A1C7E 000000000F1DE060 sasvmail:tkvercn1+0xC3E
000000000700CEA7 000000000F1DE068 sasxkern:tkvercn1+0x8BE67
000000000E5FDD0A 000000000F1DE378 sasdsx:tkvercn1+0x1CCCA
000000000E5F970F 000000000F1DE830 sasdsx:tkvercn1+0x186CF
000000000E5E149B 000000000F1DE8A0 sasdsx:tkvercn1+0x45B
00000000096DBA00 000000000F1DE8A8 sasds:tkvercn1+0xA9C0
00000000096D5466 000000000F1DF440 sasds:tkvercn1+0x4426
000000000555A066 000000000F1DF448 sashost:Main+0x11BA6
000000000556011D 000000000F1DF7B0 sashost:Main+0x17C5D
00007FFB4CC41FE4 000000000F1DF7B8 KERNEL32:BaseThreadInitThunk+0x14
00007FFB4D7BEFC1 000000000F1DF7E8 ntdll:RtlUserThreadStart+0x21
The following information can also possibly appear:
77D558ED 0FEEFCEC ntdll:RtlGetAppContainerNamedObjectPath+0xFD
77D558BD 0FEEFCFC ntdll:RtlGetAppContainerNamedObjectPath+0xCD
ERROR: Read Access Violation DATASTEP
00007FF8C718A02B 000000003529DFD0 KERNELBASE:FileTimeToSystemTime+0x1B
The error messages occur because of a conflict with the drivers for Microsoft Access Database Engine 2016 (ACE engine). This problem does not occur with drivers for Microsoft Access Database Engine 2013 (ACE engine).
To confirm that your environment has this issue, take these steps:
- In your SAS® session, submit the following code:
proc options option=emailsys value;
run;
- Check the SAS log to verify that Value: MAPI appears.
- On your PC, type the following in the Search box:
odbc data sources
- Select the 32-bit or 64-bit desktop application that matches the bitness of your Microsoft Office installation.
- Open the ODBC Data Source Administrator (either 32-bit or 64-bit) and select the Drivers tab.
- Contact SAS Technical Support and provide a screen shot of all Microsoft Access drivers. Provide the Name, Version, File, Company, and Date information.
To work around this issue, use one of the following options:
- Option 1: Use the SAS SMTP email option. See SAS Note 19767, “Using SAS® software to send SMTP email.”
- Option 2: Change the PROC EXPORT or PROC IMPORT code to use the DBMS=XLSX option. However, if you have multiple sheets or tabs in your Microsoft Excel file, you must include the SHEET="sheet-name" option.
Operating System and Release Information
SAS System | Base SAS | Microsoft® Windows® for x64 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows 8 Enterprise x64 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows 8 Pro x64 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows 8.1 Enterprise 32-bit | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows 8.1 Enterprise x64 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows 8.1 Pro 32-bit | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows 8.1 Pro x64 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows 10 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows Server 2008 R2 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows Server 2008 for x64 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows Server 2012 Datacenter | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows Server 2012 R2 Datacenter | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows Server 2012 R2 Std | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows Server 2012 Std | 9.4 | | 9.4 TS1M0 | |
Windows 7 Enterprise x64 | 9.4 | | 9.4 TS1M0 | |
Windows 7 Professional x64 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows Server 2016 | 9.4_M5 | | 9.4 TS1M5 | |
*
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.
The FILENAME EMAIL access method might produce the error messages "An exception has been encountered" and "ERROR: Write Access Violation DATASTEP" after you run PROC EXPORT or IMPORT with the following DBMS= options: EXCEL2000, EXCEL, ACCESS2000, or ACCESS.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2019-07-15 12:45:57 |
Date Created: | 2019-02-26 11:31:08 |