<?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 Re: Proc Export Problem in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Export-Problem/m-p/57853#M16135</link>
    <description>Your Excel file is corrupt.  See&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://support.sas.com/kb/15/543.html" target="_blank"&gt;http://support.sas.com/kb/15/543.html&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
searched on support.sas.com for&lt;BR /&gt;
excel "Read Access Violation"</description>
    <pubDate>Tue, 16 Feb 2010 16:56:33 GMT</pubDate>
    <dc:creator>Doc_Duke</dc:creator>
    <dc:date>2010-02-16T16:56:33Z</dc:date>
    <item>
      <title>Proc Export Problem</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Export-Problem/m-p/57852#M16134</link>
      <description>A regularly used piece of code to export a table from SAS to an excel sheet (in a spreadsheet that already exists) has suddenly stopped working.  The code below was used to create a new tab 'sas_update' in the spreadsheet 'policy rule tracking.xls' and previously worked fine.&lt;BR /&gt;
&lt;BR /&gt;
Now, when the code below runs the first time the various error messages are displayed. &lt;BR /&gt;
&lt;BR /&gt;
If it is run a second time (with nothing changed) it appears to work (again message displayed below).&lt;BR /&gt;
&lt;BR /&gt;
However after either the 1st or 2nd attempts the excel file can't be opened - a message is displayed 'cannot access policy rule tracking.xls'.&lt;BR /&gt;
&lt;BR /&gt;
I have then found that if I close the SAS session I can open the excel file but the new sheet does not appear!&lt;BR /&gt;
&lt;BR /&gt;
Any ideas / suggestions would be greatly appreciated.  This has me completely stumped.&lt;BR /&gt;
&lt;BR /&gt;
&lt;U&gt;&lt;B&gt;Initial Run&lt;/B&gt;&lt;/U&gt;&lt;BR /&gt;
&lt;BR /&gt;
  1    libname jgsas 'c:\temp\jgsastemp'; &lt;BR /&gt;
NOTE: Libref JGSAS was successfully assigned as follows: &lt;BR /&gt;
      Engine:        V9 &lt;BR /&gt;
      Physical Name: c:\temp\jgsastemp &lt;BR /&gt;
&lt;BR /&gt;
2    proc export data=jgsas.policy_rule_tracking_4 &lt;BR /&gt;
3    outfile='c:\temp\jgsastemp\acquisition tracking\policy rule tracking.xls' &lt;BR /&gt;
4    dbms=excel2000 replace; &lt;BR /&gt;
5    sheet=sas_update; &lt;BR /&gt;
6    run; &lt;BR /&gt;
&lt;BR /&gt;
ERROR:  Read Access Violation In Task [ SQL ) &lt;BR /&gt;
Exception occurred at (5570C819) &lt;BR /&gt;
Task Traceback &lt;BR /&gt;
Address   Frame     (DBGHELP API Version 4.0 rev 5) &lt;BR /&gt;
5570C819  06F4E1F4  sasjet:mcn_main+0xB819 &lt;BR /&gt;
55750030  06F4E2EC  sasiojet:mcn_main+0xF030 &lt;BR /&gt;
6597F5AC  06F4E334  sasxdbi:mcn_main+0xE5AC &lt;BR /&gt;
671A331A  06F4E484  sasyoio:mcn_main+0x231A &lt;BR /&gt;
06F626CC  06F4E4F0  sassqx:mcn_main+0x116CC &lt;BR /&gt;
06F620FD  06F4E5EC  sassqx:mcn_main+0x110FD &lt;BR /&gt;
06F618BB  06F4E628  sassqx:mcn_main+0x108BB &lt;BR /&gt;
06F771C1  06F4E654  sassqx:mcn_main+0x261C1 &lt;BR /&gt;
06F739E2  06F4FF54  sassqx:mcn_main+0x229E2 &lt;BR /&gt;
600D118A  06F4FF88  sassql:mcn_main+0x18A &lt;BR /&gt;
01262B02  06F4FFA0  sashost:Main+0xBE72 &lt;BR /&gt;
01266C20  06F4FFB4  sashost:Main+0xFF90 &lt;BR /&gt;
7C80B683  06F4FFEC  kernel32:GetModuleFileNameA+0x1B4 &lt;BR /&gt;
&lt;BR /&gt;
WARNING: The data set _IMEX_.sas_update may be incomplete.  When this step was stopped there &lt;BR /&gt;
         were 0 observations and 26 variables. &lt;BR /&gt;
