John May - Point In Space Posted June 18, 2009 Posted June 18, 2009 Just did the latest updates to OS X 10.5 today, and now FileMaker Server Admin, on both FMSA9 and FMSA10, won't start any longer. If I go to http://servername:16000 then click on the server admin link, it asks to start in Java Web Start, then just opens the .jnlp file in TextEdit. Anyone else seeing this? Any ideas on how to fix? - John
John May - Point In Space Posted June 18, 2009 Author Posted June 18, 2009 FYI, this has now been confirmed by others, and appears to have been caused by the "Java for Mac OS X 10.5 Update 4" update. I would highly advise against running said update until a solution has been found to this problem. - John
John May - Point In Space Posted June 18, 2009 Author Posted June 18, 2009 OK, found the solution. It seems that the web browser (system?) wasn't associating the .jnlp files with the proper application. When you go to http://server:16000 and click "Start Admin Console", the "open with" dialog will come up. Instead of selecting OK, select the path "System:Library:CoreServices:Java Web Start.app" and it should work. - John
Steven H. Blackwell Posted June 18, 2009 Posted June 18, 2009 I believe this issue is discussed in thefmkb.com/7121 on the FMI web site. Steven
John May - Point In Space Posted June 19, 2009 Author Posted June 19, 2009 Actually, that's a different issue. In my case, clearing the Java cache and trying to re-download the Admin Console did not help. As stated, I had to re-point the helper application for .jnlp files. - John
Steven H. Blackwell Posted June 19, 2009 Posted June 19, 2009 OK, good. Thanks for the clarification. Steven
Tom Kennedy Posted June 24, 2009 Posted June 24, 2009 I have the same problem. When I go to "http://server:16000", I still have the same problem. I had to use "localhost" instead of "server" in order to access the "Start Admin Console" page. I also tried "myserver.private" instead of "server" with the same result. I admit that I am a lightweight when it comes to FileMaker Server and Leopard server. Any ideas?
Troy Meyers Posted June 26, 2009 Posted June 26, 2009 I'm having the same problem too, after the Java update. I did clear the files using the Java Preferences app. Backtracking to http://192.168.1.104:16000/ (the FMS Server is 192.168.1.104) everything seems to proceed as usual, but when the web app is trying to launch I get the Application Error box, "Unable to launch the application". By clicking "Details" the More Information box comes up, and it says, "Error: Unexpected exception: java.lang.reflect.InvocationTargetException". There are two tabs in this box. The Exception tab is probably the important one, here's its contents: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.javaws.Launcher.executeApplication(Launcher.java:1359) at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1297) at com.sun.javaws.Launcher.doLaunchApp(Launcher.java:1096) at com.sun.javaws.Launcher.run(Launcher.java:116) at java.lang.Thread.run(Thread.java:613) Caused by: java.lang.ExceptionInInitializerError at com.filemaker.adminconsole.ui.clients.AdminConsoleJnlpLauncher.(AdminConsoleJnlpLauncher.java:195) at com.filemaker.adminconsole.ui.clients.AdminConsoleJnlpLauncher.main(AdminConsoleJnlpLauncher.java:102) ... 9 more Caused by: java.lang.RuntimeException: java.lang.NullPointerException at com.oaklandsw.util.LogUtils.checkInitialLogging(LogUtils.java:61) at com.oaklandsw.http.HttpURLConnection.(HttpURLConnection.java:159) ... 11 more Caused by: java.lang.NullPointerException at com.oaklandsw.http.HttpURLConnection.(HttpURLConnection.java:1114) at com.oaklandsw.http.eb.(eb.java:179) at com.oaklandsw.http.Handler.openConnection(Handler.java:19) at java.net.URL.openConnection(URL.java:943) at sun.net.www.protocol.jar.JarURLConnection.(JarURLConnection.java:64) at com.sun.jnlp.JNLPCachedJarURLConnection.(JNLPCachedJarURLConnection.java:66) at com.sun.javaws.net.protocol.jar.Handler.openConnection(Handler.java:21) at java.net.URL.openConnection(URL.java:943) at sun.misc.URLClassPath$JarLoader.getJarFile(URLClassPath.java:581) at sun.misc.URLClassPath$JarLoader.(URLClassPath.java:546) at sun.misc.URLClassPath$3.run(URLClassPath.java:324) at java.security.AccessController.doPrivileged(Native Method) at sun.misc.URLClassPath.getLoader(URLClassPath.java:313) at sun.misc.URLClassPath.getLoader(URLClassPath.java:290) at sun.misc.URLClassPath.getResource(URLClassPath.java:160) at java.net.URLClassLoader$1.run(URLClassLoader.java:192) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at com.sun.jnlp.JNLPClassLoader.findClass(JNLPClassLoader.java:257) at java.lang.ClassLoader.loadClass(ClassLoader.java:316) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at com.oaklandsw.util.LogUtils.checkInitialLogging(LogUtils.java:40) ... 12 more Any clues there? -Troy
Recommended Posts
This topic is 5633 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now