Upgrade OttoDeploy to version 2 FAILED

I have tried a couple of times to upgrade my OttoDeploy using the recommended method. Both times it has failed. I don’t have my file encrypted on my server. Not sure why it would fail. Here is the detailed log from the display:

queued - Deployment queued 00:00.000
starting - Starting deployment: “Upgrade OttoDeploy to version 2” 00:00.000
starting - 1 files 00:00.002
closing - Starting to close files 00:02.369
closing - Files closed successfully 00:03.068
fetching - Downloading source files for buildId ottodeploy-2.0.0 00:03.286
fetching - Download completed, unzipping. 00:03.485
fetching - Unzipping OttoDeploy.fmp12 00:03.488
fetching - Source files fetched successfully 00:03.499
migrating - Starting data migration 00:04.196
migrating - Starting data migration of OttoDeploy.fmp12 00:04.198
migrating OttoDeploy.fmp12 The source file is not encrypted.
Source: /opt/FileMaker/FileMaker Server/Data/Operation_DBs/Otto/OttoDeploy.fmp12
00:04.981
migrating OttoDeploy.fmp12 Command failed with exit code 4: /opt/FileMaker/FileMaker Server/Database Server/bin/FMDataMigration -src_path /opt/FileMaker/FileMaker Server/Data/Operation_DBs/Otto/OttoDeploy.fmp12 -src_account Developer -src_pwd *** -clone_path /opt/FileMaker/FileMaker Server/Data/Backups/OttoFMS/inbox/ottodeploy-2.0.0/OttoDeploy.fmp12 -clone_account admin -clone_pwd *** -target_path /opt/FileMaker/FileMaker Server/Data/Backups/OttoFMS/inbox/ottodeploy-2.0.0/OttoDeploy_otto_migrated.fmp12 -clone_key *** -force
The source file is not encrypted.
Source: /opt/FileMaker/FileMaker Server/Data/Operation_DBs/Otto/OttoDeploy.fmp12 00:05.936
opening - Starting to open files 00:08.126
opening - Files opened successfully 00:08.817
post-deployment script - Post-deployment script not run since deployment failed 00:08.819
done - Deployment process failed. Original files are unmodified. 00:08.821
post-deployment steps - Removing builds from inbox 00:08.828

Please advise.
Jeff

Hey Jeff,

It is failing since your file is now encrypted but the OttoDeploy source file is encrypted. OttoFMS cannot currently migrate data from an unencrypted file to an encrypted file, they need to either both be encrypted or both unencrypted.

We do not recommend keeping your OttoDeploy file unencrypted as it stores full-access passwords for your files. However, if you want to keep it unencrypted you will need to perform the migration yourself. You’ll need to choose the manual route, pull down a copy of OttoDeploy version 2.0.0, decrypt it, and perform a migration of your file onto the new file.

-Kyle