Skip to main content

[archive] File index broken

  • August 23, 2005
  • 2 replies
  • 0 views

[Migrated content. Thread originally posted on 14 July 2005]

Good days,

We have 100 customers, but only 1 of them have the next problem:

Every time that two users access to the same program where the same registry is read with "read 'file' invalid key continue" a "File index broken" error 98,90 is found.
We didnt detected power cuts or conexion downtimes with the server, and in the server with the files they have windows 2000 and in the terminals where they access to the server they have windows XP. Their runtime version is 6.2 and file vision is 5.

?Why this could happen?

Thank you very much

2 replies

[Migrated content. Thread originally posted on 14 July 2005]

Good days,

We have 100 customers, but only 1 of them have the next problem:

Every time that two users access to the same program where the same registry is read with "read 'file' invalid key continue" a "File index broken" error 98,90 is found.
We didnt detected power cuts or conexion downtimes with the server, and in the server with the files they have windows 2000 and in the terminals where they access to the server they have windows XP. Their runtime version is 6.2 and file vision is 5.

?Why this could happen?

Thank you very much
We have had this problem in cases where the user has different versions of Windows on the client PCs and especially if the server has an older version of Windows NT. One solution is either to ensure that they have the same version of Windows on the client PCs and a newer version on the server. A more reliable solution is to use Acuserve on the server.

[Migrated content. Thread originally posted on 14 July 2005]

Good days,

We have 100 customers, but only 1 of them have the next problem:

Every time that two users access to the same program where the same registry is read with "read 'file' invalid key continue" a "File index broken" error 98,90 is found.
We didnt detected power cuts or conexion downtimes with the server, and in the server with the files they have windows 2000 and in the terminals where they access to the server they have windows XP. Their runtime version is 6.2 and file vision is 5.

?Why this could happen?

Thank you very much
So we have the Problem too. Since we made the Update of the Runtime to 6.2 any customers told us about the File error 98,90 in Vision 5. But we have no solutions for this problem.