Invalid Header response from server (1): Empty header - Cryptomigration tool failure

[jamedina]

Hi Server community, taking a chance to see if anyone has similar experience or results running the CryptoMigration Tool.

For context, this is Alteryx Server 2022.1 (Patch 12) with a user managed mongodb running on an EC2 instance.

When attempting to run the Crypto Migration Prep Tool we get these errors:

6;RunasCredential failed to fetch decrypt key using AES256 encryption. <Invalid Header response from server (1): Empty header>. Attempting to fetch keys with sha256 encryption (for Version < 22.3).
3;RunasCredential failed while Decrypting storage key. <Invalid Header response from server (1): Empty header>
3;Error during key initialization. <Invalid Header response from server (1): Empty header>

Looking at the service migration log we see zero AS_Schedules successfully migrated.  From our experience, this means the scheduler api would fail after upgrading Alteryx Server to a newer version as the __ServiceData blob becomes incompatible.  Alteryx support is in the loop although they say this is a new error so I thought it best to socialze on community. 

[jamedina · Accepted solution]

Quick update after confering with support on the matter. The crypto migration from the server installer completed with success after moving ahead with the upgrade to 2024.1

The 2024.1 install did take longer than expected, however we saw all the schedules and collections migrate as expected.  We took a steps to delete disabled and completed schedules.  Also removed objects from commandQueueItems, checked for locks and re-indexed the database before installing 2024.1.  Not sure if that had any impact or was germane to the solution but content to see a successful migration.