<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><br><br>--- On <b>Wed, 10/28/09, Walter Vaughan <i><wvaughan@steelerubber.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Walter Vaughan <wvaughan@steelerubber.com><br>Subject: Re: lockfile<br>To: "filePro" <filepro-list@lists.celestial.com><br>Date: Wednesday, October 28, 2009, 12:05 PM<br><br><div id="yiv1903022249">
<title></title>
ivan wrote:<br>
<blockquote type="cite">
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; font-size: inherit; line-height: inherit; font-size-adjust: inherit; font-stretch: inherit;" valign="top">Good morning all...<br>
<br>
After running a report for several years and not having made any
changes this morning I and every one else trying to run this report has
encountered an error.<br>
<br>
The first runnings produced several different errors<br>
disk error<br>
files with names as just symbols<br>
</td>
</tr>
</tbody>
</table>
<br>
</blockquote>
1) rebooting didn't fix anything.<br>
2) I would not trust anything on that server<br>
<br>
You had a hardware failure. They don't just fix themselves unless you
were the victim of some sort of electromagnetic or Gamma particle
interference.<br>
Or heat related.<br>
<br>
How good are your backups? This is only going to get worse, and perhaps
any minute you might have an unusable server.<br>
</div><a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank"></a><br></blockquote>OK, let me explains what happens. This server is less than 8 months old, so I'm really hoping there was no failure...<br>
<br>
This report runs in the file fescall, It goes through the selection
process fine, then runs through the first record just fine, it get to
the second record and, as in the first record, does a lookup to the
file fescall to see if there is any other records for that customer,
when it does this record is when it just bombs out. It does this on
any report that looks back into the file after processing the first
record in the report.<br>
<br>
Everything else we do with the file works fine... Can access all
records, make new ones, change old ones, it's just the reports that we
are having issues with.<br>
<br>
So does this still sound like a hardware failure???<br>
<br>
-Ivan</td></tr></table><br>