Have you ran Recover on the file? Just because the error is not detected on one system doesn't mean the file is not corrupt. The file could be corrupt and just isn't been detected on the other systems. Always make a backup copy before you do anything. If you have an older backup copy, then test this older backup and see if you get the error. If you don't have a backup or you have a backup and still get the error then run recover on the file. Test this file. I have seen a corrupt file that require a recover to be ran then all the records were deleted (Save Copy As - Clone no records )and then the records were imported to the new blank recoverd file from the error file. These are suggested steps to run to rule out the the file is not corrupt.
Can ANY database be opened in your configuration.
Make a drop dead simple NEW database and test.
Have you tried recovering this file? It sounds like it is damaged.
Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
- The recovered copy may behave differently even if recover reports "no problems found".
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
And here's a knowledgebase article that you may find useful: What to do when your file is corrupt (KB5421).
And how are you opening that database from the server?
If you are using directly opening the fie from a shared directory instead of using Open Remote, that is one of the classic ways that you can damage a Filemaker Database file--particularly if there is more than one user accessing the file in this manner.