Since the May 2022 update our PowerBI RS servers have been throwing excessive warnings when "Editing a report" from the portal
Example:
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=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.CodeAnalysis.VisualBasic, Version=4.0.0.0, 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