ERROR:  Read Access Violation In Task [ SQL ) &lt;BR /&gt;
Exception occurred at (5570C819) &lt;BR /&gt;
ERROR: Unable to clear or re-assign the library _IMEX_ because it is still in use. &lt;BR /&gt;
ERROR: Error in the LIBNAME statement. &lt;BR /&gt;
ERROR: Export unsuccessful.  See SAS Log for details. &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.59 seconds &lt;BR /&gt;
      cpu time            0.15 seconds &lt;BR /&gt;
&lt;BR /&gt;
&lt;U&gt;&lt;B&gt;2nd run from here&lt;/B&gt;&lt;/U&gt;&lt;BR /&gt;
&lt;BR /&gt;
7    proc export data=jgsas.policy_rule_tracking_4 &lt;BR /&gt;
8    outfile='c:\temp\jgsastemp\acquisition tracking\policy rule tracking.xls' &lt;BR /&gt;
9    dbms=excel2000 replace; &lt;BR /&gt;
10   sheet=sas_update; &lt;BR /&gt;
11   run; &lt;BR /&gt;
&lt;BR /&gt;
NOTE: "sas_update" was successfully created. &lt;BR /&gt;
NOTE: PROCEDURE EXPORT used (Total process time): &lt;BR /&gt;
      real time           0.50 seconds &lt;BR /&gt;
      cpu time            0.04 seconds

Message was edited by: J Guthrie</description>
      <pubDate>Tue, 16 Feb 2010 15:13:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Proc-Export-Problem/m-p/57852#M16134</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2010-02-16T15:13:34Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Export Problem</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Export-Problem/m-p/57853#M16135</link>
      <description>Your Excel file is corrupt.  See&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://support.sas.com/kb/15/543.html" target="_blank"&gt;http://support.sas.com/kb/15/543.html&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
searched on support.sas.com for&lt;BR /&gt;
excel "Read Access Violation"</description>
      <pubDate>Tue, 16 Feb 2010 16:56:33 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Proc-Export-Problem/m-p/57853#M16135</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2010-02-16T16:56:33Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Export Problem</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Export-Problem/m-p/57854#M16136</link>
      <description>Hi:&lt;BR /&gt;
  This Tech Support note seems relevant:&lt;BR /&gt;
&lt;A href="http://support.sas.com/kb/15/543.html" target="_blank"&gt;http://support.sas.com/kb/15/543.html&lt;/A&gt; &lt;BR /&gt;
 &lt;BR /&gt;
You may want to work with Tech Support on this issue. To send a question to Tech Support, go to &lt;A href="http://support.sas.com/" target="_blank"&gt;http://support.sas.com/&lt;/A&gt; and in the left-hand navigation pane, click on the link entitled "Submit a Problem". Alternately, you can go directly to the Tech Support Problem Form here:&lt;BR /&gt;
&lt;A href="http://support.sas.com/ctx/supportform/createForm" target="_blank"&gt;http://support.sas.com/ctx/supportform/createForm&lt;/A&gt; &lt;BR /&gt;
 &lt;BR /&gt;
cynthia</description>
      <pubDate>Tue, 16 Feb 2010 17:09:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Proc-Export-Problem/m-p/57854#M16136</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2010-02-16T17:09:45Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Export Problem</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Export-Problem/m-p/57855#M16137</link>
      <description>Thanks for the replies, much appreciated.  I've re-created the target excel file and tried again and it works.</description>
      <pubDate>Wed, 17 Feb 2010 08:54:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Proc-Export-Problem/m-p/57855#M16137</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2010-02-17T08:54:23Z</dc:date>
    </item>
  </channel>
</rss>

