Forum Discussion
August release - Failed to load expression host assembly
I'm receiving the following errror on a number of SSRS reports using the August 2018 release:
|
I've tried clearing the cache in both IE and Chrome but this does not resolve the issue. I have found that deleting the report and redeploying it does resolve the issue, however.
Thanks a lot for your patience and help to diagnose the issue
For your reference this is the entire assemblyBinding section for the two files in a clean install of PBIRS, after you udpate them you need to restart the service as some of you have mentioned and it should fix your issue.
"C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\web.config"
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Microsoft.ReportingServices.Interfaces" publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="8.0.242.0-2018.8.0.0" newVersion="2018.8.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.ReportingServices.ProcessingCore" publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="9.0.242.0-2018.8.0.0" newVersion="2018.8.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.ReportingServices.ProcessingObjectModel" publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="9.0.242.0-2018.8.0.0" newVersion="2018.8.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="10.0.0.0-15.0.0.0" newVersion="14.0.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="msmgdsrv" publicKeyToken="89845dcd8080cc91" /> <bindingRedirect oldVersion="9.0.0.0-15.0.0.0" newVersion="15.0.0.0" /> <codeBase version="15.0.0.0" href="%ProgramFiles%\Microsoft Analysis Services\AS OLEDB\150\msmgdsrv.dll" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.Owin" publicKeyToken="31bf3856ad364e35" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="System.Web.Cors" publicKeyToken="31bf3856ad364e35" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-5.0.0.0" newVersion="5.2.3.0" /> </dependentAssembly> </assemblyBinding>"C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\bin\ReportingServicesService.exe.config"
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <probing privatePath="bin" /> <dependentAssembly> <assemblyIdentity name="ReportingServicesAppDomainManager" publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="8.0.242.0-15.0.0.0" newVersion="15.0.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.ReportingServices.Interfaces" publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="8.0.242.0-2018.8.0.0" newVersion="2018.8.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.ReportingServices.Exceptions" publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="8.0.242.0-2018.8.0.0" newVersion="2018.8.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.ReportingServices.ProcessingRenderingCommon" publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="8.0.242.0-2018.8.0.0" newVersion="2018.8.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.ReportingServices.ProcessingCore" publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="9.0.242.0-2018.8.0.0" newVersion="2018.8.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.ReportingServices.ProcessingObjectModel" publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="9.0.242.0-2018.8.0.0" newVersion="2018.8.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="10.0.0.0-15.0.0.0" newVersion="14.0.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.Owin" publicKeyToken="31bf3856ad364e35" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="System.Web.Cors" publicKeyToken="31bf3856ad364e35" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-5.0.0.0" newVersion="5.2.3.0" /> </dependentAssembly> </assemblyBinding>We will be working in a fix in order to solve the issues with the config files during the upgrade
38 Replies
I encountered the exact same issue after upgrading to the August 2018 version of PBIRS. It seemed to affect all paginated reports that already existed on the server prior to the upgrade. I was able to clear the issue by re-deploying all of the reports using our VSTS release pipeline.
There was a dll version change that happened in this release that is the root cause here, most likely it's caused by execution snapshots being cached in the database. If you re-render (not from cache) the report you shouldn't need to be republished.
We just published an update that addresses this issue as well as some rendering issues, you can get it here:
https://www.microsoft.com/en-us/download/details.aspx?id=57270
mgmeyer Changelog update incoming tomorrow maybe? :) https://docs.microsoft.com/en-us/power-bi/report-server/changelog
Working on it, wanted to get the bits out first ;)
Thank you
I very much appreciate the quick turnaround for the fix. This allows us to move forward to use in production.
Just looking at the Change Log and the latest version listed is:
1.3.6816.37243 (Build 15.0.2.557)
However the version I downloaded based on the announcement in this thread is:
1.3.6813.37954 (Build 15.0.2.554)
This version is not listed in the Change Log so am unsure of the differences between the two but have now upgraded to the latest build.
Possibly others may also be unaware.
Ccparkhill, I'm investigating the issue, does the report that fails to render have history snapshots or caching enabled?
or its happening to all your reports regardless the features you have enabled on them.
Thanks
For those affected can you validate in this files
"C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\web.config"
"C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\bin\ReportingServicesService.exe.config"
There is a configuration for Microsoft.ReportingServices.ProcessingObjectModel , it should look like the one below
focus in the values for oldVersion and newVersion
<dependentAssembly>
<assemblyIdentity name="Microsoft.ReportingServices.ProcessingObjectModel" publicKeyToken="89845dcd8080cc91" culture="neutral" />
<bindingRedirect oldVersion="9.0.242.0-2018.0.0.0" newVersion="2018.8.0.0" />
</dependentAssembly>Feel free to change them and verify if that fix your issue, also if they are different that the one I showed, please post here the values you have.
Thanks
All RDL reports are now rendering sucessfully after updating the config files and restarting the service. We were not using snapshots or caching. Also, not all of our RDL reports were affected by this issue.
When can we expect to see an updated installer? Thanks.
We're going to try and get a patch update out for this sometime this week.
