Node read error

Nancy Palmquist nlp at vss3.com
Tue Nov 27 11:40:02 PST 2007


Don Coleman wrote:
>> -----Original Message-----
>> From: Nancy Palmquist [mailto:nlp at vss3.com]
>> Sent: Tuesday, November 27, 2007 1:40 PM
>> To: Don Coleman
>> Cc: 'Filepro-List at Lists. Celestial. Com'
>> Subject: Re: Node read error
>>
>> Don Coleman wrote:
>>> Client reported a number of node read errors on an index file while
>> running
>>> an archive process this AM.  I did not see the error myself so I can't
>> be
>>> sure of the exact wording.  We have already rebuilt the index.  They
>>> reported the error message appeared to be a fP error because it was
>> shown in
>>> a red box.  Does this error mean it could not save the index data to
>> disk?
>>> If so, I'm curious as to why we got the error on the index file but not
>> the
>>> key file.
>>>
>>> Don Coleman
>>> Donald G. Coleman, Consultant
>>> 402 Andrew Circle
>>> Indiana, PA 15701
>>> dcoleman at dgcreact.com
>>> (724) 349-6302
>>>
>>> _______________________________________________
>>> Filepro-list mailing list
>>> Filepro-list at lists.celestial.com
>>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>>
>>>
>> Don,
>>
>> This is the corrupt index error that happened in certain versions of
>> filePro.
>> What version are they using?
>>
>> Also, make sure all filePro programs are the same version.  dxmaint,
>> dreport, rreport, dclerk,
>> rclerk, dprodir.
>>
>> Which ever you use, verify that they all have the same version number.
>>
>> Using mixed up versions, can cause issues like this, since patches might
>> not be applied to all
>> correctly.
>>
>> Nancy
>>
>> --
>> Nancy Palmquist 		MOS & filePro Training Available
>> Virtual Software Systems	Web Based Training and Consulting
>> PHONE: (412) 835-9417		   Web site:  http://www.vss3.com
> 
> Nancy:
> 
> RCLERK v5.0.13RN9
> RREPORT v5.0.13RN9
> DPRODIR v5.0.13DN9
> DXMAINT v5.0.13DN9
> 
> So the gist of it is the error message indicated a bad index, not
> necessarily a bad hard drive?

Yes exactly.  This should have been fixed in 5.0.14 or newer.  You can download the last
release of 5.0 from the downloads.  It requires the license manager, so you have to create
and download a license also.

I have seen few of those errors since 5.0.14 versions.

Nancy


> 
> 
> 
> Don Coleman
> Donald G. Coleman, Consultant
> 402 Andrew Circle
> Indiana, PA 15701
> dcoleman at dgcreact.com
> (724) 349-6302
> 
> 


-- 
Nancy Palmquist 		MOS & filePro Training Available
Virtual Software Systems	Web Based Training and Consulting	
PHONE: (412) 835-9417		   Web site:  http://www.vss3.com


More information about the Filepro-list mailing list