locked
Unable to install ATA Gateway - Failed to connect to the console RRS feed

  • Question

  • Hi there,

    I am unable to install Microsoft ATA Gateway onto a Windows Server 2012r2 core server. The machine has been setup as a domain controller. Previously the gateway was installed on this machine but suddenly stopped working, I have been unable to start the ATA service despite restarting the machine so decided to uninstall the program.

    I receive the following error when trying to re-install "Failed to connect to the Console, https://xx.xxx.x.x If the IP address or certificate used by the console were recently updated, download the latest gateway package. 

    I have tried installing the program by selecting the 'Create self-signed certificate' check box as well as selecting both of the certificates available to me in the 'Gateway Service SSL Certificate' box.

    I have tried selecting a different certificate in the ATA Center, downloading the Gateway setup again and re-installing - no change.

    I have checked the mongodb using robomongo and confirmed the 'ServerCertificateThumbprint' is the same as the certificate in the ATA center. 

    I can successfully ping the ATA server from the problem machine and the account I am using has sufficient permissions to do what I need to do.

    Is there anything else I can look at to try and resolve this issue? I don't really want to reinstall the OS if I can help it.

    Thanks


    • Edited by Mikebiacsi Thursday, June 8, 2017 3:14 PM
    Thursday, June 8, 2017 3:11 PM

Answers

  • Hi all, just to update this ticket.

    I have installed the following updates on the ATA center server:

    KB4010105 - Update for System Center Endpoint Protection 2012 Client

    KB4017094 - Security Update for Microsoft Silverlight

    KB890830 - Windows Malicious Software Removal Tool

    KB3150513 - 2017-06 Update for Windows Server 2016 for x64-based Systems

    I then restarted the ATA center, downloaded the gateway setup file and ran this on the DC. The installer ran fine and the new Gateway is showing up in the ATA center web interface as expected.

    Not sure if it act of restarting the ATA Center or installing the updates solved the issue, but everything is working now.

    Kind Regards

    Mike

    • Marked as answer by Mikebiacsi Monday, June 12, 2017 2:17 PM
    Monday, June 12, 2017 2:17 PM

All replies

  • Hello,

    Based on the error message, it's obvious that ATA Lightweight Gateway can't communicate with ATA Center correctly.

    Just for easy, I would recommend to turn off firewall on both ATA Center and ATA Lightweight Gateway, meanwhile, please make sure there is no physical firewall sits between ATA Center and ATA Lightweight Gateway.

    In addition, please make sure the proxy server is not configured on ATA Lightweight Gateway. You can check the configuration from IE settings -> Internet Options -> Connections -> LAN Settings -> Proxy server.


    Best regards,
    Andy Liu

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 9, 2017 9:01 AM
  • Hi Andy,

    Thank you for replying. I can confirm that Windows Firewall is disabled on both the ATA center machine and the server I wish to install ATA gateway onto. There is also no physical firewall sitting between them.

    I have also checked the proxy settings on the server I wish to install ATA gateway onto, no proxy has been set.

    Kind Regards

    Mike


    • Edited by Mikebiacsi Friday, June 9, 2017 9:36 AM
    Friday, June 9, 2017 9:35 AM
  • An update,

    I have just tried to install the gateway onto a different machine that has never had ATA gateway installed, this failed with the same error leading me to believe the issue is with the ATA Center machine rather than the gateway server.

    Mike

    Friday, June 9, 2017 10:36 AM
  • Hello Mike,

    First, please make sure the service for ATA Center is up and running on ATA Center server. You can check that from Services MMC snap-in.

    In addition, please make sure there is no other process, such as IIS, Apache, which may listen on TCP port 443. If so, it will conflict with ATA Center, which also need to listen on port 443.

    You can open CMD on ATA Center, and then run the following command to find out the PID for the process, which is listen on TCP 443. And then, you can find out the process name from task manager by using the PID.

    netstat -nao | find "443"

    Best regards,

    Andy Liu


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, June 12, 2017 6:26 AM
  • Hi Andy,

    Thank you for the reply, I can confirm that the service is running fine and that no other process is listening on port 443. Apologies, I should have said this in my original post, but I do have several other servers that have ATA gateway installed, and they all communicate with the ATA center just fine.

    Kind Regards

    Mike


    • Edited by Mikebiacsi Monday, June 12, 2017 8:47 AM
    Monday, June 12, 2017 8:44 AM
  • Hello Mike,

    Could you please check the tcp connection on port 443 between ATA Center and ATA Gateway by running the following command on ATA Gateway.

    telnet <IP or FQDN of ATA Center Server> 443

    In addition, you should review the log file at C:\Users\Administrator\AppData\Local\Temp, from where you can get more details about the error.

    Finally, if the ATA Gateway is installed on Windows Server 2012 R2 Core, the following update should be installed: KB3000850

    Best regards,

    Andy Liu

     


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, June 12, 2017 9:29 AM
  • Hi all, just to update this ticket.

    I have installed the following updates on the ATA center server:

    KB4010105 - Update for System Center Endpoint Protection 2012 Client

    KB4017094 - Security Update for Microsoft Silverlight

    KB890830 - Windows Malicious Software Removal Tool

    KB3150513 - 2017-06 Update for Windows Server 2016 for x64-based Systems

    I then restarted the ATA center, downloaded the gateway setup file and ran this on the DC. The installer ran fine and the new Gateway is showing up in the ATA center web interface as expected.

    Not sure if it act of restarting the ATA Center or installing the updates solved the issue, but everything is working now.

    Kind Regards

    Mike

    • Marked as answer by Mikebiacsi Monday, June 12, 2017 2:17 PM
    Monday, June 12, 2017 2:17 PM