![]() If you are recovering to a Sandbox Server for testing, use HTTP for testing.Ultimate Multi Tool aka UMT is a dongle-based Android repair toolkit that allows you to refresh firmware, unlock pattern, reset screen lock, FRP bypass, IMEI repair, and any Android smartphone based on Qualcomm, MTK, SPD can be repaired All questions. (Coming soon) Contact your Account Executive or Customer Support. See Server Upgrade Python Tool Environment Checklist.ĭo you have a multi-node environment or user-managed Mongo? Re-install any Python packages that workflows had installed. Restore User-Based and User In-DB Connection AliasesĬ:\Users\\AppData\Roaming\Alteryx\Engine\UserConnections.xmlĬ:\Users\\AppData\Roaming\Alteryx\Engine\UserAlias.xmlĬopy Connector folders from your original server toĬontact Customer Support to enable Connectors on your new Server. %ProgramData%\Alteryx\Engine\SystemConnections.xml %ProgramData%\Alteryx\Engine\SystemAlias.xml Restore System-based and In-DB Connection Aliases In more secure environments, configure required Run As user permissions.Įnsure all credentials used to run workflows (Run As, Service Log On, or credential set when saving the workflow) have proper sufficient access, configure required run user permissions. Īdvanced issues that may not apply to your recovery: Windows Services app > right-click AlteryxService > Properties > Log OnĪdd same-version drivers and same-name System DSNs to match original Server. One or more times until you exit MongoDB and return to a normal command prompt.ĭid you have a Service Log On User on the original Server? In the original command prompt, enter the keyboard command Quit Mongo Command Line and Command Prompt 2 ![]() ![]() On success you should see: " writeResult()", where N is a number between 0 and 3. Mongo mongodb://localhost:27018/AlteryxGallery -u user -p CCEC***33C0 Mongo mongodb://SERVER:PORT/AlteryxGallery -u user -p NON_ADMIN_MONGO_PASSWORD Open a SECOND Command Prompt As Administrator and navigate to the Alteryx\bin folder, enter the commands below (adjust based on your install location).Įnter the command and copy your NON_ADMIN_MONGO_PASSWORD to Notepad If you close the window from step 3.5, none of the subsequent steps will work. ![]() Mongod ––dbpath "%ProgramData%\Alteryx\Service\Persistence\Mongo_Restore" ––auth ––port 27018 Mongod ––dbpath "MONGO_RESTORE_FOLDER" ––auth ––port 27018 Open mongoRestore.log and follow these steps: To do so, review the mongoRestore.log file in the MongoDB folder where the data was restored. This is a necessary step as a restore failure will not be reported in the previous step and can lead to missing data on your Server. In either case, review mongoRestore.log as described below to ensure the restore was successful.ĪlteryxService.exe emongorestore="MONGO_BACKUP_FOLDER","MONGO_RESTORE_FOLDER",10ĪlteryxService.exe emongorestore="D:\db_bkp","%ProgramData%\Alteryx\Service\Persistence\Mongo_Restore",10 Leaving off the ,10 might lead to faster restores. This reduces the chance of out-of-memory errors but might increase the time to restore. The final parameter, ,10, ensures lower memory usage by MongoDB during the restore. Restore the Mongo database from the backup folder to a new restore folder. Step 3 assumes you are in an Administrator command line in the \Alteryx\bin folder.Ĭopy the Mongo backup from the original server to a MONGO_BACKUP folder on your new Server. Please note that this requires the Alteryx Service to be running on your original Server Controller node and your new Server will need to be able to access it over the network. The steps in Encryption Key Transfer Process will allow you to transfer the encryption key from your existing controller to your new one. AlteryxService.exe setsmtppassword=PASSWORD If you had filled in Alteryx System Settings > Server UI > SMTP > Password (even if the SMTP checkbox was unchecked), enter the following command, otherwise skip this step. AlteryxService.exe setexecuteuser=NAME,DOMAIN,PASSWORD If you had a Run As User on the original Server, enter the following command, otherwise skip this step. You can leave RuntimeSettings.xml open in a text editor as you make further changes in step 3. It is easiest to copy the tags as well to ensure that the entire value between them is copied from the original RuntimeSettings.xml file. If so, it should be replaced with the value from the original RuntimeSettings.xml file. The value might have changed when the controller token was reset in step 2.6. To correct this, see the previous step to ensure the value was removed from between the tags. Version 2021.3+ can error on this step with: "Set server secret failed: Error in CryptImportKey(3): Bad Data. Enter the command using your original server Controller TokenĪlteryxService.exe setserversecret=CONTROLLER_TOKEN_FROM_ORIGINAL_SERVER
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |