<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic SAS WTABORT (EXPORT) The SAS System has detected an abort condition in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/SAS-WTABORT-EXPORT-The-SAS-System-has-detected-an-abort/m-p/807952#M318584</link>
    <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;
&lt;P&gt;When I export 2 SAS datasets to Excel, the first one goes fine, then I received the following error when the 2nd file is being exported.&lt;/P&gt;
&lt;P&gt;The log below I got from my SAS running in batch.&lt;/P&gt;
&lt;P&gt;Recently, when I manually run the export, sometime SAS automatically shutdown. In these instance, I dont have a log file to see what is going on.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now I have the log. Can you please review and see what can I do to fix?&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;HHC&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;proc export data=m44_UP
outfile="C:\Users\OneDrive\........\file1_UP_&amp;amp;today..xlsx"
replace;
run;

proc export data=m44_DOWN
outfile="C:\Users\OneDrive \.........\file1_DOWN_&amp;amp;today..xlsx"
replace;
run;
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;NOTE: File "C:\Users\OneDrive\.......\file1_UP_20220414.xlsx" will be created if the export process succeeds.&lt;BR /&gt;NOTE: "M44_UP" range/sheet was successfully created.&lt;BR /&gt;NOTE: PROCEDURE EXPORT used (Total process time):&lt;BR /&gt;real time 0.33 seconds&lt;BR /&gt;cpu time 0.20 seconds&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;NOTE: File "C:\Users\OneDrive\......\file2_DOWN_20220414.xlsx" will be created if the export process succeeds.&lt;BR /&gt;&lt;BR /&gt;ERROR: An exception has been encountered.&lt;BR /&gt;Please contact technical support and provide them with the following traceback information:&lt;BR /&gt;&lt;BR /&gt;The SAS task name is [EXPORT]&lt;BR /&gt;ERROR: Read Access Violation EXPORT&lt;BR /&gt;Exception occurred at (0795C006)&lt;BR /&gt;Task Traceback&lt;BR /&gt;Address Frame (DBGHELP API Version 4.0 rev 5)&lt;BR /&gt;000000000795C006 00000000096CB910 sasjet:tkvercn1+0xAFC6&lt;BR /&gt;0000000007D5DFF8 00000000096CB918 sasiojet:tkvercn1+0xCFB8&lt;BR /&gt;0000000007DF3828 00000000096CB9B8 sasxdbi:tkvercn1+0x427E8&lt;BR /&gt;0000000007DC77A1 00000000096CBA90 sasxdbi:tkvercn1+0x16761&lt;BR /&gt;0000000004919F84 00000000096CBA98 sasyh:tkvercn1+0x18F44&lt;BR /&gt;0000000004BB83C9 00000000096CBC18 sasxshel:tkvercn1+0x27389&lt;BR /&gt;0000000004B9344E 00000000096CC0C0 sasxshel:tkvercn1+0x240E&lt;BR /&gt;0000000004B919F5 00000000096CC150 sasxshel:tkvercn1+0x9B5&lt;BR /&gt;0000000004BBC332 00000000096CC2D0 sasxshel:tkvercn1+0x2B2F2&lt;BR /&gt;0000000004BE81C2 00000000096CC630 sasxshel:tkvercn1+0x57182&lt;BR /&gt;0000000004BEBDC4 00000000096CC720 sasxshel:tkvercn1+0x5AD84&lt;BR /&gt;&amp;#12;116 The SAS System 17:12 Thursday, April 14, 2022&lt;/P&gt;
&lt;P&gt;0000000004BE5015 00000000096CC7C0 sasxshel:tkvercn1+0x53FD5&lt;BR /&gt;0000000007771877 00000000096CC7C8 sasimdts:tkvercn1+0x837&lt;BR /&gt;000000000774372A 00000000096CC8C8 sasimode:tkvercn1+0x26EA&lt;BR /&gt;0000000005584497 00000000096CE9C8 sasimctr:tkvercn1+0x3457&lt;BR /&gt;00000000055817FB 00000000096CF820 sasimctr:tkvercn1+0x7BB&lt;BR /&gt;00000000055612B0 00000000096CF828 sasexpor:tkvercn1+0x270&lt;BR /&gt;000000000349A066 00000000096CF9B8 sashost:Main+0x11BA6&lt;BR /&gt;00000000034A011D 00000000096CFD20 sashost:Main+0x17C5D&lt;BR /&gt;00007FF842F97034 00000000096CFD28 KERNEL32:BaseThreadInitThunk+0x14&lt;BR /&gt;00007FF844BA2651 00000000096CFD58 ntdll:RtlUserThreadStart+0x21&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;SAS WTABORT (EXPORT) The SAS System has detected an abort condition. An Exception occurred &lt;BR /&gt;during wthtrm(). &lt;BR /&gt;Please Contact Technical Support.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Tasks&lt;/P&gt;
&lt;P&gt;[MAIN ] [WAITING ] pri[ 5] reb[03366E40] WC[0] WN[1]&lt;BR /&gt;[IDLETASK] [READY ] pri[ 9] reb[03366E40]&lt;BR /&gt;[EVENTTSK] [WAITING ] pri[ 0] reb[03366E40] WC[0] WN[1]&lt;BR /&gt;[sasxkern] [WAITING ] pri[ 3] reb[03366E40] WC[0] WN[1]&lt;BR /&gt;[SGIOREAD] [WAITING ] pri[ 3] reb[03366E40] WC[0] WN[1]&lt;BR /&gt;[SGIOWRIT] [WAITING ] pri[ 3] reb[03366E40] WC[0] WN[1]&lt;BR /&gt;[Session ] [WAITING ] pri[ 3] reb[04C77FA0] WC[0] WN[1]&lt;BR /&gt;[TKSRV ] [WAITING ] pri[ 3] reb[04C78620] WC[0] WN[1]&lt;BR /&gt;[Program ] [WAITING ] pri[ 7] reb[04C79140] WC[0] WN[1]&lt;BR /&gt;[SASODR ] [WAITING ] pri[ 3] reb[0816F2C0] WC[0] WN[1]&lt;BR /&gt;[EXPORT ] [RUNNING ] pri[ 7] reb[0816DD40]&lt;BR /&gt;Traceback&lt;BR /&gt;SASTBTraceBackCtx has been called with a&lt;BR /&gt;string ("vacrash") instead of a CONTEXT pointer.&lt;BR /&gt;Address Frame (DBGHELP API Version 4.0 rev 5)&lt;BR /&gt;00007FF842354F69 00000000096C9760 KERNELBASE:RaiseException+0x69&lt;BR /&gt;0000000010055F3B 00000000096C9768 tkmk:tkBoot+0x541EB&lt;BR /&gt;0000000010055D09 00000000096C9CB0 tkmk:tkBoot+0x53FB9&lt;BR /&gt;000000001004A15A 00000000096C9D00 tkmk:tkBoot+0x4840A&lt;BR /&gt;00000000034912D9 00000000096C9D08 sashost:Main+0x8E19&lt;BR /&gt;00000000034821C4 00000000096C9DB0 sashost:rtmdoit+0x234&lt;BR /&gt;0000000003495F8F 00000000096C9F30 sashost:Main+0xDACF&lt;BR /&gt;0000000003499A10 00000000096CA0E0 sashost:Main+0x11550&lt;BR /&gt;000000000349FEAA 00000000096CA6B0 sashost:Main+0x179EA&lt;BR /&gt;000000000349F6B9 00000000096CA9D0 sashost:Main+0x171F9&lt;BR /&gt;00000000034A0140 00000000096CAA00 sashost:Main+0x17C80&lt;BR /&gt;000000000360351F 00000000096CAA70 sashost:tkStartSas+0xB67F&lt;BR /&gt;00007FF844BF20CF 00000000096CAA78 ntdll:_chkstk+0x11F&lt;BR /&gt;00007FF844BA1454 00000000096CB1B0 ntdll:RtlRaiseException+0x434&lt;BR /&gt;00007FF844BF0BFE 00000000096CB8D0 ntdll:KiUserExceptionDispatcher+0x2E&lt;BR /&gt;000000000795C006 00000000096CB8D8 sasjet:tkvercn1+0xAFC6&lt;BR /&gt;0000000007D5DFF8 00000000096CB918 sasiojet:tkvercn1+0xCFB8&lt;BR /&gt;0000000007DF3828 00000000096CB9B8 sasxdbi:tkvercn1+0x427E8&lt;BR /&gt;&amp;#12;117 The SAS System 17:12 Thursday, April 14, 2022&lt;/P&gt;
&lt;P&gt;0000000007DC77A1 00000000096CBA90 sasxdbi:tkvercn1+0x16761&lt;BR /&gt;0000000004919F84 00000000096CBA98 sasyh:tkvercn1+0x18F44&lt;BR /&gt;0000000004BB83C9 00000000096CBC18 sasxshel:tkvercn1+0x27389&lt;BR /&gt;0000000004B9344E 00000000096CC0C0 sasxshel:tkvercn1+0x240E&lt;BR /&gt;0000000004B919F5 00000000096CC150 sasxshel:tkvercn1+0x9B5&lt;BR /&gt;0000000004BBC332 00000000096CC2D0 sasxshel:tkvercn1+0x2B2F2&lt;BR /&gt;0000000004BE81C2 00000000096CC630 sasxshel:tkvercn1+0x57182&lt;BR /&gt;0000000004BEBDC4 00000000096CC720 sasxshel:tkvercn1+0x5AD84&lt;BR /&gt;0000000004BE5015 00000000096CC7C0 sasxshel:tkvercn1+0x53FD5&lt;BR /&gt;0000000007771877 00000000096CC7C8 sasimdts:tkvercn1+0x837&lt;BR /&gt;000000000774372A 00000000096CC8C8 sasimode:tkvercn1+0x26EA&lt;BR /&gt;0000000005584497 00000000096CE9C8 sasimctr:tkvercn1+0x3457&lt;BR /&gt;00000000055817FB 00000000096CF820 sasimctr:tkvercn1+0x7BB&lt;BR /&gt;00000000055612B0 00000000096CF828 sasexpor:tkvercn1+0x270&lt;BR /&gt;000000000349A066 00000000096CFCF0 sashost:Main+0x11BA6&lt;BR /&gt;00000000034A011D 00000000096CFD20 sashost:Main+0x17C5D&lt;BR /&gt;00007FF842F97034 00000000096CFD28 KERNEL32:BaseThreadInitThunk+0x14&lt;BR /&gt;00007FF844BA2651 00000000096CFDD0 ntdll:RtlUserThreadStart+0x21&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;ERROR: User asked for termination&lt;BR /&gt;NOTE: The SAS System stopped processing this step because of errors.&lt;BR /&gt;NOTE: PROCEDURE EXPORT used (Total process time):&lt;BR /&gt;real time 0.28 seconds&lt;BR /&gt;cpu time 0.28 seconds&lt;BR /&gt;&lt;BR /&gt;ERROR: Errors printed on pages 115,116,117.&lt;/P&gt;
&lt;P&gt;NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414&lt;BR /&gt;NOTE: The SAS System used:&lt;BR /&gt;real time 9:01.08&lt;BR /&gt;cpu time 8:25.23&lt;/P&gt;</description>
    <pubDate>Fri, 15 Apr 2022 02:23:24 GMT</pubDate>
    <dc:creator>hhchenfx</dc:creator>
    <dc:date>2022-04-15T02:23:24Z</dc:date>
    <item>
      <title>SAS WTABORT (EXPORT) The SAS System has detected an abort condition</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-WTABORT-EXPORT-The-SAS-System-has-detected-an-abort/m-p/807952#M318584</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;
