Forum Discussion

ChrisOnesBroken's avatar
ChrisOnesBroken
Icon for Helper I rankHelper I
9 years ago

On-Premises data gateway - the remote certificate is invalid according to the validation procedure

I've been having problems configuring On-Premises data gateway.  The problems seem to be around certificates.  When I first tried installing from the package which retrieves installation files from a...
Need Help
ChrisOnesBroken's avatar
ChrisOnesBroken
Icon for Helper I rankHelper I
9 years ago

Thanks Anonymous,

 

I've run the powershell in the first link, and it times out;

PS H:\> Test-NetConnection -ComputerName watchdog.servicebus.windows.net -Port 9350
WARNING: Ping to watchdog.servicebus.windows.net failed -- Status: TimedOut


ComputerName           : watchdog.servicebus.windows.net
RemoteAddress          : 70.37.104.240
RemotePort             : 9350
InterfaceAlias         : Team1
SourceAddress          : [Redacted]
PingSucceeded          : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded       : True

 

However the firewall is off on the server, and server has been configured on the corporate firewall to access "any destination on TCP 443 , 5671, 5672 and 9350-9354"

 

I'm logged on as myself and have full access to do anything needed, and I've tried setting the 'On-Premises data gateway services' service to run as an AD account (pbi_DataGatewaySA) which has access to the internet etc.

 

EDIT: Further to the above, I've spoken to our networking team and they're surprised that I've been asked to ping the address becuase the documentation doesn't call for it (https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-onprem/#ports).  They've added ping/icmp to the policy, but it still doesn't respond using the powershell.

  • Anonymous's avatar
    Anonymous
    Not applicable
    9 years ago

    Hi ChrisOnesBroken,

    The Test-NetConnection may not work if your server don’t have direct Internet connections and all connections must go through your proxy server.

    Modify the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file by changing the value from AutoDetect to Https. Also configure Proxy following the guide in this article and check if the issue still occurs.

    Thanks,
    Lydia Zhang

  • ChrisOnesBroken's avatar
    ChrisOnesBroken
    Icon for Helper I rankHelper I
    9 years ago

    Anonymous

    I have amended the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file to;

     

          <setting name="ServiceBusSystemConnectivityModeString" serializeAs="String">
            <value>Https</value>
          </setting>

     

    As suggested.

     

    The enterprisegatewayconfigurator.exe.config is already configured with the value;

     

      <system.net>
        <defaultProxy useDefaultCredentials="true" />
      </system.net>

     

    ...as the article here;

     

    https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-proxy/

     

    ...suggests.

     

    The error is still occuring, and failing to configure.