Just a guess from my inexperience. You probably have port issues.
From my limited experience with Windows (of any version) 2012 you have to turn on the FMS specific ports and/or turn off the firewall. When we deploy a new Win2012 server our systems admin has to first specifically turn on all the FMS ports. For example the Admin console uses port 16001. But, a new install of Win2012 has it turned off. Windows seems to now be overly protective of port usage and requires the system admin to set these things manually.
There are a lot of ports used by FMS for either internal or external communications. I advise you to read the Knowledge base article on the subject and know exactly which ports you need for your 1 or 2 machine deployment.
not sure if that helps, but FMS is very picky on Java version. One thing you may do is check if the installed version is Ok according to FMS requirements.
Thank you, planteg and ch0ch0halic for you advice, although it did not help me. I tried a complete reinstall again with the same results. When I try to start the web console it gives me the same message.
Actually, I may be able to live without the console as the I've found out that by using the command line most actions can be performed. I even managed to make a backup directly (fmsadmin backup myfile.fmp12) Now I only need to learn the parameters for regular backups. I guess that ought to be in a separate thread.
many thanks for your help.
Hi all - ISSUE SOLVED !
I have been in cooperation with filemaker support over this strange issue. I asked my tech personnel to help me find a system file that FM support asked for and they encountered this:
When running msinfo32 we noticed that the WMI (windows management instruction, see https://en.wikipedia.org/wiki/Windows_Management_Instrumentation) repository was corrupt.
We stopped the winmgmt (windows management) service and renamed the repository folder (to make it inactive)
The restarted the winmgmt. New repository folder was then automatically created.
After the repository folder is recreated you will be asked to enter the admin console username and password.
Msinfo32 worked and so did Filemaker admin console.
This applies to windows (server 2012RE). I tested with the same path (that did not work, see original post) and voila! The admin console is up and running! All panels of the console are visible and my next job is to rebuild all the schedules.
I expect FM support to confirm this shortly. I hope this will be of help to all those who have reported this and similar issues. Please test in you local enviroment, perhaps other issues will popup.
I am having very similar issues with Windows Server 2012 R2. All was fine until this weekend, when a Windows automatic update, and then a restart caused the Filemaker Admin Console to not be reachable. I assumed it was a port issue, as I had done nothing to change any configurations; all I saw was localhost:16001 not being reachable.
The IT guys here have assured me all ports are open as needed. I have rolled back to before the Windows updates, uninstalled everything, restarted, made sure there was no automatic update after the restart, reinstalled Filemaker Server (188.8.131.523) and still no joy. I have tried the above trick with the Windows Management Service to recreate the repository folder (which it does) but still the same.
I could manage were it not for setting scheduled backups, but to be honest, I don't really want to manage - I want it to work!
Anybody else been through this and able to offer any advice?