Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Since the updgrade to version 1.24.9392.34333 the ReportingServicesService.logs generate GBs of data per day with default log settings. The issue seems that whenever a dataset is loaded it looks like every field entry is logged by something called [Report Walker].
Steps to reproduce
- Have a dataset on the PBI report server
- Open the dataset
- Go to Data Preview -> Load data
- You will have a lot of lines like these in ReportingServciesService_timestamp.log
rdlenginehost!ReportServer_0-1!27a0!10/21/2025-18:06:34:: i INFO: [Report Walker] Processing ReportItem<TextBox>: TextBox_0003_FieldName1_ACDD4B78
rdlenginehost!ReportServer_0-1!2374!10/21/2025-18:06:34:: i INFO: [Report Walker] Processing ReportItem<TextBox>: TextBox_0006_FieldName2_9110D2DC
rdlenginehost!ReportServer_0-1!30fc!10/21/2025-18:06:34:: i INFO: [Report Walker] Processing ReportItem<TextBox>: TextBox_0007_FieldName3_6E9D0731
rdlenginehost!ReportServer_0-1!2374!10/21/2025-18:06:34:: i INFO: [Report Walker] Processing ReportItem<TextBox>: TextBox_0007_FieldName3_247E481D
rdlenginehost!ReportServer_0-1!27a0!10/21/2025-18:06:34:: i INFO: [Report Walker] Processing ReportItem<Tablix>: Tablix_E7DDBF00
rdlenginehost!ReportServer_0-1!fac!10/21/2025-18:06:34:: i INFO: [Report Walker] Processing ReportItem<TextBox>: TextBox_0006_FieldName4_80E62E7F
rdlenginehost!ReportServer_0-1!27a0!10/21/2025-18:06:34:: i INFO: [Report Walker] Processing ReportItem<TextBox>: TextBox_0004_FieldName5_3BCA1333
rdlenginehost!ReportServer_0-1!2374!10/21/2025-18:06:34:: i INFO: [Report Walker] Processing ReportItem<TextBox>: TextBox_0004_FieldName6_37CA7C5F
rdlenginehost!ReportServer_0-1!30fc!10/21/2025-18:06:34:: i INFO: [Report Walker] Processing ReportItem<TextBox>: TextBox_0004_FieldName6_5AFF6016
rdlenginehost!ReportServer_0-1!2374!10/21/2025-18:06:34:: i INFO: [Report Walker] Processing ReportItem<TextBox>: TextBox_0001_FieldName7_A42C1B49
rdlenginehost!ReportServer_0-1!27a0!10/21/2025-18:06:34:: i INFO: [Report Walker] Processing ReportItem<TextBox>: TextBox_0005_FieldName8_79E38078
rdlenginehost!ReportServer_0-1!fac!10/21/2025-18:06:34:: i INFO: [Report Walker] Processing ReportItem<TextBox>: TextBox_0001_FieldName9_86050404
rdlenginehost!ReportServer_0-1!27a0!10/21/2025-18:06:34:: i INFO: [Report Walker] Processing ReportItem<TextBox>: TextBox_0006_FieldName4_B332431D
As a workaround we have set the log level for the Reporting Services lower.
C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\bin\ReportingServicesService.exe.config
In the <RStrace> segment we changed the line
<add name="Components" value="all:3" />to
<add name="Components" value="all:2" />
Does anyone know about a better solution without loosing some diagnostic information in the logs?
Solved! Go to Solution.
Hi @jpapmeier
After upgrading to Power BI Report Server version 1.24.9392.34333, many users have reported excessive log growth in the ReportingServicesService logs, often reaching several gigabytes per day. The issue is caused by an overly verbose logging behavior from a component called [Report Walker], which logs a message for nearly every field or report item processed during dataset loading. This results in a massive amount of repetitive “Processing ReportItem” entries whenever a dataset is previewed or refreshed. While Microsoft hasn’t yet released an official fix, the most practical workaround, as you mentioned, is to reduce the RStrace logging level in the configuration file (ReportingServicesService.exe.config) from all:3 (Info level) to all:2 (Warning level). This effectively suppresses the excessive info-level entries while still retaining important warnings and errors. However, this change does come with the trade-off of losing some diagnostic detail that might be useful for deeper troubleshooting. Until Microsoft addresses this issue in a cumulative update or hotfix, adjusting the logging level remains the safest and most efficient solution to control log file growth without disrupting server functionality.
Hi @jpapmeier
After upgrading to Power BI Report Server version 1.24.9392.34333, many users have reported excessive log growth in the ReportingServicesService logs, often reaching several gigabytes per day. The issue is caused by an overly verbose logging behavior from a component called [Report Walker], which logs a message for nearly every field or report item processed during dataset loading. This results in a massive amount of repetitive “Processing ReportItem” entries whenever a dataset is previewed or refreshed. While Microsoft hasn’t yet released an official fix, the most practical workaround, as you mentioned, is to reduce the RStrace logging level in the configuration file (ReportingServicesService.exe.config) from all:3 (Info level) to all:2 (Warning level). This effectively suppresses the excessive info-level entries while still retaining important warnings and errors. However, this change does come with the trade-off of losing some diagnostic detail that might be useful for deeper troubleshooting. Until Microsoft addresses this issue in a cumulative update or hotfix, adjusting the logging level remains the safest and most efficient solution to control log file growth without disrupting server functionality.
Hi @jpapmeier ,
Thanks for reaching out to Community Forum.
The excessive log files you’re seeing in Power BI Report Server (September 2025 update) are caused by the Report Walker feature, which logs a lot of details for every report and can quickly fill up your disk. To fix this, you can reduce logging by opening the ReportingServicesService.exe.config file in your PBIRS installation folder, finding the line <add key="LogLevel" value="Information"/>, and changing Information to Warning or Error so that only important messages are logged. After saving the file, restart the Power BI Report Server service. It’s also a good idea to keep an eye on the LogFiles folder and move or archive older logs to prevent them from taking up too much space. Finally, since this issue is known in the September 2025 update, reporting it to Microsoft can help them track and fix it in future updates.
Thank you.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 1 |
| User | Count |
|---|---|
| 10 | |
| 5 | |
| 5 | |
| 5 | |
| 4 |