Jump to content

Filemaker Server 16 and Windows 10

Recommended Posts

The FM specifications state that (On Windows platform), the Windows 10 OS is nos apparently supported.

Any experiences about installing FMServer 15 or 16 under Windows 10?

Thanks in advance,



Share this post

Link to post
Share on other sites

not supported, so why would you want to?

You'll find plenty of posts of people who have tried with 15, some were able to make it work, some didn't.

Share this post

Link to post
Share on other sites

Consumer-grade Windows OS is lacking many of the optimizations that a true server has. Along with vast differences in prioritizing of services and processes, it is truly a different kind of beast.

As Wim said, you may get it to work. You may get it to partially work. It may put your data at risk. Or it may fail completely. At that point, you have no support options with FMI. They won't help you until you get it onto a supported OS.

Some important things to keep in mind should you continue down that route.

Share this post

Link to post
Share on other sites

Well it is the classic strange issue that comes to me.

A company set up a server in a NUC5i5RYH with Win10 and said it was good enough for FMServer 15… and it was not supported.

I can see the tech reasons in favor of the server-grade Windows OS

I will try a search in order to see if the difficulties are beatable. 

Thanks, folks !!

Share this post

Link to post
Share on other sites

How many users?

Share this post

Link to post
Share on other sites

4 users 


