Welcome to the Alteryx Knowledge Base

Error: Alteryx Service fails to start after Server shutdown
user

Created/Edited - 3/18/2025 by Jessica Silveri | Alteryx

Description
After a previous shutdown of Server, the Alteryx Service will not start.
Issue
One of the following Alteryx Service start up errors may be observed:
No suitable servers found: `serverSelectionTimeoutMS` expired: [connection refused calling ismaster on 'localhost:27018']: generic server error" code: 
 
There was an error starting the Alteryx Service <Embedded Mongo Service failed to start in a timely fashion, exiting.>

The Alteryx Service start up errors can be found in the following locations on the Server machine:
  • The LastStartUpError.txt file in "C:\ProgramData\Alteryx\Service"
  • The latest Service log file in "\ProgramData\Alteryx\Service". Look for the latest entry with "AlteryxService_LogStartupError"
Environment
Alteryx Server
  • All versions
  • Embedded MongoDB
Cause
Alteryx Server had an unclean shutdown.
Resolution

Diagnosis

Check if the mongod.lock file is > 0KB in size.

  1. Identify where the MongoDB is installed from the Alteryx System Settings under Controller > Persistence > Data Folder
  2. Navigate to that folder in Windows File Explorer
  3. Confirm the size of mongod.lock

 

Art edit 1.png

 

If the mongod.lock file is > 0kb in size, see Solution A below.
If the mongod.lock file is = 0kb in size, see Solution B below.


Solution A


If the mongod.lock file does have data inside (1KB usually), we recommend you first backup your persistence database before proceeding. Alternatively, in step 1 below, rename the file instead of deleting it if you do not have a backup.

  1. Delete/rename the mongod.lock file
    1. For example, rename mongod.lock to mongod.old
  2. Right-click on a blank space in the window and select New > Text Document
    1. 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 it into the folder where MongoDB is installed. 
  3. Name the document mongod.lock

Note: Make sure that File Extensions are visible, otherwise this file will actually be mongod.lock.txt

 

  1. Open a Windows Command Prompt and navigate to the Alteryx bin directory:
cd "[Drive:]\Program files\Alteryx\bin"
  1. Start the MongoDB just to make sure everything is clean:
mongod --dbpath [MongoDB folder path] --auth --port 27018

 

  1. 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 shut down the service.
  2. Start the AlteryxService. This can be done via either option:
    • Command Prompt with:
sc start AlteryxService
  • From the Services window

 

Solution B

 

  1. Open a Windows Command Prompt and navigate to the Alteryx bin directory, e.g.:
cd "[Drive:]\Program files\Alteryx\bin"
 
  1. Run the AlteryxService in test mode to identify the actual error

 

AlteryxService test
  1. If you are unable to easily identify what is causing the error, you can open a Support case on MyAlteryx and attach the Service and Server UI (Gallery) logs that match the time that the error happened to the case. For more information on where to find the logs, see Configure and Use Server Logs .
Additional Information
Was this article helpful?