5 Replies Latest reply on Apr 6, 2015 12:54 PM by disabled_ntaylor

    FMS9 install on Yosemite, can't get Deployment Wizard to run

    DagCrumb

      Title

      FMS9 install on Yosemite, can't get Deployment Wizard to run

      Your post

      FMS9 install on Yosemite, can't get Deployment Wizard to run

       

      An OS X 10.4.11 iMac with FileMaker Server 9 (and FileMaker Pro 9) is serving files to a small group of computers.  Someone else set that up.

      I’m attempting to replace it / set up a new iMac with Yosemite / 10.10 OS X (64bit), to be a FileMaker Server 9 server.  All the web posts I said I couldn’t use the migration assistant between these OS’s, so I though tI’d go from scratch.

      I believe I have installed FMS9, but cannot get to the “deployment wizard”. (I haven’t had a chance to set up an administrator login or password.) Some posts say I need to roll back java, edit Java’s security (did that), try a different browser (did that), tweak browser securities (did that), drop firewall to open port (did that), and so on.  So before I waste more time on the various suggestions I’ve come across, I thought I”d ask experts.
      _____________
      Here are the details:

      I used apple’s remote disc to copy the FMS installer files from the old mac’s dvd drive to my new mac desktop. The filename is “fms_9.0v1_R2_full_ESD.dmg”. This FMS9 installer said I needed JAVA, which I already had. Then it seemed I needed 32bit java, but before I got there I found the download “JavaForOSX2014-001.dmg”, which allowed me to run the FMS9 installer.  But then when I tried the initial run of ht program, I had java security permissions errors, until I entered this into Java’s Exception Sitelist: http://localhost:16000.  

      Now when I clicked on the FMS9 start page, it loads a page (url is: file:///Library/FileMaker%20Server/Admin/admin-server/launch-page/prelaunch_single_en.html), which says “please wait while the Admin Server starts” but never proceeds.   If I click on the link (provided sometimes) and download a copy of “admin_console_init_webstart.jnlp” and double-click on it, it says:

      Application Error:  Unable to launch application (see details in attachment below)

      At one point, (I don’t know why)  it seemed to progress past this point, it loaded a white console with black text. But it doesn’t look at all like the “deployment wizard” I see in the “getting started” PDF.
      I tried installing “FMP9” as well but it made no difference.
      _______
      So my most urgent questions are:
      (1) how to get the DEPLOYMENT wizard to open, and
      (2) if necc, how to get the “admin console” to open consistently (although I don’t know what its for)
      (3) Seeing as I can’t even get the software to run — will I ever be able to set up the server to serve the eight or so databases they need? Does this require an expert in FMS?

        • 1. Re: FMS9 install on Yosemite, can't get Deployment Wizard to run
          DagCrumb

          Application Error:  Unable to launch application
          ___
          details:
          _________
          “console” tab:
          #### Java Web Start Error:
          #### Connection refused
          ______
          “exception” tab
          java.net.ConnectException: Connection refused
              at java.net.PlainSocketImpl.socketConnect(Native Method)
              at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
              at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
              at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
              at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
              at java.net.Socket.connect(Socket.java:589)
              at java.net.Socket.connect(Socket.java:538)
              at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
              at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
              at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
              at sun.net.www.http.HttpClient.<init>(HttpClient.java:211)
              at sun.net.www.http.HttpClient.New(HttpClient.java:308)
              at sun.net.www.http.HttpClient.New(HttpClient.java:326)
              at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1168)
              at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1104)
              at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:988)
              at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:986)
              at java.security.AccessController.doPrivileged(Native Method)
              at java.security.AccessController.doPrivileged(AccessController.java:713)
              at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:985)
              at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:932)
              at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1512)
              at sun.net.www.protocol.http.HttpURLConnection.access$200(HttpURLConnection.java:90)
              at sun.net.www.protocol.http.HttpURLConnection$9.run(HttpURLConnection.java:1432)
              at sun.net.www.protocol.http.HttpURLConnection$9.run(HttpURLConnection.java:1430)
              at java.security.AccessController.doPrivileged(Native Method)
              at java.security.AccessController.doPrivileged(AccessController.java:713)
              at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1429)
              at com.sun.deploy.net.HttpUtils.followRedirects(Unknown Source)
              at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
              at com.sun.deploy.net.BasicHttpRequest.doGetRequestEX(Unknown Source)
              at com.sun.deploy.cache.ResourceProviderImpl.checkUpdateAvailable(Unknown Source)
              at com.sun.deploy.cache.ResourceProviderImpl.isUpdateAvailable(Unknown Source)
              at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
              at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
              at com.sun.javaws.Launcher.updateFinalLaunchDesc(Unknown Source)
              at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
              at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
              at com.sun.javaws.Launcher.launch(Unknown Source)
              at com.sun.javaws.Main.launchApp(Unknown Source)
              at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
              at com.sun.javaws.Main.access$000(Unknown Source)
              at com.sun.javaws.Main$1.run(Unknown Source)
              at java.lang.Thread.run(Thread.java:745)
          ____

           

          • 2. Re: FMS9 install on Yosemite, can't get Deployment Wizard to run
            RickWhitelaw

            FMS 9 will not run on Yosemite as far as I know.

            • 3. Re: FMS9 install on Yosemite, can't get Deployment Wizard to run
              DagCrumb

              I  noticed that there's one other Yosemite computer that's running fine as a FMP9 client.

              I work for a small non profit that just spent a ton on the new Imac, but can't afford to upgrade to FMS/FMP 13. So we're looking for any kind of work-around...

              • 4. Re: FMS9 install on Yosemite, can't get Deployment Wizard to run
                RickWhitelaw

                Considering it took a few iterations of FMS 13 to become compatible with Yosemite I really doubt there's a workaround.

                • 5. Re: FMS9 install on Yosemite, can't get Deployment Wizard to run

                  Dag Crumb:

                   

                  Thank you for the post.

                   

                  “FileMaker 12 and earlier versions of FileMaker have not been tested or certified with OS X Yosemite (10.10).  These products were developed and released before OS X Yosemite became available.

                  While these earlier versions may install and run on OS X Yosemite (10.10), you may encounter installation and stability issues for which there is no resolution.”

                   

                  FileMaker 12 and earlier versions, OS X Yosemite compatibility

                   

                  Additionally, for a list of all the operating systems tested to be compatible for FileMaker Server 9, please review the following knowledge base article:

                   

                  FileMaker Server operating system requirements - all versions

                   

                  TSFalcon

                  FileMaker, Inc.