Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago
Solved

On premse gateway error

Does anyone have an idea what could be causing these errors?

 

1. Failed to create gateway. Please try again.

Request error: Id: '9aedf2f8-fba1-4bae-ad59-843e1b5933e4', Status code: 'Forbidden', Timestamp: '11/13/2017 04:32:32 +00:00', ErrorCode: 'TokenExpired', Detail: ''

 

2. Gateway service health check failed.

Below is the stack trace:

Microsoft.PowerBI.DataMovement.Pipeline.GatewayClient.GatewayConfigurationClientException: Error getting Gateway service health data. ---> System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

 

 

  • Anonymous

     

    Please check your firewall or proxy blocks connection following this document.

     

    You can also try to force the gateway to communicate with Azure Service Bus using HTTPS instead of direct TCP. You will need to modify the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file. Change the value from AutoDetect to Https. This file is located, by default, at C:\Program Files\On-premises data gateway.

     

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

     

    Best Regards,
    Herbert

2 Replies

  • v-haibl-msft's avatar
    v-haibl-msft
    Microsoft Employee

    Anonymous

     

    Please check your firewall or proxy blocks connection following this document.

     

    You can also try to force the gateway to communicate with Azure Service Bus using HTTPS instead of direct TCP. You will need to modify the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file. Change the value from AutoDetect to Https. This file is located, by default, at C:\Program Files\On-premises data gateway.

     

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

     

    Best Regards,
    Herbert

  • Anonymous's avatar
    Anonymous
    Not applicable

    Thanks for all your comments gentlemen. It was the firewall blocking some of the ports and domains. It's all good now.