AnsweredAssumed Answered

FileMaker Cloud encryption password not saving correctly

Question asked by greglane on Mar 22, 2018
Latest reply on Jul 26, 2018 by TSGal

We have a FileMaker Cloud 1.16.1.18 instance that is not correctly saving an encryption password. On 3/21, we uploaded a new version of a database that was configured with the same encryption password as the previous version. The file did not open automatically. We then opened it manually and saved the encryption password. We then closed and opened the database to confirm the encryption password was saved. On 3/22, the auto-maintenance process restarted the instance and the databases were not automatically opened because of an incorrect encryption password.

 

Both databases on this instance have the same encryption password and that password is the same as when the instance was created about a month ago.

 

We've disabled auto-maintenance for now. What else can we do to troubleshoot this issue?

 

Thanks,

Greg

 

 

2018-03-21 13:33:58.502 -0400 Information 668 **** Preparing to upload database "Database.fmp12" to "filelinux:/opt/FileMaker/FileMaker Server/Data/Databases/" by "****".

2018-03-21 13:34:06.838 -0400 Information 669 **** Database "Database.fmp12" has been uploaded to "filelinux:/opt/FileMaker/FileMaker Server/Data/Databases/".

2018-03-21 13:34:09.584 -0400 Information 520 **** Administrator disconnected: " [##.##.##.##]" (fmadminserver).

2018-03-21 13:34:09.757 -0400 Information 520 **** Administrator disconnected: " [##.##.##.##]" (fmadminserver).

2018-03-21 13:34:14.173 -0400 Information 418 **** Opening database "Database_dev"...

2018-03-21 13:34:14.173 -0400 Information 418 **** Opening database "Database"...

2018-03-21 13:34:16.411 -0400 Error 939 **** SECURITY: Database "Database" could not be opened: incorrect encryption password.

2018-03-21 13:34:16.436 -0400 Error 939 **** SECURITY: Database "Database_dev" could not be opened: incorrect encryption password.

2018-03-21 13:34:29.335 -0400 Information 418 **** Opening database "Database"...

2018-03-21 13:34:29.336 -0400 Information 827 **** SECURITY: Saved encryption password for database: "Database".

2018-03-21 13:34:29.545 -0400 Information 184 **** Opened database "Database".

2018-03-21 13:34:35.790 -0400 Information 418 **** Opening database "Database_dev"...

2018-03-21 13:34:35.990 -0400 Information 184 **** Opened database "Database_dev".

2018-03-21 13:34:39.318 -0400 Information 140 **** Closing database "Database_dev"...

2018-03-21 13:34:39.338 -0400 Information 168 **** Database "Database_dev" closed.

2018-03-21 13:34:41.018 -0400 Information 418 **** Opening database "Database_dev"...

2018-03-21 13:34:41.217 -0400 Information 184 **** Opened database "Database_dev".

2018-03-21 13:34:43.672 -0400 Information 140 **** Closing database "Database"...

2018-03-21 13:34:43.692 -0400 Information 168 **** Database "Database" closed.

2018-03-21 13:34:45.559 -0400 Information 418 **** Opening database "Database"...

2018-03-21 13:34:45.759 -0400 Information 184 **** Opened database "Database".

...

2018-03-22 00:55:00.545 -0400 Information 486 **** Database Server started.

2018-03-22 00:55:00.546 -0400 Information 418 **** Opening database "Database"...

2018-03-22 00:55:00.546 -0400 Information 418 **** Opening database "Database_dev"...

2018-03-22 00:55:02.219 -0400 Error 939 **** SECURITY: Database "Database_dev" could not be opened: incorrect encryption password.

2018-03-22 00:55:02.245 -0400 Error 939 **** SECURITY: Database "Database" could not be opened: incorrect encryption password.

Outcomes