I wouldn't have done it differenlty and see no reason why it should not work.
Maybe you were just unlucky and hit a bad spot on your hard disk?
My next step would indeed be a uninstall / re-install cycle of FMS.
Since we can save the server schedules this is just a 15 min process.
(Have not yet tried it myself on MountainLion)
Well, I have uninstalled and re-installed and it is currently working. Let's see if it lasts more than 4 days.
My concern really is that there are issues with mountain lion, as we have customers starting to roll that puppy out as they buy new machines. If there are issues, I want to be on top of them, especially given the history of command line deafness and the unreliable java based admin console.
Thanks Rob, please post the outcome, good or bad.
I didn't do a vanilla install - did Lion, then 12v2 SA, then Mountain Lion upgrade, then uninstalled, and reinstalled FMSA and can't get the admin console to start no matter what I do, including above steps
I'm afraid I'm in the same boat.
Server uninstall, Mountain Lion upgrade, Server reinstall. Now I can't get the admin server to start up at all either with the command line or java.
Thankfull that it's just my bench tester for now.
replying to my own posts here...
I uninstalled and re-installed FileMaker Server and managed to get everything going again.
However, it ran for 2 days before the computer restarted by itself. The crash log contains the line about the thread that crashed:
"BSD process name corresponding to current thread: java"
which made me suspicious of the admin console. Restoring backups, restarting, etc. The same thing happened two days later.
I have now removed the one modification I installed (temperature monitor) and have restarted and will monitor again for a few days.
I'll keep you in the loop when I have more information.