Thank you for your post.
It is difficult to determine what is causing the problem based on your post. If you look at the event.log or the system.log, do you see anything out of the ordinary? I doubt the event.log would show anything because FileMaker Server is still running, as clients can still connect to hosted files.
For clarification, it appears you are launching Admin Console from the server. Correct? Regardless, have you tried to connect to Admin Console from another computer?
Any other information you can provide may be helpful in narrowing down the possible causes.
the last time I tried to launch the Admin Console on the server machine it was no dice. I can access it from other machines however. I just haven't bothered to try again.
Thank You very much for Your answer!
I _believe_ that a couple of weeks ago, I tried to access the console from another machine. Since it happens only after running for some weeks, I'm unsure. Last weekend, I just tried from the server machine - and restarted that Mac. Now, everything runs fine.
The only things I'm sure about is that it happens after a longer time of use - and I don't have the latest patch of FMS (we got customers where we can't roll updates quickly - and when the release notes more or less just show WD stuff...)
We got several FMS13 running - and all of them have this issue in common. (and restarting helps)
I believe I'm experiencing the same issue, only I'm experiencing it every time I reboot the server. I'm also running 10.9.3 and it Filemaker server 13 runs fine after a fresh install, however after a reboot the admin console won't load and when I try to run "fmsadmin start adminserver" I'm told the object does not exist.
I have noticed that if I go into terminal, navigate to Library/Application Data/Filemaker/Filemaker Server and run "./launcher -load" followed by "./launcher -start" then I am able to successfully run "fmsadmin start adminserver" however even after manually starting and restarting all filemaker services I'm still unable to connect.
The only workaround I've found is to run the "FileMaker Server 13.0v2 Updater", after that runs I'm again able to get to the admin console.
markus schneider and RIck Whitelaw:
Thank you for the information.
Have you upgraded to FileMaker Server 13.0v2?
Since this appears to occur after a "few weeks", is there anything in the system logs that looks out of the ordinary?
What browser and browser version are you using on the server to access Admin Console?
When you try to connect, do you get an error message? What are the exact symptoms?
I'll upgrade one of the servers to the latest version of FMS13 - it will take some weeks until I can say if it helped...
I can't launch the admin console, local or remote, and webdirect is not working. This has happened before, and the reinstall of FMS would fix it, but not now. Java had updated to update 60, but I have rolled that back to update 55 and it didn't help. FMP and FM Go clients can still use the server.
FMS13v2 on Windows Server 2008.
Thank you for your post.
Were you trying to install Java and FileMaker Server at the same time? FileMaker Server 13.0v2 has been certified to run under Java 7 update 60. Once the Java update has been installed, then install FileMaker Server 13.0v2.
Let me know if you continue to run into difficulty.
I'm running the latest FMS version accessing with the latest version of Safari on MBP, MacPro and iPad. Server is Mac Mini with latest OS. I haven't tryed to access the Admin Console locally for around ten days. The only reason I did try was I had rebooted the server machine and was testing everything. At that point I couldn't access the Console locally. However, though I should be able to do this, the fact that I've been able to access it from three other machines obviates the need to access it on the server machine. I just never do it. I rarely turn on the screen which happens to be my tv.
Not much help, but wanted to point out that my lack of local access also was immediately after a reboot.