Server Upgrade v2020.2 to v2021.2 Failed to construct Gallery daemon process, code 9001

DVAMortensen

Windows Server Standard 2019

VM based 4 core, 16GB RAM

Attempting to upgrade our Alteryx Server from v2020.2 to v2021.2 and startup of service fails. Last line in AlteryxServiceLog.log is

2021-06-17 21:18:08.413000,ERROR,5204,AlteryxService,,,,,,,,,"AlteryxService_LogStartupError: There was an error starting the Alteryx Service <Failed to construct Gallery daemon process, process exited code <9001>>"

Also attached log to post.

Need help in debugging this upgrade.

-mark

AlteryxServiceLog.log

DVAMortensen

@joshuaburkhow , @bjschwartz3 

Support helped point me in the right direction for our upgrade issue and resolved our particular problem.  There exists logs for the Gallery service at

[alteryx_global_workspace_home]\Gallery\Logs

Within the latest log file was a FATAL record entry saying something like this:

Command createIndexes failed: E11000 duplicate key error collection: AlteryxGallery.users index: Email_1 dup key: { : "**USER**@**COMPANY**com" }.

This was the root of our issue.  We had two entries in a MongoDB table for this particular user and support told me in later versions they require unique user emails for each user record.  In our case, we had two users with the same email.  

To resolve, support instructed me to launch the embedded MongoDB with this command

[alteryx_install_home]\bin\mongod --dbpath [alteryx_persistence_folder]

then use a MongoDB client such as NoSQLBooster or Robo3T to logon as "user" with the Alteryx' non-admin pwd to the AlteryxGaller db.  The "user" pwd can be captured from the Alteryx System Settings application (it'll be the pwd from the Controller > Persistence > Database section and look like an encoded hex string).

I found the duplicate users and altered the user accounts email for the record that had the oldest last logon time.  Started the AlteryxService and now the upgraded v2021.2 environment is working for us.

-mark