2 Replies Latest reply on Jan 1, 2014 11:22 AM by tjsoftworks

    FileMaker Server 12 - Another Server admin hiccup


      Yesterday, I installed a new FileMaker Server 12 instance on a new MtLion Server. All updates applied in OS ( 10.8.5) , FileMaker and Java land 7.0.45.


      I can open FileMaker Server Admin local to the machine.

      I have Enabled access restrictions for IP addresses that I want to allow Admin access in the General Settings>Admin Console area

      SSL communication is turned on.


      I can get to the server info page



      I can launch the applet but when I do I get "Admin Console could not start: Admin Server Manager unavailable."



      Wireshark shows communcation going out but nothing coming back...


      I cleared the Java caches and reset on both sides.





        • 1. Re: FileMaker Server 12 - Another Server admin hiccup

          Correction to above.... Cross out Wireshark comment. There is communication going on but the result is the error message.


          I do get the security warning about the certificate being ok - "Publisher: FileMaker Incorporated" but that the app itself is unsigned.

          I click "Run". It runs and

          The Java console shows:


          CacheEntry[]: updateAvailable=false,lastModified=Wed Dec 31 16:00:00 PST 1969,length=-1

          Exception in thread "AWT-EventQueue-1" java.lang.NullPointerException

              at com.sun.deploy.ui.DialogTemplate.imageAvailable(Unknown Source)

              at com.sun.deploy.ui.DialogTemplate.finalImageAvailable(Unknown Source)

              at com.sun.deploy.ui.ImageLoader$2.run(Unknown Source)

              at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)

              at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)

              at java.awt.EventQueue.access$200(EventQueue.java:103)

              at java.awt.EventQueue$3.run(EventQueue.java:694)

              at java.awt.EventQueue$3.run(EventQueue.java:692)

              at java.security.AccessController.doPrivileged(Native Method)

              at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)

              at java.awt.EventQueue.dispatchEvent(EventQueue.java:703)

              at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)

              at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)

              at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)

              at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)

              at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)

              at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)

          Using standard JNLP Launcher

          Show stack traces: null

          Arg = keep-alive-interval=60

          Arg = log-level=WARNING

          Arg = carrier-stream-provider=com.ulcjava.base.shared.TrivialCarrierStreamProvider

          Arg = client-coder-registry-provider=com.filemaker.ulc.client.ClientCoderRegistryProvider

          Arg = url-string=

          Arg = launchtype=normal

          Arg = server-language=en

          Arg = server-timezone=US/Pacific

          AdminConsoleJnlpLauncher - using allCertsTrustManager

          AdminConsoleJnlpLauncher - Installing custom trust manager

          AdminConsoleJnlpLauncher - Register HttpURLConnection

          AdminConsoleJnlpLauncher - finished installing custom trust manager

          AdminConsoleJnlpLauncher - installing File Service

          AdminConsoleJnlpLauncher - installing Browser Service

          AdminConsoleJnlpLauncher - createSessionStateListener()




          JNLPClassLoader: Finding library libquaqua64.dylib


          And then the dialog "Admin Console could not start: Admin Server Manager unavailable."

          • 2. Re: FileMaker Server 12 - Another Server admin hiccup

            I think there is a bug in the "Enable access restrictions" OR the format is very sensitive or something.


            I added the following address list and it did not work.




            So I isolated my issue. Now why? I'm not sure yet.