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

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Issue: Scheduled Refresh Intermittent Issue

Hi,

 

We are experiencing issues with our scheduled refreshes on an intermitment basis, we have around 10 reports setup on different refresh schedules however over the past few weeks we have noticed that at certain times the refreshes have failed on some ocassions. Below is a list of some of the failed refreshed dates and times upto yesterday but still ongoing today. It is different reports and sometimes different times.

 

I have confirmed with our IT support team that the gateway used in the scheduled refreshes are active, the server has plenty of memory available and cores, there is no peaks in traffic through that particular server and the internet connection is of a very high quality and very stable,

 

The Error message is blank inside the notification email which i noticed is a known bug at the moment, when i check on the dataset for the failed refresh we see an error message of "Unable to connect to the data source undefined". The datasets being used are very small and the queries are hitting high performance SQL server boxes which again i have confirmed have plenty of resources available to them when the queries have failed.

 

DateTimeDataset Name
09/03/201909:44QA Calls
09/03/201912:16Timesheet per Category
09/03/201912:16Software Engineering - Non Chargeable
09/03/201917:11Timesheet per Category
09/03/201917:11Software Engineering - Non Chargeable
10/03/201909:40QA Calls
10/03/201910:18ServiceBuildDashboard_DB_CONNECTED
10/03/201911:13ServiceBuildDashboard_DB_CONNECTED
10/03/201912:18Employees Weekly Hours
10/03/201917:12Software Engineering - Non Chargeable
11/03/201909:42QA Calls
11/03/201917:11Software Engineering - Non Chargeable
12/03/201913:12QA Calls
12/03/201914:01Tickets Analysis
12/03/201914:12Tickets Analysis
12/03/201914:43Employees Weekly Hours
12/03/201915:18Timesheet per Category
12/03/201917:17Tickets Analysis
12/03/201917:25QA Calls
12/03/201918:24Timesheet per Category
13/03/201909:44QA Calls
13/03/201910:17ServiceBuildDashboard_DB_CONNECTED
13/03/201911:17ServiceBuildDashboard_DB_CONNECTED

 

Please can you look into the issue and let me know if any more information is required.

Status: Needs Info
Comments
v-yuezhe-msft
Employee

@GordonDoggett ,

What is the version of your gateway?Could you please share gateway log here.


Regards,
Lydia

v-yuezhe-msft
Employee
Status changed to: Needs Info
 
GordonDoggett
Regular Visitor

Hi @v-yuezhe-msft  how can we attach the log files to this post?  We have recently upgraded the gateway last week to 3000.2.47 (March 2019). Below is some of the error logs when we have seen this error.

 

As explains the reports havent been changed and sometimes the scheduled refresh works as expected.

 

