alteryx server Knowledge Base

Issue:  Alteryx Service will not Start and LastStartUpError.txt contains "No suitable servers found: `serverSelectionTimeoutMS` expired: [connection refused calling ismaster on 'localhost:27018']: generic server error" code: <mongodb:13053>   By Default, the LastStartupError text file can be found at C:\ProgramData\Alteryx\Service     Error Code: No suitable servers found: `serverSelectionTimeoutMS` expired: [connection refused calling ismaster on 'localhost:27018']: generic server error" code: <mongodb:13053>   Environment   Product - Alteryx Server Version(s) 11.8+ Diagnosis   Check the mongod.lock file is > 0KB in size   Identify where the MongoDB is installed from the Alteryx System Settings under Controller > Persistence > Data Folder Navigate to that folder in Windows File Explorer Confirm the size of mongod.lock Cause   Alteryx Server had an unclean shutdown.   Solution   If the mongod.lock file does have data inside (1KB usually), we recommend to first  backup your persistence database  (in case of corruption) before proceeding. Alternatively, in step 1 below, rename the file instead of deleting if you do not have a backup.   Delete/rename the mongod.lock file e.g: mongod.lock renames to mongod.old Right-click on a blank space in the window and select New > Text Document Alternatively, if you do not have this option you can create a new text file in Notepad and save the file into this directory. If you run into issues saving into this directory directly, you can save the file to your Desktop and then move into the folder where MongoDB is installed Name the document mongod.lock Make sure that File Extensions are visible, otherwise this file will actually be mongod.lock.txt Open a Windows Command Prompt and navigate to the \Alteryx\bin directory e.g.  cd "\Program files\Alteryx\bin"​ Start up the MongoDB service just to make sure everything is clean: mongod --dbpath "folder path from system settings" --auth --port 27018   With an unclean shutdown it may take a few minutes to reallocate the data.  Look for a line that says "Waiting for connections on port 27018"  When it appears, hit CTRL+C on your keyboard to shutdown the service. Start up the AlteryxService.  This can be done via: Command Prompt with:  sc start AlteryxService​ From the Services window   Next Steps if the Mongod.Lock file was empty (0KB)   Open a Windows Command Prompt and navigate to the \Alteryx\bin directory e.g.  cd "\Program files\Alteryx\bin" Run the AlteryxService in test mode to identify the actual error  AlteryxService test If you are unable to easily identify what is causing the error, send the service log files (path found in System Settings->Controller->General) to Alteryx Support    

This is a very common error that can occur if the AlteryxService shuts down unexpectedly. Most commonly the error is caused by MongoDB not shutting down properly and the lock file does not get released. This prevents MongoDB from starting the next time you try to start the AlteryxService and returns an error message.

This is most likely caused by a licensing error or an issue that can arise from the AlteryxService shutting down unexpectedly .  It can also be due to an incorrect or expired license, or a correct license not being installed with admin rights, or in the case of Runtime-only users (this type of license has been phased out for all but a few legacy clients).

Receiving the error below when attempting to schedule a module?   “An error occurred in the scheduler. Server Error: 500 Server Error GetExpectedValue: Expected “Container” but got “Sid” Incorrect type requested 1 actual 4”   Post v10.5 release, your Alteryx Server and working environment must be of the same version in order to enjoy the upgrades of the release and still be able to commit scheduled workflows correctly. When the versions of your worker and server do not match, you’ll receive the error above. While our recommendation is to be using the most up to date release, you can always upgrade or revert your designer version either at our Downloads page (current version) or the Previous Releases webpage. To check on the version you’re using, you can navigate in the Designer to the Help >> About menu.

Adding files to Gallery App   Sometimes when uploading Apps or Macros the Gallery you may receive an error with a file extension referencing externals_...... You may also  select the workflow assets and the files are checked, but they are not loading to the gallery.   This often means the file cannot be found on the server side and as a result needs to be added to the workflow package and uploaded to with the app or macro.   Attaching the workflow assets can often be selected when exporting the workflow or adding them through the display asset management properties window within the input tool. Please see this Article for more information.   Similarly, you can also add assets within the events>>>Run command>>Assets tab.       If you add the assets through either of these methods when uploading to the Gallery, the server should be able to see the correct assets and execute without any externals errors.   Again if you are still experiencing any issues please reach out to Alteryx Support   Best,   Jordan Barker Client Services Support Engineer