Quickmap Data Download Manager Hangs

Posted on by

When starting Quickmap Data Download Manager, it hangs and gives this error:

Problem with Quickmap Data Download Manager

An error occurred while receiving the HTTP response to
http://localhost:9001/QDataDownloadAdminService. This
could be due to the service endpoint binding not using the
HTTP protocol. This could also be due to an HTTP request
context being aborted by the server (possibly due to the
service shutting down). See server logs for more details.

This is typically because there is another program that uses the same port. To discover what program may be using the port (port 9001), run the following in the command prompt:

netstat -a -b

Alternatively, use this PowerShell commandlet:

get-nettcpconnection -remoteport 9001 | select *,@{Name=”Process”;Expression={(Get-Process -Id $_.OwningProcess).ProcessName}}

If you get this message back in PowerShell, then a port conflict probably isn’t the issue (see below for other solutions):

get-nettcpconnection : No MSFT_NetTCPConnection objects found with property ‘RemotePort’ equal
to ‘9001’. Verify the value of the property and retry.
At line:1 char:1
+ get-nettcpconnection -remoteport 9001 | select *,@{Name=”Process”;Exp …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (9001:UInt16) [Get-NetTCPConnection], CimJobExcep
tion
+ FullyQualifiedErrorId : CmdletizationQuery_NotFound_RemotePort,Get-NetTCPConnection

Here’s a list of programs that are known to use the same port as Quickmap Data Download Manager:

  • Jumpstart (DPAgent.exe)
  • HP Protect Tools
  • TeamViewer (Some versions work alongside Quickmap, others don’t)

Addendum: It may be that you just need to reboot the computer. More solutions for the Quickmap Data Download Manager hanging are in the comments below.

Please like this page:

One thought on “Quickmap Data Download Manager Hangs”

  1. I recently had a customer who had installed Quickmap Data Download Manager (QDDM) on a computer, and the executable that manages the QDDM service was in a place that was backed up by Microsoft OneDrive. When the customer logged onto a different computer without the QDDM Service installed, he launch the executable that was in OneDrive (which had been synch’d from the other computer) and this displayed the QDDM user interface, but it hung because the Quickmap Data Download Manager had never been installed on that computer.

    Therefore, it’s worth checking that the Quickmap Data Download Manager has actually been installed on the computer if it’s hanging.