Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

Reply
Anonymous
Not applicable

Power Bi Gateway

Hi 

I am Ravi a consultant involved in power bi dev and support.We involved in a issue with client for on prem gateway.

This is the error i got wile triing to recover "Error updating the configuration" bcoz of "System TimeOut exception". This runs on Windows Server 2008 R2 .Following is the detailed error :

Failed to update gateway details. You may need to change the account the gateway runs under.
Error updating gateway configuration.

Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
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.UpdateGatewayConfiguration(UpdateGatewayConfigurationRequest request, Boolean copyKeyAsLegacy, Int32 maxRetries)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayClient.GatewayConfigurationClient.UpdateGatewayConfiguration(UpdateGatewayConfigurationRequest request, Boolean copyKeyAsLegacy, Int32 maxRetries)An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.CouldNotUpdateGatewayConfigurationException: Error updating gateway configuration. ----> System.ServiceModel.CommunicationException: The request operation did not complete within the allotted timeout of 00:00:10. The time allotted to this operation may have been a portion of a longer timeout. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 ----> System.TimeoutException: The request operation did not complete within the allotted timeout of 00:00:10. The time allotted to this operation may have been a portion of a longer timeout. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 ----> System.Net.WebException: The request was aborted: The request was canceled.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ServiceBus.ServiceBusClientWebSocket.<ConnectAsync>d__54.MoveNext()
--- End of inner ExceptionDetail stack trace ---
at Microsoft.ServiceBus.ServiceBusClientWebSocket.<ConnectAsync>d__54.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ServiceBus.Common.TaskHelpers.EndAsyncResult(IAsyncResult asyncResult)
at Microsoft.ServiceBus.WebSocketConnectAsyncResult.<GetAsyncSteps>b__19_1(WebSocketConnectAsyncResult thisPtr, IAsyncResult r)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
--- End of inner ExceptionDetail stack trace ---
at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.CommunicationObject.EndOpen(IAsyncResult result)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.ServiceModel.ServiceHostController.<ExecuteRunnerIterationAsync>d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.ServiceModel.ServiceHostController.<StartRunnerAsync>d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.ServiceModel.ServiceHostController.StopHandle.<StartRunnerAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayServiceHost.GatewayServiceHost.<UpdateConfigurationImplAsync>d__41.MoveNext()
--- End of inner ExceptionDetail stack trace ---
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayServiceHost.GatewayServiceHost.<UpdateConfigurationImplAsync>d__41.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.PowerBI.DataMovement.Pipeline.Common.TaskUtils.ExtendedWait(Task task, TimeSpan timeout)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayServiceHost.GatewayServiceHost.UpdateConfiguration(GatewayConfiguration configuration, Boolean copyKeyAsLegacy, Int32 maxRetries)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayPipelineTelemetry.PipelineTelemetryService.ExecuteInActivity(PipelineActivityType pipelineActivityType, Action action)
at SyncInvokeUpdateGatewayConfiguration(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

3 REPLIES 3
nickyvv
Community Champion
Community Champion

While that might be true, it is probably not supported. And I doubt you will get official support from Microsoft if you do not meet the minimum requirements.

My suggestion would be to upgrade to at least Win Server 2012 R2, update to the latest version of the gateway and try again.



Did I answer your question? Mark my post as a solution!

Blog: nickyvv.com | @NickyvV


nickyvv
Community Champion
Community Champion

Hi @Anonymous,

 

Please have a look at the Minimum requirements: Windows Server 2012 R2 is required, instead of Win Server 2008.



Did I answer your question? Mark my post as a solution!

Blog: nickyvv.com | @NickyvV


Anonymous
Not applicable

It is true but for 1 year it has been working in windows server 2008 r2 because i am one who managed this gateway from start only for past 1 week it is making this problem.

This list is it upadated minimum requirment.  

Helpful resources

Announcements
LearnSurvey

Fabric certifications survey

Certification feedback opportunity for the community.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors