Reports on Power bi service is not showing latest data on publish and scheduled refresh

[kasirambala]

Configuration:

DataSource connection : Tabular

Connection type : Direct Query

Issue:

When connected from client tools powerbi desktop and excel is showing all the data and when published to power bi service, it is showing data up to a particular date and no data change after multiple refreshes.

Observations:

1.When we download and analyze in excel from power bi service all data is shown

2.Few charts are showing all data and few charts are not showing all data in power bi service.

  For simple test I have created a test reports with one visual just to display count then also it is not showing all data

3.For testing two gateways are configured prod ( Connects to prod tabular) and non prod ( connects to non prod tabular), All data is showing up when we connect to non prod gateway. ( both the configurations are same and installed on two different servers )

[kasirambala]

Gateway logs:

Exceptions are logged on the Gateway, but not able to trace the issue

DM.EnterpriseGateway Information: 0 : 2018-06-06T03:05:07.8383434Z DM.EnterpriseGateway 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 0000 00000000-0000-0000-0000-000000000000 E5F6199B [DM.GatewayCore] Ignoring Faulted event for 'Transfer service' because it happened before the service host was actually opened
DM.EnterpriseGateway Information: 0 : 2018-06-06T03:05:07.8383434Z DM.EnterpriseGateway 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 0000 00000000-0000-0000-0000-000000000000 9EA26F93 [DM.GatewayCore] Transfer service faulted
DM.EnterpriseGateway Information: 0 : 2018-06-06T03:05:07.8422498Z DM.EnterpriseGateway 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 0000 00000000-0000-0000-0000-000000000000 612F4B3D [DM.GatewayCore] Aborting service host for 'Transfer service' that failed to create
DM.EnterpriseGateway Information: 0 : 2018-06-06T03:05:07.8432264Z DM.EnterpriseGateway 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 0000 00000000-0000-0000-0000-000000000000 47CFB9DF [DM.GatewayCore] Transfer service aborted
DM.EnterpriseGateway Information: 0 : 2018-06-06T03:05:07.8432264Z DM.EnterpriseGateway 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 0000 00000000-0000-0000-0000-000000000000 294F8B2E [DM.GatewayCore] Transfer service closed
DM.EnterpriseGateway Error: 0 : 2018-06-06T03:05:07.8432264Z DM.EnterpriseGateway 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 0000 00000000-0000-0000-0000-000000000000 46F2FAA1 [DM.GatewayCore] Swallowing non-fatal exception encountered during attempt 4470/2147483647 for startup of Transfer service:
System.TimeoutException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond --->

System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.ServiceBus.AmqpRelay.ConnectTask.<Start>d__5.MoveNext()
   --- End of inner exception 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 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.ServiceModel.ServiceHostController.<StartRunnerAsync>d__14.MoveNext()

[Anonymous]

@kasirambala,

It looks like a timeout issue. 

Please go to C:\Program Files\On-premises data gateway, open Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file, and change the value of MashupDSRTestConnectionTimeout setting from  00:00:50 to a proper value such as 00:02:50, then restart your gateway and check if you can get rid of this issue. Back up the config file before your make any changes to it. 

Regards,
Lydia