EAR password not saving after server restart for migrated file

[nat_robinson]

Hey team.

I have a consistent issue that I hope is a config option I am missing somewhere.

When I migrate an encrypted file and embed the EAR password, the password does not store on the server.

The file opens fine after migration but when the server is restarted, those specific migrated files do not open and require the EAR password to re-open.

All other files that weren’t migrated using OttoDeploy open fine.

Any help is appreciated.

All the best,
Nat

[kduval]

Hey Nat,

Unfortunately this is a known issue with FileMaker server. as far as we can tell when a file is replaced on the destination server (which happens during a replace or migrate operation in ottofms deployments), sometimes the encryption key is not saved in a way that persists across FileMaker Server restarts.

Check out these threads for more details and troubleshooting steps:

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

After deployment and restart the 22.02 FMS reopened the files on the 2 servers correctly. No new version of OttOFMS installed, still using 4.10.3 (not broke aint fixing it) so this seems to be solved by Claris. Touching wood now.

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]

How to save encryption key in FileMaker server during deployment

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.

Sorry I can’t give you better news than that!

-Kyle