Server migration failed (2023.2)

[LordingBeaten]

I started the migration procedure this morning to move from version 2023.1 to version 2023.2.1.7.

Since installation, the server does not restart.

The "AlteryxService test" command returns many errors.

Error, could not migrate record with id 651cb94b0e3300003400313c for table "AS_Results". Message: Column: ExecutionTime Exception: The format of the input string is incorrect.

Error, could not migrate record with id 651cffad0e3300003400313e for table "AS_Results". Message: Column: ExecutionTime Exception: The format of the input string is incorrect.

Error, could not migrate record with id 651e0acb0e33000034003140 for table "AS_Results". Message: Column: ExecutionTime Exception: The format of the input string is incorrect.

Error, could not migrate record with id 651e512d0e33000034003142 for table "AS_Results". Message: Column: ExecutionTime Exception: The format of the input string is incorrect.

Error, could not migrate record with id 651f5c4c0e33000034003144 for table "AS_Results". Message: Column: ExecutionTime Exception: The format of the input string is incorrect.

[...]

Error, could not migrate record with id 651cb9240e3300003400313b for table "AS_Queue". Message: Column: ExecutionTime Exception: The format of the input string is incorrect.

Error, could not migrate record with id 651cff9c0e3300003400313d for table "AS_Queue". Message: Column: ExecutionTime Exception: The format of the input string is incorrect.

Error, could not migrate record with id 651e0aa40e3300003400313f for table "AS_Queue". Message: Column: ExecutionTime Exception: The format of the input string is incorrect.

Error, could not migrate record with id 651e511c0e33000034003141 for table "AS_Queue". Message: Column: ExecutionTime Exception: The format of the input string is incorrect.

Error, could not migrate record with id 651f5c240e33000034003143 for table "AS_Queue". Message: Column: ExecutionTime Exception: The format of the input string is incorrect.

Error, could not migrate record with id 651fa29d0e33000034003145 for table "AS_Queue". Message: Column: ExecutionTime Exception: The format of the input string is incorrect.

[...]

Migration incomplete due to records that failed to migrate.

Done renaming collection

ERROR: __ServiceData column should not be present on any records; found on AS_Results

Aborting migration

Removing collection: AS_ResultsFilesMigrationInProcess_2

Removing collection: AS_ResultsMigrationInProcess_2

Removing collection: AS_QueueInputsMigrationInProcess_2

Removing collection: AS_App_ChunksMigrationInProcess_2

Removing collection: AS_SchedulesMigrationInProcess_2

Removing collection: AS_ApplicationsMigrationInProcess_2

Removing collection: AS_ApplicationVersionsMigrationInProcess_2

Removing collection: AS_PackageDefinitionsMigrationInProcess_2

Removing collection: AS_QueueMigrationInProcess_2

Removing collection: AS_TileSetsMigrationInProcess_2

Removing collection: AS_TileSetAccessTimesMigrationInProcess_2

Removing collection: AS_RunAsCredentialsMigrationInProcess_2

Removing collection: AS_ResourcePermissionsMigrationInProcess_2

Removing collection: AS_ResourcesMigrationInProcess_2

Removing collection: AS_InsightsMigrationInProcess_2

Removing collection: AS_GalleriesMigrationInProcess_2

Done Aborting migration

There was an error starting the Alteryx Service:

La migration du serveur a échoué avec le code de sortie <3762504530>. Consultez les journaux de migration pour obtenir le message d'erreur détaillé. Cette erreur doit être corrigée pour que le service démarre.

[fmvizcaino]

Hi @LordingBeaten ,

First and foremost, I wouldn`t recommend to upgrade to 23.2 just yet. The new version is still in the first major release, which means that you could be experiencing something unexpected that will be soon fixed. For your reference, version 23.1 had 3 patches do fix bugs, 22.3 had 5 and 22.1 had 8.

I would recommend you to reach out to Alteryx support through your case portal.

The error you are receiving is brand new and very specific to this new version. They recently removed a column called ServiceData from MongoDB and for some reason the MongoDB migration tool is not properly removing it.

Please post the fix suggested by Support later here.

Best,

Fernando Vizcaino

[PatPli]

Hello,

I'm a LordingBeaten's colleague.

Finally the problem was categorised as a defect by Alteryx support. The problem appeared because we have installed with regional and language settings in French. 

To successfully migrate we had to put regional and language in English but it remains one problem : the schedules run now one hour early. We have to open a new ticket for this.

[fmvizcaino]

Hi @PatPli ,

Thanks for sharing!

This thread is discussing the issue you just mentioned. https://community.alteryx.com/t5/Alteryx-Server-Discussions/Alteryx-Server-Upgrade-2023-2-Timezone-G...

Best,

Fernando Vizcaino