The 4 machines are: (3 windows and 1 mac.

Next year perhaps the 5th license to be used with FMGo. Not important.

Share this post

Link to post
Share on other sites

In my last job we developed for a customer that ran their FMS on a Win7 system. They had constant issues and rebooted the box nearly daily. We kept telling them to move it to a proper server OS. They haven't as yet.

You can always buy a Mac mini and run it on that for those few users. Here in Australia they sell for $800 and it's supported by FileMaker. Just make sure you don't skimp on backups as the mini only has a single drive.

Share this post

Link to post
Share on other sites

Well, it can work.

But you may run into issues like your Windows PC goes to sleep or restarts to install updates.

For Server you can configure more to keep it running all the time. Depends all on the compromises you like to make.

Share this post

Link to post
Share on other sites

As always helpful and concise messages.

I will search in the forum to give the instalation process a try. 

Thanks to all.

Share this post

Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Ben_TFS
      Hi There, I am writing a system script that needs to be run using an admin account on a Windows Server 16 machine. However when I try to set this up it says that the script is missing or invalid.
      The login details I am entering are to an admin account on the local Windows Server 2016 machine. I have tried both these, and the default administrator account.
      If I try to enter the login details for the FMS16 account it says Invalid account.
      For now I am just trying to run a test script. This script executes successfully when I run it manually as well as when I schedule it to run using the default account.   Code in test.bat: @ECHO OFF  PowerShell.exe -NoProfile -ExecutionPolicy Bypass -Command "& 'C:\Program Files\FileMaker\FileMaker Server\Data\Scripts\test1.ps1'";   Code in test1.ps1: $put = "C:\Program Files\FileMaker\FileMaker Server\Data\Scripts\test.txt" $filecontent = "Hello World" $filecontent | Out-File $put -Encoding ASCII   Screenshot 1 shows the option I am talking about. For the test if I do not tick this then it executes fine. Screenshot 2 is showing that it comes up as missing or invalid.

    • By boilnh2o
      So we VPN in to our office network and then connect to our FM16 Server with either our laptops (Filemaker 16) or FM Go (16.0.4) 
      One of our users can get as far as loading the two database icons from the server but when trying to open the file getting timed out connections. Even when connecting to the internet via a WiFi connection. At the same time, his laptop will connect.
      Looking in the logs on the server  - there's no sign of the FMGo connection.
      Looking at VPN logs (although we know he's connecting) shows a normal connection into our network.
      Is there any other source of information that might illuminate the problem?
    • By boilnh2o
      So I'm setting up WebDirect and for the first time setting up a worker machine. I initially set it up using the IPs of my two machines. It worked. I could access my DB with a browser.
      After setting up our router to forward port 80 traffic to the worker machine*, I found that it re-wrote the URL to the IP address which wasn't going to work.
      I'm running a Mac Server so I set up the DNS service to resolve the FQDN that is used by our remote IP (dynamic DNS) to the internal IPs and then set my two servers to use our internal name server.
      I disconnected the worker and then reconnected using the FQDN. It registered with my FM Server but it will not start.
      "cannot start or stop worker machine"
      Logs tell me nothing other then the worker was added.
      *In the process of trying to read up on this and find what I was missing I discovered that I might be thinking of the worker/master incorrectly. That I should be directing my browser to the Master not the Worker.
      Both Servers running 10.13.3 and the current version of FM Server 16
      Thanks for any insight.
    • By Siva D
      We have ESET Endpoint Security on the FileMaker Server 16 machine (Single machine deployment).
      When ESET Firewall is active with default settings, We couldn't access FileMaker databases from FileMaker Pro using external network (WAN).
      We opened the ports 5003, 16001, 80 and 443. Still no success.
      If we completely disable Firewall, or If we open "All" ports, we could access the databases.
      Please someone direct us how to open only FileMaker Server specific ports on ESET Firewall.
    • By Olypatchmaster
      Our network person and I have done a bunch of troubleshooting and came up with this summary and a few questions.
      Ever since we installed FileMaker 16 in our two-machine setup, Zulu has been failing. In the Zulu error log from C:\Program Files\360Works\Applications\logs:
      Oct 2, 2017 8:44:59 AM PDT com.prosc.mirror.config.server.FileMakerServerInfo getHostAddressForProperties
      INFO: Will use for direct WPE address.
      Oct 2, 2017 8:45:05 AM PDT com.prosc.fmpjdbc.FmXmlRequest doRequest
      INFO: Starting request:
      Oct 2, 2017 8:45:05 AM PDT com.prosc.fmpjdbc.FmXmlRequest setProductVersion
      WARNING: Null product version; assuming 12
      Oct 2, 2017 8:45:05 AM PDT com.prosc.fmpjdbc.FileMakerException <init>
      INFO: com.prosc.fmpjdbc.FileMakerException: Error 959: XML Web Publishing is not enabled - Run the FileMaker Server deployment assistant and make sure that the XML web publishing checkbox is selected () username: domain\user / requestUrl:

       I verified that the URL does indeed return an error code of 959. Playing around with it, I found that if you use the DNS name of the machine instead of the localhost IP:port (https://wpe.domain.edu/fmi/xml/FMPXMLRESULT.xml?-db=DatabaseName&-lay=ProscNoSuchTable&-view), the request returns an error 105 (expected response) instead. 
      I poked around on the internet trying to find out more about this, and discovered the -dbnames command; again, it works fine on the main https port (https://wpe.domain.edu/fmi/xml/FMPXMLRESULT.xml?-dbnames), but returns a 959 on the Custom Web Publishing port of 16020 ( So it’s like XML is enabled on port 443, but not for the Custom Web Publishing port 16020. How is that possible?
      For reasons we don’t fully understand and haven’t figure out how to correct, both the FileMaker Master and the Worker machines ended up with the Web Publishing Engine. So I tried the port 16020 request on the Master server, and it works! Which is great, except we want it to work on the Worker machine, not the Database server which ended up with a WPE.
      Some questions:
      1)      We know XML is enabled on the main (port 443) site, what do we need to do to make work on the localhost:16020 site?
      a. I hope this involves moving the ‘Web Server’ listed in the Admin Console to the Worker machine, but if not any info on what might be going on there would be great.
      2)      If we can’t get the Worker machine to realize XML is enabled on port 16020, can we change the FM config so Zulu doesn’t use port 16020 ‘for direct WPE address.’?
      3)      If we can’t do that, are there any issues with installing it on the Master, other than the obvious issue that we don’t want the WPE on that machine?
      Thanks for any insight anyone might have.

Important Information

By using this site, you agree to our Terms of Use.