10 Replies Latest reply on May 29, 2017 2:32 AM by alangodfrey

    Filemaker Server 16 'Open Remote...' response time

    alangodfrey

      I have installed FM Server 16 on an iMac 14.4 (and I'm not a Mac user, sorry).  It is running:

      Sierra 10.12.5

      1.4 GHz Core i5

      8GB RAM

      1600MHz DDR3

       

      I have FM Pro installed on a Core i5 Windows 10 Pro machine sitting beside it.  When I 'Open Remote...' on the Windows machine it shows the Server Machine straight away in the Launch Centre, then gives me a 'Waiting response...' progress bar for 30 seconds before it shows me the Sample File.  When I double-click the Sample File it gives me an egg timer for another 30 seconds before it opens.  Once opened it seems to be fine, though it's hardly a demanding file.

       

      Can anyone confirm if this is normal behaviour for Version 16?

       

      Thanks very much.

       

      - update -

      When I install FM Pro 16 on the same iMac and use it to 'Open remote...' it shows the Server's Sample File immediately, and when I double-click the Sample File it opens immediately, all as expected.

        • 1. Re: Filemaker Server 16 'Open Remote...' response time
          wimdecorte

          alangodfrey wrote:

           

          1.4 GHz Core i5

           

           

          That is major league slow... Given that processing power is one of the top two typical bottlenecks for FMS I would get away from that setup ASAP.

           

          In the meantime:

          If the connection is also slow from any other machine then the server is your main issue.

          If the connection is reasonably fast from other machines then you may want to check if your client has:

          - enough free disk space

          - isn't doing anything else with the connection

          - isn't running any monitoring / AV / scanning process on anything on the network connection that would slow things down

          - try and delete the dbcache folders that FMP keeps. Those have been known to cause slowdowns under certain circumstances.

          1 of 1 people found this helpful
          • 2. Re: Filemaker Server 16 'Open Remote...' response time
            alangodfrey

            Thanks for the tips, Wim, and confirmation that this is not normal.  (Phew...)

             

            The Server and Client are sitting side-by-side on a test bench, each doing nothing else.  Plenty of HD space, and I thought the spec of the iMac seemed there or thereabouts with the hardware spec recommended.  Certainly for opening one Sample File and accessing by one client.

             

            Both machines are connected to the router via a switch.  I removed them from the network and connected them both directly to another stand-alone router.  Then the client connected in an instant.

             

            I removed the switch and connected them both directly to the original router, and the problem came back.  (I changed leads also; no difference.)

             

            I connected another laptop via wi-fi and it flashed the 'waiting for response' progress bar for maybe a second, then would open the Sample File instantly when double-clicked.  Connecting it via cable produced the same result.

             

            (Update: the laptop hadn't been turned on for a while, and I noticed a lot of HD activity.  Checking Task Manager showed it was running a Windows Security Check.  Retrying after that was finished removed even the second's delay.  Nothing similar seems to be affecting the original PC.)

             

            I conclude it is a network issue (presumably with that particular Win 10 workstation) and probably then nothing to do with FM.

             

            (This is all further to our previous conversation, where I am trying my darndest to find the most cost-effective way to deploy the server.  I know nothing about the Mac platform, but I am looking to see if a Mac running Sierra 10.12 is a less-cost option than a Windows server running Server 2016 etc.  This is for clients who have a very light workload by FM or Windows standards - they have maybe 10 clients purely because of the layout of their offices; it is not a reflection of the data processing.)

             

            Thanks again for your help.

            1 of 1 people found this helpful
            • 3. Re: Filemaker Server 16 'Open Remote...' response time
              wimdecorte

              alangodfrey wrote:

               

               

              (This is all further to our previous conversation, where I am trying my darndest to find the most cost-effective way to deploy the server. I know nothing about the Mac platform, but I am looking to see if a Mac running Sierra 10.12 is a less-cost option than a Windows server running Server 2016 etc. This is for clients who have a very light workload by FM or Windows standards - they have maybe 10 clients purely because of the layout of their offices; it is not a reflection of the data processing.)

               

               

               

              Keep in mind that all entry-level Macs (Mac Minis and iMac) have fairly locked-down hardware that is not user-upgradeable and does not come with a lot of processing power.  Mac Minis for instance only come with 2 cores.  For 10 concurrent users and perhaps some PSoS or server-side schedules (and god forbid; WebDirect) that just not going to cut it.  So make sure to work backwards from the projected workload in picking the right machine.

              • 4. Re: Filemaker Server 16 'Open Remote...' response time
                Markus Schneider

                but when FMP is installed on the server machine (OP edited the first posting apparently), the file shows immediately

                 

                -> network?

                • 5. Re: Filemaker Server 16 'Open Remote...' response time
                  taylorsharpe

                  Trying connecting with a favorite using an IP only (don't use domain or Bonjour).  Or make an alias such as fmp://[server ip]/[filename].fmp12 (e.g., fmp://192.168.1.10/myfile.fmp12) and see if that takes you there faster.  If so, it is because of networking issues such as Bonjour or DNS.  I see this a lot in LAN networks the were not put together by  a networking specialist, particularly the problem with Bonjour searches. 

                  • 6. Re: Filemaker Server 16 'Open Remote...' response time
                    alangodfrey

                    Thanks very much, Taylor

                    It took me a while to wade through the latest un-intuitive way to add a Favourite, but when I did, this is it:

                    - I add the Sample filepath as a Favourite

                    - I 'Open remote...' and choose from the Favourites

                    - The file shows immediately

                    - Double-click it: it open immediately.

                     

                    I would never have thought that setting a 'Favourite' would have made such a (or indeed any (short of 'convenience')) difference.  Now there's food for thought for me.

                     

                    (Wim: the workload is light by FM standards, I believe, and the clients have no interest in Web Direct.  Thanks for your advice: I shall try to implement it as best I can.)

                     

                    Yes, Markus - I now believe this is a network issue.  Thank you.  Taylor's suggestion exposes it as a little more complicated; not just a straightforward 'slow network connection' issue.

                     

                    Thank you to everyone.  I'll pursue the network issue.

                    • 7. Re: Filemaker Server 16 'Open Remote...' response time
                      CarlSchwarz

                      alangodfrey wrote:

                       

                       

                      where I am trying my darndest to find the most cost-effective way to deploy the server. I know nothing about the Mac platform, but I am looking to see if a Mac running Sierra 10.12 is a less-cost option than a Windows server running Server 2016 etc. This is for clients who have a very light workload by FM or Windows standards - they have maybe 10 clients purely because of the layout of their offices; it is not a reflection of the data processing.)

                       

                      Thanks again for your help.

                      If their internet connection is good enough and your solution runs well over a WAN then renting a FMServer offsite can also be budget conscious.

                      • 8. Re: Filemaker Server 16 'Open Remote...' response time
                        user19752

                        "30 seconds" also show it as network issue, waiting something time out.

                        When I try to open "favorite" file that is not hosted any more, it takes 30 seconds before showing error dialog.

                         

                        I want some way to edit favorite in "text", not reselect it from list in host (it is hidden), nor edit registry

                        And now I saw registry, it have interesting format as

                        fmnet://hostIP/hostName/filename.fmp12

                        and it is also showed as tooltip in "Manage Favorites".

                        • 9. Re: Filemaker Server 16 'Open Remote...' response time
                          alangodfrey

                          Thanks, Carl - I'm going to try the solution over a WAN when I get it fully converted from version 11.  At the moment it is a critical USP for these customers that it is self-hosted inside their own office.  All the other solutions they could use are web-hosted, and they've had any or all of, a) slow performance, b) internet going down at some stage, and c) being held to ransom when they want to move to another solution provider.

                           

                          There's no point in me trying it until I get all 200 layouts converted from Classic theme, of course...

                          • 10. Re: Filemaker Server 16 'Open Remote...' response time
                            alangodfrey

                            I tried flushing the DNS cache, and it made no difference.  Taylor's solution still works every time, and simple 'Open remote...' still takes 30 seconds every time.

                            It's as if FM tries to find the Server with 'Open remote...' one way, times out with a failure, so then says 'I'll try it another way' and connects.  Then it tries to open the found file in the 'Open Remote' dialogue, times out, tries another way, and opens.

                             

                            It's as if Taylor's method tells FM to just bypass all the first bit and gets straight to the chase.