"Cannot connect to the Supervisor service" when starting PRTK

Created by: Brendan Bone
Created date:
Last Updated date:


When starting PRTK, you are told it can't connect to the Supervisor service (which connects over port 49190).



To determine what application or service is using port 49190:

  1. Open a Command Prompt
  2. Run the command netstat -ano | find ":49190"
  3. The right side of the window will list the PID of the process using port 49190
  4. Open Task Manager
  5. Open the Processes tab, and show processes from all users
  6. Go to View > Select Columns
  7. Check the box for "PID (Process Identifier)" and click OK
  8. Find the PID from step 3 to determine what is using port 49190, and end the process (as long as it is safe to do so)



Another application or service is using port 49190



  • You may reserve the ports used by PRTK/DNA from being used by some other applications by following the steps here.
  • If you have ElasticSearch, which requires a lot of internal ports, Windows may automatically assign ports in the 49000 range to ElasticSearch.  If this happens, you may stop ElasticSearch, open PRTK, the restart ElasticSearch and it will bind to a new port.  Following the steps here should prevent ElasticSearch from using those ports in the future.
  • If the conflicting service using port 49190 is necessary, you may change the ports used by PRTK by following the steps here.
Was this article helpful?
0 out of 1 found this helpful
Have more questions? Submit a request


  • Avatar
    Steffen Moorrees

    Wouldn't it be usefull to add these exceptions by default in the application installer ?
    It looks like i have this issue on every single processing workstation in my lab. So this doesn't look like an incidental bug anymore, but more a design issue?

  • Avatar
    Danny Tong

    +1 Steffen

  • Avatar
    Tyson Beall

    The PID didn't appear in my task manager and I had to use the command prompt to kill the task with
    C\:taskkill /f /PID (identified PID)

Powered by Zendesk