Error on on-premise Data Gateway

[Kamaizziati]

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.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.GenerateAsymmetricKey()
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayClient.GatewayConfigurationClient.GenerateAsymmetricKey()

[GIS_powerBI]

I was recently upgraded to Windows 10 and my domain changed for my log in. I am trying to recover my gateway and it is telling me my 'key is not valid for the state'

Any idea on how to fix this?

[Kamaizziati]

Hi @GIS_powerBI,

It is your proble already solved?

Did you put the name of your PC correct? or do you shutdown the PC because on one premisse gateway need 24 hour PC on.

Thanks

[GIS_powerBI]

turns out with the windows 10 upgrade there was a domain change. Only way to resolve it was to get a Windows 7 computer again and put 64 bit office and BI on there.

[v-ljerr-msft · Accepted solution]

Hi @Kamaizziati,

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

---

---

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

[Kamaizziati]

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()