Not a helpful reply, but i just about to do the same as you... Move the FMS10 software onto another server....
Looks like i could end up in the same issue ?! :(
Thank you for your post.
The Admin Console is a Java application that runs on the local machine. Therefore, what version of Java are you using on the machine where you are trying to launch Admin Console? I would start by using Java 6 Update 7, as this what was originally used to test FileMaker Pro 10.
Well I hope for your sake Stuart that you have no dramas. It is a pain in the butt.
Thanks for the response TSGal.
Well on the existing server it is running Java 6 Update 7. It was working when I originally deployed it, but something has caused it to stop working since. An update of something else I'm not sure.
On the Server I am attempting to transfer to it is currently running Java 6 Update 22.
If it is not working with Java 6 Update 7, then download a new jnlp file by launching a browser and entering:
Download and try to launch again.
Assuming FileMaker Server is working on the original machine (Admin Console notwithstanding), try launching Admin Console from the new server, referencing the old server. If this works, then you'll know Java 6 Update 22 is okay.
Ok I attempted to enter http://localhost:16000 into my browser on the original machine, and it is just sitting there idle with a loading bar, and in the bottom lefthand saying "Waiting for http://localhost:16000"
Same thing happens when I try launch the Admin Console from the new server referencing the old.
I don't mean to be pushy, or abnoxious, but any ideas or suggestions?
It's really got me stumped.
Thanks in Advance.
i have the same problem (http://forums.filemaker.com/posts/fd0be0a47f). The problem exist since FileMaker Server 9. I can't understand that FileMaker Inc. know this bug but the problem is still exist! Why FileMaker Inc. doesn't fix it?
That's a shame. Still not fixed on my end.
I'm currently speaking with Technical Support (Australia) on the matter. The person that is helping me finds it odd, but at the moment wants me to uninstall and reinstall it. (Despite it happening on old and new machines)
In my experience Java is rubbish. So finicky, and older programs don't work with newer versions and visa versa, you get one thing to work and something else fails. It's a joke.
I hope you get your problem sorted also.
i have a workaround for you. You can create a batch file with the following content. If the FMS Admin Console stands still, you can run the batch file and you dont need to reboot the server.
cd "C:\Program Files (x86)\FileMaker\FileMaker Server\Database Server"
fmsadmin CLOSE -y -u <YourUsername> -p <YourPassword> -force
fmsadmin RESTART ADMINSERVER -y -u <YourUsername> -p <YourPassword>
fmsadmin RESTART SERVER -y -u <YourUsername> -p <YourPassword>
But this is not the solution. FileMaker have to fix this problem.
With FileMaker Server 9, Admin Console won't run with a a version of Java beyond version 6 update 7. This was fixed in FileMaker Server 10. With FileMaker Server 10, it was fully tested with version 6 update 7, and later versions/updates do seem to work, but when customers encounter problems with Admin Console, Technical Support tries to return to the basics and have customers reinstall version 6 update 7. With FileMaker Server 11, there were a few problems reported attributed to Java version 6 update 18 and certain plug-ins, but those plug-ins have been updated.
If http://localhost:16000 does not work, try using the exact IP address. That is,
... where xxx.xxx.xxx.xxx is the IP address.
If this fails, then make sure the server is set up properly, and make sure FileMaker Server is installed properly.
I forgot... Make sure port 16000 is open! For a list of ports that need to be open, please seen Knowledge Base Article #6427:
Thanks for the suggestion L.S. I've been on the road and not able to test this out, I wll give it a go next week once I'm back in the office.
TSGal, whilst I appreciate your suggestions this was covered with the Technical Support Rep. Tried the localhost, the loopback, the exact IP.
The server was setup correctly as it was running fine in the past, and the issue also occured on a fresh brand new server.
I will be uninstalling and reinstally when I can, it's hard to get a good window to do it as the database is used by employees 24/7.