Thanks for posting!
Let's verify that the expected processes are actually running. Open the Task Manager by hitting CTRL + ALT + Delete and selecting Task Manager. Then, click on the processes tab. Confirm that the following processes are listed there:
Once we have this info, we'll be able to determine next steps.
The following processes are running:
Stopping FileMaker Server from the Windows Server Manager kills all 5, and starting it starts them again, so it does not appear to be a zombie process that is showing up.
What's the exact error you receive when you attempt from a different machine?
Let's disable the network adapters, reboot, and then attempt the admin console launch again. If it still fails, I think it might be best to try a full uninstall and reinstall. I've included instructions for this below.
1. Open the command prompt (Start -> Run -> cmd) and run the following commands:
"C:\Program Files (x86)\FileMaker\FileMaker Server\Database Server\fmsadmin.exe" close
"C:\Program Files (x86)\FileMaker\FileMaker Server\Database Server\fmsadmin.exe" stop server
2. Move the C:\Program Files (x86)\FileMaker\FileMaker Server\Data folder to your desktop. This contains all of your databases, back ups, system level scripts, etc.
3. Uninstall FileMaker Server through Add/Remove Programs.
4. Delete the C:\Program Files (x86)\FileMaker Server folder.
The exact error I get when trying to access the admin console remotely is as follows. I assume it is an IIS configuration thing, that the files required to launch the Java console are not shared outside of the local machine:
HTTP Status 403 -
FileMaker Server has encountered an error:
Access to the specified resource () has been forbidden.
If the http://filemaker.math.illinois.edu:16000/Server Launch Page is not available, visit the FileMaker Website for more assistance.
FileMaker Server 11
(note that I edited the error to remove a direct link to my server...)
Hi Jonathan Manton,
I know it has been more than a year, but just wanted to find out if you got it resolved in the end, because I'm seeing the exact same issue on one of our servers.
Your response regarding what you ended up doing would be appreciated.