• Solution: FileMaker Server will not start after Windows Server crash or upgrade

    SHORT ANSWER: Try moving the file ‘ServerCustom.pem’ from the “C:\Program Files\FileMaker\FileMaker Server\CStore” directory to the desktop, and then try starting the FileMaker Server. If it works, you’ll need to download and install a new SSL certificate, but other than that you should be fine. If it still doesn’t work, put it back into “C:\Program Files\FileMaker\FileMaker […]

  • “[Er, Almost] Always Working” FileMaker app Multi-Page PDF viewer

    Note: This technique should be considered “almost always working”, not “always working” as previously (and wishfully) billed. Sorry, as FileMaker and desktop OSes have changed, this file, which relies on several technologies from several different sources working together, has proven to be not always reliable. I would not try to use it in any solution […]

  • Opener file no longer works after upgrade to FileMaker 16

    Due to FileMaker version 16’s new warnings about connecting to servers without SSL,  after upgrading, some opener files simply don’t open files from FileMaker Server over the network like they did under previous versions of FileMaker Pro or FileMaker Advanced. The symptom: Many users use “opener” files, local files saved on their hard drives, to open FileMaker databases […]

  • Case Study: FileMaker database suddenly slow on startup, then speeds up with use

    TL;DR: A corrupt record can cause sporadic performance problems in FileMaker databases, especially when accessing them remotely. I encountered an interesting error recently. A client database on which I am working remotely suddenly took much longer to open than it used to – increasing from about 20 seconds to fully open to about 4 minutes. The database […]

  • Michael Kupietz
  • FileMaker Consultant
  • Serving clients locally and remotely, in California's San Francisco Bay Area and nationwide
  • Phone: (415) 545-8743
  • Download vCard