Showing results for 
Search instead for 
Did you mean: 
Regular Visitor

Report Builder throws excessive Warnings in ReportingServicesService

Since the May 2022 update our PowerBI RS servers have been throwing excessive warnings when "Editing a report" from the portal


library!ReportServer_0-5!1d5c!10/25/2022-15:49:26:: i INFO: Call to CreateReportEditSessionAction(Parent=/, Report=****NameOfTheReport*****). User: MYDOMAIN\MYUSERID.
processing!ReportServer_0-5!1d5c!10/25/2022-15:49:26:: w WARN: An exception occurred when extracting info about expression usage. Details: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.CodeAnalysis.VisualBasic, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.CodeAnalysis.VisualBasic, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
at Microsoft.ReportingServices.RdlExpressions.ExpressionExtractor.ExtractExpression(ExpressionInfo exprInfo)
at Microsoft.ReportingServices.RdlExpressions.VBExpressionParser.AddToExpressionInstrumentation(ExpressionInfo expressionInfo)

WRN: Assembly binding logging is turned OFF.


This warning is repeated about 20 times, bloating the logs. When deploying large batches of reports using powershell modules, this turns into over 1000 copies of said error.


I have repeated the use case against a much older server installation (Jan 2019) and do not get the same Warnings.

I have turned on Fusion logging as per internet guidance :~)  and with the added verbose logging can clearly see the report server is looking for:

LOG: Attempting download of new URL file:///L:/Program_Files/PBIRS/PBIRS/ReportServer/RSTempFiles/reportserver/87b89504/492007a1/Microso....

The DLL its searching for definitely does not exist in the installation directory:

l:\programfiles\pbirs\reportserver\bin along with all the other DLLs the fusion logs reference


Update to Sept 2022? Update dot.Net? Thoughts

New Member

We see the same problem on our server. Setting the suggested registry entry hasn´t changed anything. 
The problem occured some versions before and wasn´t solved in any upgrade we made. (Currently have have Sep 22 deployed).

Any help on the topic is appreciated!


Best regards,


Regular Visitor

Running as admin makes no differnce. Same warnings thrown in the logs

Community Support
Community Support

Hi @jeffcurrie ,


You can indeed upgrade your Power BI report Server to the September release to see if this issue is mitigated.

Have you tried running Power BI Report Server as an administrator?


Best Regards,
Community Support Team _ Caitlyn


Helpful resources

Vote for T-Shirt Design

Power BI T-Shirt Design Challenge 2023

Vote for your favorite t-shirt design now through March 28.

March 2023 Update3

Power BI March 2023 Update

Find out more about the March 2023 update.

March Events 2023A

March 2023 Events

Find out more about the online and in person events happening in March!