Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
I wanted to post a notice that we have identified and resolved an issue affecting the Power BI Report Server September release. The issue involves some extra logging that was added related to identify certain memory situations into the ReportingServicesService.log file. The amount of logging this generates under those situations results in repeated and near constant logging leading to the file growing in size quickly, and in some reported cases consuming all available drive space.
A QFE was released this morning, September PBIRS 1.18.8683.7488 (15.0.1113.165), which will be live for all users in the Microsoft Download Center within 24 hours. In this QFE the new logging has been properly moved to the verbose level.
We don't currently have a feature for this and including the query text is by design.
@Anonymous can you please at least bring it to the attention of the product team. We are now at over 30 100MB log files per day, just on a single cluster member. We also noticed that the Query text in the log is cut off at 32766 characters. (the actuall query can be up to 120K characters)
Can you do the same for gateways? The QueryStartReport log files include the query text (Base64 encoded) and we have a scenario where a (relatively benign) PowerApp accessing an on-prem data source manages to create a new 100 MB log file every hour (!!!) just because it has a ginormous query running every couple seconds. Would be nice if the verbosity could be controlled, for example to not include the query text.
User | Count |
---|---|
4 | |
3 | |
2 | |
2 | |
2 |
User | Count |
---|---|
6 | |
4 | |
3 | |
3 | |
2 |