<?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: ERROR: Write to WORK.ALL.DATA failed.  File is full and may be damaged. in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/ERROR-Write-to-WORK-ALL-DATA-failed-File-is-full-and-may-be/m-p/39774#M10273</link>
    <description>I'm providing an update and possible solution in case anyone else encounters this problem ...&lt;BR /&gt;
&lt;BR /&gt;
I think the issue is the limitation on file size for hard drives formatted using FAT32 which has a maximum file size of 4GB.  Most new external drives are formatted using FAT32 by default.  I think the fix is to reformat using NTFS.&lt;BR /&gt;
&lt;BR /&gt;
-MBI</description>
    <pubDate>Tue, 02 Jun 2009 15:53:07 GMT</pubDate>
    <dc:creator>MBI</dc:creator>
    <dc:date>2009-06-02T15:53:07Z</dc:date>
    <item>
      <title>ERROR: Write to WORK.ALL.DATA failed.  File is full and may be damaged.</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/ERROR-Write-to-WORK-ALL-DATA-failed-File-is-full-and-may-be/m-p/39773#M10272</link>
      <description>Hi everyone,&lt;BR /&gt;
&lt;BR /&gt;
I got this error last night while running a data step on a large set of data:&lt;BR /&gt;
ERROR: Write to WORK.ALL.DATA failed.  File is full and may be damaged.&lt;BR /&gt;
&lt;BR /&gt;
The log says that 19million observations were read but my data set has about twice that.&lt;BR /&gt;
&lt;BR /&gt;
I changed the default work folder in SASV9.CFG to an external 2000G drive a while back so there should be enough space.  Any idea what is going on?  Is there a setting elsewhere that limits the size of these temp work files?  Will I have any better luck if I use permanent user files?  I'm using EG 4.1.&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
&lt;BR /&gt;
MBI</description>
      <pubDate>Tue, 02 Jun 2009 11:57:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/ERROR-Write-to-WORK-ALL-DATA-failed-File-is-full-and-may-be/m-p/39773#M10272</guid>
      <dc:creator>MBI</dc:creator>
      <dc:date>2009-06-02T11:57:16Z</dc:date>
    </item>
    <item>
      <title>Re: ERROR: Write to WORK.ALL.DATA failed.  File is full and may be damaged.</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/ERROR-Write-to-WORK-ALL-DATA-failed-File-is-full-and-may-be/m-p/39774#M10273</link>
      <description>I'm providing an update and possible solution in case anyone else encounters this problem ...&lt;BR /&gt;
&lt;BR /&gt;
I think the issue is the limitation on file size for hard drives formatted using FAT32 which has a maximum file size of 4GB.  Most new external drives are formatted using FAT32 by default.  I think the fix is to reformat using NTFS.&lt;BR /&gt;
&lt;BR /&gt;
-MBI</description>
      <pubDate>Tue, 02 Jun 2009 15:53:07 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/ERROR-Write-to-WORK-ALL-DATA-failed-File-is-full-and-may-be/m-p/39774#M10273</guid>
      <dc:creator>MBI</dc:creator>
      <dc:date>2009-06-02T15:53:07Z</dc:date>
    </item>
    <item>
      <title>Re: ERROR: Write to WORK.ALL.DATA failed.  File is full and may be damaged.</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/ERROR-Write-to-WORK-ALL-DATA-failed-File-is-full-and-may-be/m-p/39775#M10274</link>
      <description>Try doing the same step in a permanent library. Also if possible do send the code which you are trying to execute.</description>
      <pubDate>Tue, 16 Jun 2009 19:50:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/ERROR-Write-to-WORK-ALL-DATA-failed-File-is-full-and-may-be/m-p/39775#M10274</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-06-16T19:50:58Z</dc:date>
    </item>
  </channel>
</rss>

