Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
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?
Solved! Go to Solution.
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:
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
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:
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
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 45 | |
| 41 | |
| 20 | |
| 18 |
| User | Count |
|---|---|
| 68 | |
| 67 | |
| 33 | |
| 31 | |
| 29 |