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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
Anonymous
Not applicable

Gateway Issue

Hello Everyone,

 

I have setup gateway to refresh daily, but somehow, I have failed to refresh due to timeout, and I have never change anything to to the file, 13 and 14 went through but not 15 and alost 12 went error due to oever 120min

 

Any ideas?

e.PNG

 

1 ACCEPTED SOLUTION
v-juanli-msft
Community Support
Community Support

Hi @Anonymous

Could you refresh manually successfully?

 

Regarding to some similar issues, here is a workaround

1) Turn on mashup engine logs

2) Turn on verbosity level logs

3) Increase the MashupTestConnectionPoolContainerMaxInstanceCount to a larger number (say 20) in C:\Program Files\On-premises data gateway\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config

4) Restart gateway service and turn on sql profiler (if data source is SQL server)

5) Retry the refresh on the dataset.

 

Please find the instructions on how to log mashup and verbose logs.

To enable verbose please follow below link:

https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem-tshoot#microsoftpowerbidatamovementpipelinediagnosticsdllconfig


 

To enable the Mashup logs for the Gateway service on the Gateway machine:
a. Stop Gateway service PBIEgwService.
b. Open the file in a text editor like notepad: C:\Program Files\On-premises data gateway\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config
c. Search for "MashupExtendedTracing" in the file
d. Update the flag "MashupExtendedTracing" to True as the following:
<setting name="MashupExtendedTracing" serializeAs="String">
        <value>True</value>
</setting>
e. Using the Gateway Configurator to enable the "Additional logging".
f. Restart the service

 

If the refresh still fails, collect the logs and create a support ticket here for better help.

 

Best Regards

Maggie

View solution in original post

1 REPLY 1
v-juanli-msft
Community Support
Community Support

Hi @Anonymous

Could you refresh manually successfully?

 

Regarding to some similar issues, here is a workaround

1) Turn on mashup engine logs

2) Turn on verbosity level logs

3) Increase the MashupTestConnectionPoolContainerMaxInstanceCount to a larger number (say 20) in C:\Program Files\On-premises data gateway\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config

4) Restart gateway service and turn on sql profiler (if data source is SQL server)

5) Retry the refresh on the dataset.

 

Please find the instructions on how to log mashup and verbose logs.

To enable verbose please follow below link:

https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem-tshoot#microsoftpowerbidatamovementpipelinediagnosticsdllconfig


 

To enable the Mashup logs for the Gateway service on the Gateway machine:
a. Stop Gateway service PBIEgwService.
b. Open the file in a text editor like notepad: C:\Program Files\On-premises data gateway\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config
c. Search for "MashupExtendedTracing" in the file
d. Update the flag "MashupExtendedTracing" to True as the following:
<setting name="MashupExtendedTracing" serializeAs="String">
        <value>True</value>
</setting>
e. Using the Gateway Configurator to enable the "Additional logging".
f. Restart the service

 

If the refresh still fails, collect the logs and create a support ticket here for better help.

 

Best Regards

Maggie

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

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