I am writing again about this same issue. My server restarted over the weekend as it is scheduled to do and now I am left with a non-working system because FMSA10 web component failed to restart when the rest of the server restarted. I cannot use the admin console because of the java update problem. I cannot command line restart the web component of FMSA10 because this command does not exist. I am left with broken software. Filemaker Server Advanced 10 does not work. No one has even replied to this post suggesting that Filemaker is at least considering how to resolve this problem.
I guess this issue is two fold. Filemaker server admin console requires Java and the latest update of Java is not working with Filemaker Admin Console. Thus we have no method of restarting or configuring FMSA10 now.
Secondly, the web component of FMSA10 does not ever start correctly when FMSA10 is launched and always requires the defunct admin console to get it going.
A fix to either of these issues would be helpful.
A fix to the first issue is absolutely expected and there is no situation that justifies Filemaker's refusal to get this working again. This whole problem, as I understand it is due to a single file within the Java system being moved. This should be a simple thing to change in the admin console programing. reassign the correct path to the needed file, recompile, release for download. Done.
Java 6 Update 26 Mac OS X is now available. From the Apple menu, select "Software Update...". It will be listed as "Java for Mac OS X 10.6 Update 5". This corrects the problem of the Admin Console not working with FileMaker Server 10.