We have installed FileMaker Pro 5.5 Unlimited on a Windows 2000 web server. The installation was done remotely via Terminal Services Client, and now whenever we log off the (TSC) session, FileMaker is shut down. While it is open we can serve pages (db) without problem, but we can't seem to figure out how to keep it open. Should FileMaker be installed from the console of the server? Would this eliminate the issue? I know this is sort of a dumb question, but we can't seem to find an answer and nobody else seems to have run into the problem. At least they haven't posted it.

FileMaker Unlimited must be open to serve your databases - logging in from a terminal services session is no different than logging in at the console of the machine - what happens if you log off and there are programs running? They shut down. If you want the pages served with Unlimited then a user needs to stay logged in - that solves the problem of serving the pages but may complicate remote administration - when you log in remotely (via TS) you will be in a new session independent of the session running Unlimited so you will not be able to do any troubleshooting maintenence - I'm not positive, but if the session running Unlimited is open and you log in remotely and try and open Unlimited, you may get an error message about a FileMaker license conflict - the solution would be to use PCanywhere, VNC, or some other remote control software that, unlike terminal server, does not open a new session when you connect.

Will