I have been struggling with this on a new install of FileMaker 184.108.40.206 and running the default Java 8 update 171 on WIndows Server 2016. I am working with file that I am migrating from a FileMaker 13 installation that is being completely replaced hardware and software. So we using a fresh VM on a fresh box with a fresh OS with a fresh install of FileMaker.
I am well aware that many people have posted this error over the years. It seems to be a perennial bug with mysterious workarounds and rumoured causes. Apparently it has existed since FM13, in fact I encountered it in that version, but I was able to fix it then. This time no.
I have tried them all:
- Make sure the account you choose has the fmapp extended privilege set turned on.
- Try resetting the script triggers when the file opens in the client
- Try creating different users
- Export a compact copy of the file
- Recover the file
- Restart the server
- Update java
- Reinstall everything
None of it works.