This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
on 01-11-201907:37 AM - edited on 09-05-201901:02 AM by SophiaF
As documented in the Community article Alteryx Install Wizard | 2018.1, Alteryx Server version 2018.1 includes a new version of the embedded MongoDB(MongoDB functions as the server's persistence layer). If you are upgrading your Alteryx Server from an older version to 2018.1 or greater, your MongoDB will be migrated from Mongo 3.0 to Mongo 3.4 as part of the process.
Some users have reported the following error after beginning the migration :
Unhandled exception has occurred in your application.
System.AggregateException: One or more errors occurred. ---> System.InvalidOperationException: Process must exit before requested information can be determined. at System.Diagnostics.Process.EnsureState(State state) at System.Diagnostics.Process.get_ExitCode() at MongoDbUpgradeTo30.MongoDBManager.HandleMongoExit(String dbPath) at MongoDbUpgradeTo30.MongoDBManager.StartMongo(String mongoExeName, String dbPath, String port, Boolean withAuth, Boolean setMmapFlag) at MongoDbUpgradeTo30.Migrator.StartNewMongo() at MongoDbUpgradeTo30.Migrator.PerformMigration() at System.Threading.Tasks.Task`1.InnerInvoke() at System.Threading.Tasks.Task.Execute() --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at MongoDbUpgradeTo30.MainForm.StartMigration_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ---> (Inner Exception #0) System.InvalidOperationException: Process must exit before requested information can be determined. at System.Diagnostics.Process.EnsureState(State state) at System.Diagnostics.Process.get_ExitCode() at MongoDbUpgradeTo30.MongoDBManager.HandleMongoExit(String dbPath) at MongoDbUpgradeTo30.MongoDBManager.StartMongo(String mongoExeName, String dbPath, String port, Boolean withAuth, Boolean setMmapFlag) at MongoDbUpgradeTo30.Migrator.StartNewMongo() at MongoDbUpgradeTo30.Migrator.PerformMigration() at System.Threading.Tasks.Task`1.InnerInvoke() at System.Threading.Tasks.Task.Execute()<---
After hitting "Continue" the installer freezes on the following migration window.
Eventually, to complete the upgrade, the user will click "Cancel".
While the server may still run on the MongoDB 3.0, this may cause unexpected behavior in the long term. Should you encounter this error, it is important to troubleshoot it and make sure that your MongoDB is able to successfully migrate.
Upgrading from a version < 2018.1 to a version ≥ 2018.1
If this error is encountered, the server itself will upgrade, but fail to restart the service.
To determine which troubleshooting steps to take, we first need to check if the migration was actually successful or not :
Is there a MongoDB_34 folder under %ProgramData%\Alteryx\Service\Persistence?
If there is a MongoDB_34 folder, check the migration.log file found under %ProgramData%\Alteryx\Service\Persistence\MongoDB_34 :
This section runs a Mongo dump out to the PreUpgrade folder specified in the migration utility. You should see that the databases get dumped out to bson files. Hopefully, we won't see any errors in there. Once the backup completes the MongoDB service is stopped and the .js script verifies the MongoDB is not responding.
We then start Mongo 3.4 server, and restore to the new MongoDB_34 directory from the previous backup that was just taken. Again, we should hope not to see any errors in here. Then, the createUsers.js re-creates all the user accounts for each database. The MongoDB is then shut down again, and the .js script verifies the service is down.
The new MongoDB is then started up again with Mongo 3.4, and we run getstats.js again, giving us a list of the collections and the count of the documents, similar to the first step.
If everything looks good up to this point, the migration has likely been successful.
Are the System Settings pointing out the new MongoDB folder (MongoDB_34)?
If everything looks good in the logs, but the service didn't start or something happened after this point, we should be able to manually change the persistence directory to point at the new MongoDB_34 directory, and in theory, the service should start up fine.
What version of Mongo is running after the attempt?
In the persistence directory of the target database, there's an "ASMongoDBVersion.bin" that seems to match up with the version of Mongo.
If the log contains all the information mentioned previously and the migration seems successful, but there’s an error starting the service:
Make sure that the Persistence folder is set to MongoDB_34 and not MongoDB.
Restart the service.
If the migration log doesn’t match the description above, run the following utility to give migration another attempt :