Thank you for your post.
I don't have enough information to determine what might be the problem.
First, tell me more about your Windows 2003 system. That is, specifications, memory, etc.
Admin Console has nothing to do with IIS, so something else is occurring.
When installing FileMaker Server, did you run into anything out of the ordinary?
Uninstall FileMaker Server 10, run msconfig, and disable all non-Microsoft Services. Then, install FileMaker Server 10 again.
Please keep me updated with any progress.
Dual Core Xeon 2.6GHz
2GB RAM (I've asked them to increase)
9GB free HD space on C:
I misstated the IIS error - meant IE error. That is, IE responds that the resource could not be found.
There were no errors or other indications that FileMaker Server did not install correctly. It was only when reaching the last step to configure FMS deployment that we're stuck at the screen waiting for the Admin Console to launch. It never does.
What is responsible for responding on port 16000? Is it Catalina or another process and how can we determine if it is installed correctly and running?
Why would the CLI return an error when attempting to run the fmsadmin command? The fmsadmin process works (e.g. 'fmadmin HELP Commands' works), but anything requiring it to communicate with the database server results in an error such as the one I listed.
I had disabled other services before but will uninstall, disable, and reinstall as you suggest.
IE means Internet Explorer?
Can you launch Internet Explorer directly or does that also trigger an error?
What version of Java is installed?
IE = Internet Explorer, in my first post I had mistakenly written IIS
Java 184.108.40.206 although while FMS 9 was picky about JVM versions, supposedly FMS 10 is not.
After installing FMS 10, it is supposed to launch the deployment configuration wizard. It does not. The page it launches is simply a local file with an iFrame pointing to http://localhost:16000
If I type that into the browser location bar I get an error from IE stating that the resource could not be found. That (as well as probing the port) tells me that there's nothing listening on port 16000.
The error messages you received are an indication that Catalina never started. You'll receive these errors when you stop the FMS service and FMS attempts to stop Catalina (which had never actually started).
What does your memory environment look like and what else is running on the server?
Our server has 4GB of RAM and FileMaker Server is the only application/database that runs on it, so it is a dedicated server. We also use Backup Exec for nightly backups.
We had FileMaker Server 9 admin console running fine on this same server with the exact same configuration. When we uninstalled FMS 9 and installed FMS 10, thats when the admin console stopped working.