Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. Qt VS Addin - TCP port 12005
Forum Updated to NodeBB v4.3 + New Features

Qt VS Addin - TCP port 12005

Scheduled Pinned Locked Moved Qt Creator and other tools
3 Posts 3 Posters 4.2k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • O Offline
    O Offline
    Orione
    wrote on last edited by
    #1

    Hello!
    I use Visual Studio 2010 Pro with Qt Add-in for Qt 4.8.5
    First time I start VS2010 I get following error message:

    Qt Visual Studio Add-in

    The following error occured:
    Could not connect to Appwrapper. Please make sure that TCP port 12005 is not blocked.

    This happens only the first time I start VS2010 every time I switch on my laptop.
    My laptop firewall is disabled so TCP port 12005 should be not blocked.
    My company firewall is probably blocking this port, this could explain the message.

    Why is Qt trying to connect to this port?
    Can this be disabled?
    Thanks for any information and/or hint.

    1 Reply Last reply
    0
    • dheerendraD Offline
      dheerendraD Offline
      dheerendra
      Qt Champions 2022
      wrote on last edited by
      #2

      Do you have two Qt versions running on your box ? Or 12005 port is used by some other component in your box.

      Dheerendra
      @Community Service
      Certified Qt Specialist
      http://www.pthinks.com

      1 Reply Last reply
      0
      • M Offline
        M Offline
        msue
        wrote on last edited by
        #3

        I am using VS 2013 and I got a similar message after my last combined WINDOWS and VS update. The only difference: it complained about port 12015. The message appeared once and never again until now. There were no visible problems, so far: build and debugging work just fine.

        Maybe the WINDOWS update closed some ports (as a security feature) and the VS Add-In does not really need them in what I am using of it.

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved