Error: read_node address 0

[lansman]

I have 2 UNIX clients on filePro 4.05.08 versions who are both getting the following error as a popup:
                           Error: read_node address 0
                           Index = file_name/index.X

Is this a connectivity problem, a kernel problem and is there a patch for this?

[Joe Chasan]

filePro 4.5 had a few indexing bugs that could cause this.
While rebuilding the indexes in question may give you a temporary fix, you would be best served by upgrading to the latest & greatest so that you don't have to worry if it is your code or filePro itself that is causing these errors. 
If you still get errors then, post some relevent processing table code when the files/indexes get updated and someone can probably spot if there is a problem in it.