enterprise data gateway configuration error

[Peeches123]

hi

i've been trying to configure the enterprise gateway and i keep getting errors, some i have resolved but i'm stuck on this one.

i would really appreciate if someone could give me a step by step breakdown on 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.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()

[Peeches123]

i've tried some of the solutions i got from the forums.

 when i set my log on to this "NT SERVICE\PBIEgwService" i get a temp user error but when i change to local system account, i get the above error.

Note: the server i'm trying to configure the gateway on is not on a domain

please for any solution i get, can i have a step by step walk through

[v-caliao-msft]

@Peeches123,

The gateway creates an outbound connection to Azure Service Bus. It communicates on outbound ports: TCP 443 (default), 5671, 5672, 9350 thru 9354. Please try to open outbound rule for those ports on your server which you want to configure data gateway.

Regards,

Charlie Liao