I don't have an answer but would like to nail down a few details with you so that anyone else, such as a FileMaker Tech, will have as complete a picture as possible to work with.
I gather FileMaker Pro 8 is hosting the database for others to access. Do all users use Open Remote to access this database or do you have the file in a shared directory where users can open the file directly? OR are do the users use a web browser to connect to the database?
What do you mean by "the 2nd server"?
What error message, if any is displayed when a user is "kicked off"?
Exactly what do you mean by "resynchronize the computer to the server to re establish a connection for that user"?
Have you checked your file for possible corruption?
We have 2 servers but only one runs the file maker data base the other handles all employee drives and programs.
I took a screen shot of the error message.
If we don't log the user off their computer when we reboot the connection to the file maker pro server they still might connect to the data base and that is how we resynchronize the user to the data base
We have not checked for possible corruption. How might we go about diagnosing this?
The error message I see should display if you try to open the hosted file and FileMaker is unable to to open it. This is a possible error message if the user navigates directly to the file on a shared directory and tries to open it. If this is what they are doing, you should stop this immediately as this method for opening the file can corrupt it. Users should launch FileMaker and then use Open Remote to find and open the hosted file. The file should be hosted on your server by opening it with either FileMaker Pro or FileMaker Server.
To check for File Corruption, you can take a copy of your file (not the copy currently hosted) such as last night's back up copy and run a recover on it to see what it reports. A third party product, FMDiff, can also be used for this purpose.
Things to keep in mind about Recover:
- 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.