Node read error
Nancy Palmquist
nlp at vss3.com
Tue Nov 27 10:39:34 PST 2007
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
More information about the Filepro-list
mailing list