Unable to access Alteryx Gallery post version upgrade to 2024.1

Hi,

I have followed the Alteryx guidelines and upgraded Alteryx Server version from 2023.2 to 2024.1

The Alteryx Service is running fine, and I can work in Designer but unable to access Alteryx Gallery. (HTTP Error 404. The requested resource is not found.)

Receiving errors under Event Viewer -> Windows Log -> Application

Faulting application name: AlteryxServerHost.exe, version: 2024.1.1.178, time stamp: 0x67649aa6
Faulting module name: KERNELBASE.dll, version: 10.0.17763.6775, time stamp: 0x80a03a31
Exception code: 0xe0434352
Fault offset: 0x0000000000041b39
Faulting process id: 0x740
Faulting application start time: 0x01db76dac4fa643a
Faulting application path: \Program Files\Alteryx\bin\AlteryxServerHost.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: a9c7057a-42ed-424e-a33b-d63c7b48eec2
Faulting package full name:
Faulting package-relative application ID:

Need assistance to fix the issue.

Gallery

Error Message

Server

Accepted answers

EN6924

Hey fmvizcaino

Checked the logs and found Schema migration failed.

The issue has been resolved after renaming the affected collections that has MigrationInProcess/ MigrationInProgress in its name.

And I'm able to access the Gallery now.

All comments

fmvizcaino

Hi @EN6924 ,

Could you please share the steps you did during the upgrade?

Have you performed the preupgrade checks? tried deleting the locks?

Best,

Fernando Vizcaino

EN6924

Hey fmvizcaino

Checked the logs and found Schema migration failed.

The issue has been resolved after renaming the affected collections that has MigrationInProcess/ MigrationInProgress in its name.

And I'm able to access the Gallery now.

JonathanAllenby

For anyone else, we encountered the same error.

Our upgrade was not completing with the error described here:

https://knowledge.alteryx.com/index/s/article/Could-not-finalize-mongodb-restore-the-mongodb-database-failed-to-start-with-exit-code-100

Could not finalize MongoDB restore. The MongoDB database failed to start with exit code: 100.

It wasn't disk space but we ran through Resolution B (skipping increasing the disk space) and it allowed the Alteryx Service to start and the upgrade to finish. However, the Gallery was inaccessible with 404 on both localhost and the web address.

Investigating the alteryx-migration.txt log revealed the following:

2025-05-14 11:24:29.110388,INFO,1,AlteryxServerHost,migrationLogger,MoveNext,Renaming collection from 'dCMEConnections' to 'dCMEConnectionsMigrationInProcess_50'->,
2025-05-14 11:24:29.110388,INFO,1,AlteryxServerHost,migrationLogger,MoveNext,Done renaming collection->,
2025-05-14 11:24:29.110388,INFO,1,AlteryxServerHost,migrationLogger,MoveNext,,
2025-05-14 11:24:29.259389,FATAL,1,AlteryxServerHost,migrationLogger,DoMigrateDatabase,Migration failed with error: Command aggregate failed: PlanExecutor error during aggregation :: caused by :: indexes of target collection AlteryxGallery.dCMEConnections changed during processing..,
2025-05-14 11:24:30.750390,FATAL,1,AlteryxServerWebApiHost,migrationLogger,DoMigrateDatabase,Database requires migration from 49 to 61. Attempting to obtain lock...,
2025-05-14 11:24:30.871392,FATAL,1,AlteryxServerWebApiHost,migrationLogger,DoMigrateDatabase,"...lock obtained, performing migration.->Services will start but be unavailable until migration is complete.",
2025-05-14 11:24:30.871392,INFO,1,AlteryxServerWebApiHost,migrationLogger,MoveNext,Starting Migration: 50,
2025-05-14 11:24:31.096390,INFO,1,AlteryxServerWebApiHost,migrationLogger,MoveNext,Renaming collection from 'dCMEConnections' to 'dCMEConnectionsMigrationInProcess_50'->,
2025-05-14 11:24:31.096390,INFO,1,AlteryxServerWebApiHost,migrationLogger,MoveNext,Done renaming collection->,
2025-05-14 11:24:31.100387,INFO,1,AlteryxServerWebApiHost,migrationLogger,MoveNext,,
2025-05-14 11:24:31.132386,FATAL,1,AlteryxServerWebApiHost,migrationLogger,DoMigrateDatabase,Migration failed with error: Command create failed: Collection AlteryxGallery.dCMEConnectionsPostMigration_50 already exists..,

The rest of the log was it trying and failing to create the new collection and failing since it already existed. Using Robo3T (Guide: https://knowledge.alteryx.com/index/s/article/How-to-Connect-to-an-Embedded-Server-UI-MongoDB-using-Robo-3T) we found the collection and renamed it.

Following this, we retried Resolution B of the article I previously linked to in order to retry the migration and success! The Alteryx Server has been upgraded and the Gallery front end is now accessible.

Quick Links

This months top contributors

atcodedog05 19598

Qiu 15879

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703