I suspect your server periodically "hangs" a scheduled backup. You can spot these in the Log as the log will show that a back up as started but doesn't log the completion nor the rescheduling of the backup.
This is a known issue that FileMaker Inc. has had a lot of trouble reproducting though many reports of it have been made.
The backups actually don't hang up. They keep on working as indicated by the log viewer. It seems that it's just the admin console that hangs. For example, this admin console hang occurred during a backup 5 days ago. The schedule says it's still running however the log viewer says it finished successfully and it continues to run.
More importantly I really need to know how I can close the open databases without the admin console working.
To close all your databases without crashing the server open the windows commandline(cmd.exe):
cd "C:\Program Files\Filemaker\Filemaker Server\Database Server"
You'll be prompted with (y/n) if you want to close all db's; answer Y
then you'll be promted for your admin-name and admin-password and after that your databases are closed, you see alle the files being closed and when that's done you can shutdown/restart your server
More info in the prompt: fmsadmin.exe HELP COMMANDS and fmsadmin.exe HELP OPTIONS
Fantastic. Thank you very much for that information. I'm guessing that Filemaker is continuing to look into this issue? It'd be nice to see the Admin Console not freeze.
Thank you for your posts (and thank you "menno" for the commands).
Yes, we are aware of this issue, but we continue to have difficulty reproducing the freezing of the Admin Console.
There were some changes to FileMaker Server 11v2 that supposedly has helped other users, but it doesn't appear to have help you. In the remote chance you specified 11v2 for FileMaker Pro rather than FileMaker Server, can you verify you are indeed running FileMaker Server 11v2?
Yes, we are using Filemaker Server 11v2. Oh and to add on to this case. I didn't need to close down the databases and server. I was able to use 'fmsadmin RESTART ADMINSERVER' from the 'Database Server' folder to get the console working again.
Thanks for the double-checking the version.
This problem started in FileMaker Server 10, and previously, you could not start Admin Console without rebooting the server, so FileMaker Server 11 introduced restarting the Admin Console without having to restart the server.
How many files are being hosted? How many clients are typically connected? What is the maximum number of clients that may be connected at peak times? What Schedules do you have active? What do the Schedules do (besides Backup)?
Since Admin Console is a Java application, what version of Java is being used?
FYI ... I have the exact same problem on a windows 2008 (x64). We are hosting 7 files with 11v2. We have to reboot to get the admin console usable and usually it dies within the day again ... so anytime we want to work with the admin console we have to plan a reboot ahead of time.
And Ryan ... Thank you! The restart command does work for me as well. So no more reboots needed, just a restart of fmsadmin :) A small step in the right direction.
I am happy to have FM look at our production server after hours (weekend) if they would like to try and pinpoint the issue.
one other possibility ... I use Windows RDC to connect to the server to use the ADMIN console. Might be an issue???
Ryan ... do you connect directly via monitor or remotely as I do?
I'm usually pulling the admin console up from within the same network as the server.
TSGal, to answer your questions. There are currently 3 files hosted on the server and maybe 15-20 client connections are possible at once I believe. Java version is most current normally. I can get the Java version if absolutely necessary. For schedules we have 3 backup schedules that run at different time of the day/week and a number of script schedules that perform maintenance functions.
Exactly the same problem here:
Windows Server 2008 x64 Standard
Schedule hangs (not really) and admin console does not update anymore.
Backup folder gives status Not a valid path? Strange because it is a valid path ....
using 50 files +/- 30 clients
Does backup folder give a status of "not valid" all the time or only when a schedule hangs?
If it shows "invalid" all the time, I'd take a closer look at the path to this folder, (Must be a local folder), to make sure it's really valid.
from my testing, it only happens until you do a 'restart' of FMSadmin, then everything works fine. but until then ... the invalid path is there no matter what the path is. In fact, even if you go to a pre-defined FM backup (that was in the schedules upon installation of the product), those show the path as invalid as well.
I'm drawing attention to that Invalid Path response as it's not, as far as I know, typical of the "hung schedule" or "Deaf server" issue. It may not even be a factor in this issue.
It does, however, suggest that something isn't quite right with either your system set up (accounts, permissions, etc.) or how the file path to the back up directory was specified.