How to save encryption key in FileMaker server during deployment

[ajohn]

Hi,

I recently started using OttoFMS v4.11 and OttoDeploy for migration and I am wondering if there is an option to save the encryption key while opening the file on FileMaker server after a deployment.

I ask because when we reboot the server after a deployment, the FileMaker server errors out with “Error 939 SECURITY: Database could not be opened: incorrect encryption password.”

Any thoughts or insights on how to fix this error and proceed is appreciated.
Thank you.

[kduval]

Hey @ajohn ,

OttoFMS will save the encryption key by default when opening the files. However, we have seen the same issue with the FileMaker Server restarts that you see. It seems that there are circumstances where FileMaker Server does not properly save off the encryption keys in a way that persists across restarts of the server.

Usually when we see this you can open and close the file without entering the encryption key after running the OttoFMS deployment, but restarting the server will have inexplicably lost the encryption key that was saved.

We’re investigating further to see if there is something that we can do to avoid the issue (or report to Claris as a bug), but we haven’t fully tracked down the issue yet.

Thanks for the report!

-Kyle

[kduval]

Check out these other two threads for more details:

Option to save encryption password or not after deployment opening (--savekey)

One last question. How does the error show up for your support team? Is it in OttoFMSs logs or is it from FileMaker Server’s logs. Knowing the specifics of the error, might help us track down any edge cases that might be out there. Thanks Todd

Saved Encryption Password removed after deployment

Encryption passwords that are stored in FMS (via the “Save Password” checkbox shown below) seem to be erased when an OttoFMS deployment is performed. Otto opens the files just fine after a deployment, but after a non-Otto-related restart the files stay closed and the logs show SECURITY: Database "database" could not be opened: incorrect encryption password. Once I open one, save the password, and open the rest, reboots work as normal. Is OttoFMS “clearing” the encryption password? [image]

-Kyle