I have Filemaker Server 7 hosting filemaker files on Windows Server 2003. My data base consists of one master and 12 related tables. On occasion, one of the related tables is not accessible and I get the following message on the client. "Filemaker has been forcefully disconnected by the host. All attached windows will be closed. [from administrator ""]. After I get this message, the only way I can access this file again is to "Reboot" the server. If I try to open the file with filemaker pro 7, it rebuilds itself as if it was open doing a system power failure. All of the other files in my database remain accesible. Has anyone else experienced this problem?

don't reboot the machine until you've stopped the filemaker server service!!

If you haven't enabled the "disconnect on idle" in filemaker server then typically the disconnect problem indicates a network problem. But in that case it should happen to all open files.

Other possibility is that something is corrupted in that one file. And you're not helping it much by rebooting the machine without making sure all files are closed properly.

What does the event log say around the time the disconnects happen and after you reboot?

I did not see anything unusual in the event log. Just a lot of login/logouts. The file I am having a problem with contains data that is imported from our main system nightly (.txt file). Therefore, the file contents are deleted and replaced daily. It is used in a portal as "read only". Before I reboot, I close all the files with filemaker administrator. They all close except for the problem file. It simple lists as "closing" but it is not open. The only way to get it open is to re-boot. I will disable the "disconnet when idle" to see if that helps. However, I have four other related tables that work fine with disconnect enabled. I will also delete the (120,000) records in this file to verify that corrupt data is not the problem. Thanks for your help!