AnsweredAssumed Answered


Question asked by Jason Wood on May 20, 2018
Latest reply on Nov 12, 2018 by CarlSchwarz

I would like to have a FMS AMI in AWS so I can quickly deploy new FileMaker Servers.


I started with a new Windows Server 2012 R2 instance, installed FMS 17 and a wildcard certificate. Then I stopped the database server and shut down the instance, and created an AMI.


I launched a new instance using that AMI but FMS would not start. In the command prompt, I got the error "System error 1003 occurred" when I run 'net Start "FileMaker Server"'. I tried using the FMS installer to "repair" the installation, but at the end of the process, it gave another error, mentioning something about checking permissions. It worked fine after I uninstalled and re-installed, but the whole point was to avoid that.


The original instance works fine. I can start & stop it on different hardware and that works fine too. Why would an image of that system not work?