locked
Cannot install ATA 1.7 : Console IP address is being used. Install button deactivated. RRS feed

  • Question

  • While attempting to deploy ATA 1.7.5757 on a 2012 R2 server, the "Install" button is grayed and a red exclamation mark close to Console IP Address pop-up with: Console IP address is being used.

    The server is already hosting 2 IIS sites bound to address 1 ports 80 & 443.
    Address 2 has been created on purpose and is unused by any application. Confirmed by Netstat, this IP is not listening to any port used by the Center Service. The two IIS webs are configured to listen only on address 1.

    I select Address 1 port 543 for the Center Service IP and Address 2 for the Console IP address.
    The message will remain whatever available IP and port is selected: Console IP address is being used.

    Thanks in advance for help.


    /Patrice

    Friday, December 23, 2016 7:47 AM

Answers

  • Hi Gershon,

    thanks to take care.

    I created Address2 on purpose so that's exactly my goal.

    In fact, I could telnet Address2 port 80 despite no site was bound on IIS.

    Solution was to restrict IIS from listening on all IPs. I ran

    netsh http add iplisten ipaddress=Address1

    then can install successfully on Address2.

    HNY

    Cheers


    /Patrice

    • Marked as answer by PmNet-CH-FR Tuesday, January 3, 2017 7:04 AM
    Tuesday, January 3, 2017 7:03 AM

All replies

  • Hi Patrice, 

    What happens if you select Address2 for both the ATA Center Server and Console IP addresses and change the port for the ATA Center Service to a different port such as 4433? 

    HTH

    ATA Team


    Gershon Levitz [MSFT]

    Wednesday, December 28, 2016 9:59 AM
  • Hi Gershon,

    thanks to take care.

    I created Address2 on purpose so that's exactly my goal.

    In fact, I could telnet Address2 port 80 despite no site was bound on IIS.

    Solution was to restrict IIS from listening on all IPs. I ran

    netsh http add iplisten ipaddress=Address1

    then can install successfully on Address2.

    HNY

    Cheers


    /Patrice

    • Marked as answer by PmNet-CH-FR Tuesday, January 3, 2017 7:04 AM
    Tuesday, January 3, 2017 7:03 AM
  • This installation procedure provides instructions for performing a fresh installation of ATA 1.7. For information on updating an existing ATA deployment from an earlier version, see the ATA migration guide for version 1.7.
    • Proposed as answer by 腎臓移植 Tuesday, January 3, 2017 7:13 AM
    • Unproposed as answer by 腎臓移植 Tuesday, January 3, 2017 7:13 AM
    • Proposed as answer by 腎臓移植 Tuesday, January 3, 2017 7:15 AM
    • Unproposed as answer by PmNet-CH-FR Tuesday, January 3, 2017 7:17 AM
    Tuesday, January 3, 2017 7:12 AM
  • I know this is a little late to reply to this post. but I ran in the same problem when installing MsATA.

    solution is simple.. you may install with any IP preferably with new IP addresses for proper analytics...

    Solution:

    1 - Stop IIS- got to IIS server manager and stop server

    2- install MsATA -- no problem then...

    Thanks

    G.


    G-EDGE

    • Proposed as answer by G-EDGE Saturday, August 12, 2017 3:19 AM
    Saturday, August 12, 2017 3:19 AM
  • Thanks that helped.

    I think there is room for improvement in the ATA install. It installs IIS, so why does it not limit the IP address it self, or stop the server and restart it?

    Thursday, April 19, 2018 9:41 AM
  • Hi Pieter, 

    This should no longer be an issue as ATA no longer uses IIS. 

    Thanks

    Gershon


    Gershon Levitz [MSFT]

    Sunday, April 22, 2018 10:22 AM
  • Thanks, it did in my older version, and I updated it to 1.8 afterwards, but had to get it running first. Good to hear it is fixed.

    Pieter

    Sunday, April 22, 2018 10:34 AM