Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago
Solved

Error on on-premise Data Gateway

Hi,   I got error while update/migrate the gateway. Below is the error. How to solve it? Error generating an asymmetric key. The communication object, System.ServiceModel.Channels.ServiceCh...
Need Help
  • v-ljerr-msft's avatar
    v-ljerr-msft
    8 years ago

    Hi Anonymous,

     

    Here is a similar thread in which a workaround is mentioned. Could you go to check if it works in your scenario? :smileyhappy:

    Solution:

     

    Change the logon user for Service "On-premises data gateway service" (PBIEgwService) to "Local System Account".

     

    1. RUN services.msc
    2. Search "Power BI Gateway - Enterprise Service" in list of services, and click
    3. In TAB "Log On" change to "Local System Account"
    4. Restart "Power BI Gateway" Service

     

    Regards

v-ljerr-msft's avatar
v-ljerr-msft
Icon for Microsoft Employee rankMicrosoft Employee
8 years ago

Hi Anonymous,

 

Here is a similar thread in which a workaround is mentioned. Could you go to check if it works in your scenario? :smileyhappy:

Solution:

 

Change the logon user for Service "On-premises data gateway service" (PBIEgwService) to "Local System Account".

 

1. RUN services.msc
2. Search "Power BI Gateway - Enterprise Service" in list of services, and click
3. In TAB "Log On" change to "Local System Account"
4. Restart "Power BI Gateway" Service

 

Regards

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Hi v-ljerr-msft,

 

I already try that step but i got another error. Below is my error.

 

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.

Server stack trace:
at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()
at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.PowerBI.DataMovement.Pipeline.InternalContracts.IGatewayConfigurationService.GetServiceHealth()
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayClient.GatewayConfigurationClient.GetServiceHealth()
--- End of inner exception stack trace ---
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayClient.GatewayConfigurationClient.GetServiceHealth()
at Microsoft.PowerBI.DataMovement.GatewayCommon.Checks.GatewayServiceCheck.RunCheck()