&lt;P&gt;When I export 2 SAS datasets to Excel, the first one goes fine, then I received the following error when the 2nd file is being exported.&lt;/P&gt;
&lt;P&gt;The log below I got from my SAS running in batch.&lt;/P&gt;
&lt;P&gt;Recently, when I manually run the export, sometime SAS automatically shutdown. In these instance, I dont have a log file to see what is going on.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now I have the log. Can you please review and see what can I do to fix?&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;HHC&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;proc export data=m44_UP
outfile="C:\Users\OneDrive\........\file1_UP_&amp;amp;today..xlsx"
replace;
run;

proc export data=m44_DOWN
outfile="C:\Users\OneDrive \.........\file1_DOWN_&amp;amp;today..xlsx"
replace;
run;
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;NOTE: File "C:\Users\OneDrive\.......\file1_UP_20220414.xlsx" will be created if the export process succeeds.&lt;BR /&gt;NOTE: "M44_UP" range/sheet was successfully created.&lt;BR /&gt;NOTE: PROCEDURE EXPORT used (Total process time):&lt;BR /&gt;real time 0.33 seconds&lt;BR /&gt;cpu time 0.20 seconds&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;NOTE: File "C:\Users\OneDrive\......\file2_DOWN_20220414.xlsx" will be created if the export process succeeds.&lt;BR /&gt;&lt;BR /&gt;ERROR: An exception has been encountered.&lt;BR /&gt;Please contact technical support and provide them with the following traceback information:&lt;BR /&gt;&lt;BR /&gt;The SAS task name is [EXPORT]&lt;BR /&gt;ERROR: Read Access Violation EXPORT&lt;BR /&gt;Exception occurred at (0795C006)&lt;BR /&gt;Task Traceback&lt;BR /&gt;Address Frame (DBGHELP API Version 4.0 rev 5)&lt;BR /&gt;000000000795C006 00000000096CB910 sasjet:tkvercn1+0xAFC6&lt;BR /&gt;0000000007D5DFF8 00000000096CB918 sasiojet:tkvercn1+0xCFB8&lt;BR /&gt;0000000007DF3828 00000000096CB9B8 sasxdbi:tkvercn1+0x427E8&lt;BR /&gt;0000000007DC77A1 00000000096CBA90 sasxdbi:tkvercn1+0x16761&lt;BR /&gt;0000000004919F84 00000000096CBA98 sasyh:tkvercn1+0x18F44&lt;BR /&gt;0000000004BB83C9 00000000096CBC18 sasxshel:tkvercn1+0x27389&lt;BR /&gt;0000000004B9344E 00000000096CC0C0 sasxshel:tkvercn1+0x240E&lt;BR /&gt;0000000004B919F5 00000000096CC150 sasxshel:tkvercn1+0x9B5&lt;BR /&gt;0000000004BBC332 00000000096CC2D0 sasxshel:tkvercn1+0x2B2F2&lt;BR /&gt;0000000004BE81C2 00000000096CC630 sasxshel:tkvercn1+0x57182&lt;BR /&gt;0000000004BEBDC4 00000000096CC720 sasxshel:tkvercn1+0x5AD84&lt;BR /&gt;&amp;#12;116 The SAS System 17:12 Thursday, April 14, 2022&lt;/P&gt;
&lt;P&gt;0000000004BE5015 00000000096CC7C0 sasxshel:tkvercn1+0x53FD5&lt;BR /&gt;0000000007771877 00000000096CC7C8 sasimdts:tkvercn1+0x837&lt;BR /&gt;000000000774372A 00000000096CC8C8 sasimode:tkvercn1+0x26EA&lt;BR /&gt;0000000005584497 00000000096CE9C8 sasimctr:tkvercn1+0x3457&lt;BR /&gt;00000000055817FB 00000000096CF820 sasimctr:tkvercn1+0x7BB&lt;BR /&gt;00000000055612B0 00000000096CF828 sasexpor:tkvercn1+0x270&lt;BR /&gt;000000000349A066 00000000096CF9B8 sashost:Main+0x11BA6&lt;BR /&gt;00000000034A011D 00000000096CFD20 sashost:Main+0x17C5D&lt;BR /&gt;00007FF842F97034 00000000096CFD28 KERNEL32:BaseThreadInitThunk+0x14&lt;BR /&gt;00007FF844BA2651 00000000096CFD58 ntdll:RtlUserThreadStart+0x21&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;SAS WTABORT (EXPORT) The SAS System has detected an abort condition. An Exception occurred &lt;BR /&gt;during wthtrm(). &lt;BR /&gt;Please Contact Technical Support.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Tasks&lt;/P&gt;
&lt;P&gt;[MAIN ] [WAITING ] pri[ 5] reb[03366E40] WC[0] WN[1]&lt;BR /&gt;[IDLETASK] [READY ] pri[ 9] reb[03366E40]&lt;BR /&gt;[EVENTTSK] [WAITING ] pri[ 0] reb[03366E40] WC[0] WN[1]&lt;BR /&gt;[sasxkern] [WAITING ] pri[ 3] reb[03366E40] WC[0] WN[1]&lt;BR /&gt;[SGIOREAD] [WAITING ] pri[ 3] reb[03366E40] WC[0] WN[1]&lt;BR /&gt;[SGIOWRIT] [WAITING ] pri[ 3] reb[03366E40] WC[0] WN[1]&lt;BR /&gt;[Session ] [WAITING ] pri[ 3] reb[04C77FA0] WC[0] WN[1]&lt;BR /&gt;[TKSRV ] [WAITING ] pri[ 3] reb[04C78620] WC[0] WN[1]&lt;BR /&gt;[Program ] [WAITING ] pri[ 7] reb[04C79140] WC[0] WN[1]&lt;BR /&gt;[SASODR ] [WAITING ] pri[ 3] reb[0816F2C0] WC[0] WN[1]&lt;BR /&gt;[EXPORT ] [RUNNING ] pri[ 7] reb[0816DD40]&lt;BR /&gt;Traceback&lt;BR /&gt;SASTBTraceBackCtx has been called with a&lt;BR /&gt;string ("vacrash") instead of a CONTEXT pointer.&lt;BR /&gt;Address Frame (DBGHELP API Version 4.0 rev 5)&lt;BR /&gt;00007FF842354F69 00000000096C9760 KERNELBASE:RaiseException+0x69&lt;BR /&gt;0000000010055F3B 00000000096C9768 tkmk:tkBoot+0x541EB&lt;BR /&gt;0000000010055D09 00000000096C9CB0 tkmk:tkBoot+0x53FB9&lt;BR /&gt;000000001004A15A 00000000096C9D00 tkmk:tkBoot+0x4840A&lt;BR /&gt;00000000034912D9 00000000096C9D08 sashost:Main+0x8E19&lt;BR /&gt;00000000034821C4 00000000096C9DB0 sashost:rtmdoit+0x234&lt;BR /&gt;0000000003495F8F 00000000096C9F30 sashost:Main+0xDACF&lt;BR /&gt;0000000003499A10 00000000096CA0E0 sashost:Main+0x11550&lt;BR /&gt;000000000349FEAA 00000000096CA6B0 sashost:Main+0x179EA&lt;BR /&gt;000000000349F6B9 00000000096CA9D0 sashost:Main+0x171F9&lt;BR /&gt;00000000034A0140 00000000096CAA00 sashost:Main+0x17C80&lt;BR /&gt;000000000360351F 00000000096CAA70 sashost:tkStartSas+0xB67F&lt;BR /&gt;00007FF844BF20CF 00000000096CAA78 ntdll:_chkstk+0x11F&lt;BR /&gt;00007FF844BA1454 00000000096CB1B0 ntdll:RtlRaiseException+0x434&lt;BR /&gt;00007FF844BF0BFE 00000000096CB8D0 ntdll:KiUserExceptionDispatcher+0x2E&lt;BR /&gt;000000000795C006 00000000096CB8D8 sasjet:tkvercn1+0xAFC6&lt;BR /&gt;0000000007D5DFF8 00000000096CB918 sasiojet:tkvercn1+0xCFB8&lt;BR /&gt;0000000007DF3828 00000000096CB9B8 sasxdbi:tkvercn1+0x427E8&lt;BR /&gt;&amp;#12;117 The SAS System 17:12 Thursday, April 14, 2022&lt;/P&gt;
&lt;P&gt;0000000007DC77A1 00000000096CBA90 sasxdbi:tkvercn1+0x16761&lt;BR /&gt;0000000004919F84 00000000096CBA98 sasyh:tkvercn1+0x18F44&lt;BR /&gt;0000000004BB83C9 00000000096CBC18 sasxshel:tkvercn1+0x27389&lt;BR /&gt;0000000004B9344E 00000000096CC0C0 sasxshel:tkvercn1+0x240E&lt;BR /&gt;0000000004B919F5 00000000096CC150 sasxshel:tkvercn1+0x9B5&lt;BR /&gt;0000000004BBC332 00000000096CC2D0 sasxshel:tkvercn1+0x2B2F2&lt;BR /&gt;0000000004BE81C2 00000000096CC630 sasxshel:tkvercn1+0x57182&lt;BR /&gt;0000000004BEBDC4 00000000096CC720 sasxshel:tkvercn1+0x5AD84&lt;BR /&gt;0000000004BE5015 00000000096CC7C0 sasxshel:tkvercn1+0x53FD5&lt;BR /&gt;0000000007771877 00000000096CC7C8 sasimdts:tkvercn1+0x837&lt;BR /&gt;000000000774372A 00000000096CC8C8 sasimode:tkvercn1+0x26EA&lt;BR /&gt;0000000005584497 00000000096CE9C8 sasimctr:tkvercn1+0x3457&lt;BR /&gt;00000000055817FB 00000000096CF820 sasimctr:tkvercn1+0x7BB&lt;BR /&gt;00000000055612B0 00000000096CF828 sasexpor:tkvercn1+0x270&lt;BR /&gt;000000000349A066 00000000096CFCF0 sashost:Main+0x11BA6&lt;BR /&gt;00000000034A011D 00000000096CFD20 sashost:Main+0x17C5D&lt;BR /&gt;00007FF842F97034 00000000096CFD28 KERNEL32:BaseThreadInitThunk+0x14&lt;BR /&gt;00007FF844BA2651 00000000096CFDD0 ntdll:RtlUserThreadStart+0x21&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;ERROR: User asked for termination&lt;BR /&gt;NOTE: The SAS System stopped processing this step because of errors.&lt;BR /&gt;NOTE: PROCEDURE EXPORT used (Total process time):&lt;BR /&gt;real time 0.28 seconds&lt;BR /&gt;cpu time 0.28 seconds&lt;BR /&gt;&lt;BR /&gt;ERROR: Errors printed on pages 115,116,117.&lt;/P&gt;
&lt;P&gt;NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414&lt;BR /&gt;NOTE: The SAS System used:&lt;BR /&gt;real time 9:01.08&lt;BR /&gt;cpu time 8:25.23&lt;/P&gt;</description>
      <pubDate>Fri, 15 Apr 2022 02:23:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-WTABORT-EXPORT-The-SAS-System-has-detected-an-abort/m-p/807952#M318584</guid>
      <dc:creator>hhchenfx</dc:creator>
      <dc:date>2022-04-15T02:23:24Z</dc:date>
    </item>
    <item>
      <title>Re: SAS WTABORT (EXPORT) The SAS System has detected an abort condition</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-WTABORT-EXPORT-The-SAS-System-has-detected-an-abort/m-p/807954#M318585</link>
      <description>&lt;P&gt;Is the space after OneDrive in the code you provided Typo?&lt;BR /&gt;&lt;BR /&gt;If you do not export m44_UP but only m44_DOWN, does the same situation occur?&lt;BR /&gt;&lt;BR /&gt;Does this occur even if I delete the existing Excel files file1_UP_&amp;amp;today..xlsx and file1_DOWN_&amp;amp;today..xlsx before executing?&lt;BR /&gt;&lt;BR /&gt;I would suggest contacting SAS Technical Support, though, since the address for Traceback is output.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Apr 2022 02:43:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-WTABORT-EXPORT-The-SAS-System-has-detected-an-abort/m-p/807954#M318585</guid>
      <dc:creator>japelin</dc:creator>
      <dc:date>2022-04-15T02:43:32Z</dc:date>
    </item>
    <item>
      <title>Re: SAS WTABORT (EXPORT) The SAS System has detected an abort condition</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-WTABORT-EXPORT-The-SAS-System-has-detected-an-abort/m-p/808014#M318603</link>
      <description>&lt;P&gt;Thank you for your comment.&lt;/P&gt;
&lt;P&gt;I re-run the code and it works correctly.&lt;/P&gt;
&lt;P&gt;I will check with the tech support.&lt;/P&gt;
&lt;P&gt;HHC&lt;/P&gt;</description>
      <pubDate>Fri, 15 Apr 2022 14:48:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-WTABORT-EXPORT-The-SAS-System-has-detected-an-abort/m-p/808014#M318603</guid>
      <dc:creator>hhchenfx</dc:creator>
      <dc:date>2022-04-15T14:48:09Z</dc:date>
    </item>
  </channel>
</rss>

