On prem gateway fails to start due to log on error.

[MassimoB]

On prem gateway fails to start due to log on error 1069. This happened after a server restart (server 2022). Has anyone run into this before? Nothing i do gets this service to start. Logs attached.

Below is the stack trace:
Microsoft.PowerBI.DataMovement.Pipeline.GatewayClient.GatewayConfigurationClientException: Error getting Gateway service health data.
Exception message: Could not connect to net.tcp://127.0.0.1:45375/powerbi/gatewayconfiguration/service. The connection attempt lasted for a time span of 00:00:02.0428338. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:45375.  ---> System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://127.0.0.1:45375/powerbi/gatewayconfiguration/service. The connection attempt lasted for a time span of 00:00:02.0428338. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:45375.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:45375
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   --- End of inner exception stack trace ---

Server stack trace: 
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   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.ConfigurationContracts.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()

[rajendraongole1 · Accepted solution]

Hi @MassimoB -you can try reinstalling the On-Premises Data Gateway. Before doing so, make sure to back up your gateway recovery key to restore your configuration afterward.

These steps should help narrow down the issue. The problem appears to be with the service's ability to log on, which could be due to expired credentials, misconfiguration, or network connectivity issues.

Try the below workaround:

Go to Services (services.msc) on the server and find the On-premises data gateway service.>>Right-click on it, select Properties, and navigate to the Log On tab.>>Verify that the account and password are correct. If the password has changed, update it here.>>Then, restart the service.

Hope this helps.

[Wikkleyn_81 · Accepted solution]

Hi @MassimoB Yes I do get this error regularly. On the Gateway server, go to Services and the On-premises data gateway service. Right click and select Properties and navigate to the Log On tab. If you have the default NT SERVICE\PBIEgwService account. Delete the password and click OK and Ok for that pop-up message.

Close the On-premises data gateway service Properties and start the service. 

I resolved this issue by using an AD Service account for the Log On.

[rajendraongole1 · Accepted solution]

Hi @MassimoB -you can try reinstalling the On-Premises Data Gateway. Before doing so, make sure to back up your gateway recovery key to restore your configuration afterward.

These steps should help narrow down the issue. The problem appears to be with the service's ability to log on, which could be due to expired credentials, misconfiguration, or network connectivity issues.

Try the below workaround:

Go to Services (services.msc) on the server and find the On-premises data gateway service.>>Right-click on it, select Properties, and navigate to the Log On tab.>>Verify that the account and password are correct. If the password has changed, update it here.>>Then, restart the service.

Hope this helps.