DM.EnterpriseGateway Error: 0 : 2019-03-27T12:02:09.0905550Z DM.EnterpriseGateway ce9183be-8ff2-4a30-bd14-77f2ac902a86 8b385d54-a2e4-4f60-9194-7f97285ab566 MGCC 22af9e5c-5f44-4d03-9a5f-f781d74a5368 f36ed2fb-5ed0-4418-a633-a724e68e42a4 f36ed2fb-5ed0-4418-a633-a724e68e42a4 D4B33C03 [DM.Pipeline.Diagnostics] Exception object created [IsBenign=True]: Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.FailedToImpersonateUserException: Error logging on user '<pi>ase\shehaby</pi>'.; ErrorShortName: FailedToImpersonateUserException/Win32Exception[HResult=-2147467259,ErrorCode=-2147467259,NativeErrorCode=1326]
DM.EnterpriseGateway Error: 0 : 2019-03-27T12:02:09.1061695Z DM.EnterpriseGateway ce9183be-8ff2-4a30-bd14-77f2ac902a86 8b385d54-a2e4-4f60-9194-7f97285ab566 MGCC 22af9e5c-5f44-4d03-9a5f-f781d74a5368 f36ed2fb-5ed0-4418-a633-a724e68e42a4 f36ed2fb-5ed0-4418-a633-a724e68e42a4 8056B09F [DM.Pipeline.Diagnostics] StackTrace: at Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.FailedToImpersonateUserException.TraceConstructor()
at Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.FailedToImpersonateUserException..ctor(String message, Exception innerException, PowerBIErrorDetail[] errorDetails)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.ImpersonatorHelper.ImpersonateInternal(String userName, String password)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.ImpersonatorHelper.Impersonate(String userName, String password)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.AdomdConnectionProvider.OpenConnectionAsync()
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.ConnectionStrings.AdoNetDbFullConnectionString.<OpenConnectionAsync>d__17.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.ConnectionStrings.AdoNetDbFullConnectionString.OpenConnectionAsync()
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdoNetDbConnectionPool.<>c__DisplayClass1_0.<<CreateObjectInstance>b__0>d.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdoNetDbConnectionPool.<>c__DisplayClass1_0.<CreateObjectInstance>b__0()
at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.<ExecuteInActivity>d__7`1.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.ExecuteInActivity[T](PipelineActivityType pipelineActivityType, Func`1 action)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdoNetDbConnectionPool.<CreateObjectInstance>d__1.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdoNetDbConnectionPool.CreateObjectInstance(AdoNetDbFullConnectionString key)
at Microsoft.PowerBI.DataMovement.Pipeline.Common.Pool.BasePool`3.<CreatePoolObject>d__24.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.Common.Pool.BasePool`3.CreatePoolObject(TPoolObjectKey poolKey, TObjectKey objectKey)
at Microsoft.PowerBI.DataMovement.Pipeline.Common.Pool.StatelessPool`2.<Get>d__7.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.Common.Pool.StatelessPool`2.Get(TObjectKey key, Boolean forceNew)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.<>c__DisplayClass13_0.<<GetDatabaseConnection>b__0>d.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.<>c__DisplayClass13_0.<GetDatabaseConnection>b__0()
at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.<ExecuteInActivity>d__7`1.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.ExecuteInActivity[T](PipelineActivityType pipelineActivityType, Func`1 action)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.<GetDatabaseConnection>d__13.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.GetDatabaseConnection(DatabasesRequestBase dbRequestPayload, IGatewayCredentialStore credentialStore, Boolean forceNewConnection)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.<>c__DisplayClass1_0.<<EnsureConnection>b__0>d.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.<>c__DisplayClass1_0.<EnsureConnection>b__0()
at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.<ExecuteInActivity>d__7`1.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.ExecuteInActivity[T](PipelineActivityType pipelineActivityType, Func`1 action)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.<EnsureConnection>d__1.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.EnsureConnection(GatewaySerializationContext serverContext, OpenConnectionRequest connectPayload)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorDispatcher.<DispatchImpl>d__1.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorDispatcher.DispatchImpl(GatewaySerializationContext responseContext, OperationRequestBase requestObj)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorDispatcher.<Dispatch>d__0.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorDispatcher.Dispatch(GatewaySerializationContext serializationContext, OperationRequestBase requestObj)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<DeserializeImpl>d__9.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.DeserializeImpl(GatewayRelayContext requestContext, GatewaySerializationContext responseContext)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<>c__DisplayClass8_0.<<Deserialize>b__0>d.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<>c__DisplayClass8_0.<Deserialize>b__0()
at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.<ExecuteInActivity>d__7`1.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.ExecuteInActivity[T](PipelineActivityType pipelineActivityType, Func`1 action)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<Deserialize>d__8.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.Deserialize(GatewayRelayContext requestContext)
at System.Threading.Tasks.Dataflow.ActionBlock`1.ProcessMessageWithTask(Func`2 action, KeyValuePair`2 messageWithId)
at System.Threading.Tasks.Dataflow.ActionBlock`1.<>c__DisplayClass7.<.ctor>b__1(KeyValuePair`2 messageWithId)
at System.Threading.Tasks.Dataflow.Internal.TargetCore`1.ProcessMessagesLoopCore()
at System.Threading.Tasks.Task.Execute()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot)
at System.Threading.Tasks.Task.ExecuteEntry(Boolean bPreventDoubleExecution)
at System.Threading.ThreadPoolWorkQueue.Dispatch()

GordonDoggett
Regular Visitor

Hi @v-yuezhe-msft  is there any update on this? we download the new March realease as suggested in some of the other ideas but we are still experiencing this intermittent issues, please can you advise?

ENICHOLS
Frequent Visitor

I am also having this issue. Everything was working fine until I was troubleshooting a failed refresh and followed the instructions to update the on-prem gateway. I have 3 reports, all 3 use the same 2 data sets - 1 SQL database (has worked fine for around 6 months now) and 1 excel file saaved to a network share (working fine now - the original cause of the failed refresh). 

 

I am able to connect to SQL (via SSMS) and the Excel file from my local workstation where I create the reports using PowerBI Desktop, as well as a few testing VMs we utilize. However, when I go to the PowerBI Service and attempt to refresh the data set, I get:

 

Last refresh failed: Wed May 01 2019 11:36:31 GMT-0400 (Eastern Daylight Time)
Unable to connect to the data source undefined

 

The details of the data sources show everything is connected:

gatewayrefresherror_LI_Moment_Moment.jpg

 

Can anyone help me resolve the "undefined" error?