Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
Ccparkhill
Helper II
Helper II

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:

  • Failed to load expression host assembly. Details: Could not load file or assembly 'Microsoft.ReportingServices.ProcessingObjectModel, Version=15.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) (rsErrorLoadingExprHostAssembly)

 

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. 

1 ACCEPTED SOLUTION

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

View solution in original post

38 REPLIES 38
mgmeyer
Power BI Team
Power BI Team

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

 

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.  

Thank you

 

I very much appreciate the quick turnaround for the fix.  This allows us to move forward to use in production.

@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 😉

I can't imagine why... "Hey! The Changelog shows a new version but the download is wrong! Where's my download already Microsoft, GAWSH!"  LOL

jtarquino
Microsoft Employee
Microsoft Employee

@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

 

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.

Any news on the patch yet?

@Ccparkhill Did you just update part of the config files or the whole file?  @jtarquino didn't respond to my earlier query so I still don't know if we should still be looking at updating the whole file!!

 

Thanks

@kelly_darren I replaced the entire assemblyBinding section in each file with the text @jtarquino posted in message 17. 

@Ccparkhill I missed the fact that the supplied XML was only the Assembly Binding....thats what you get for reading on a phone.  Thank you for the clarification.

 

Anonymous
Not applicable

I do not have caching or snapshots enabled on my paginated reports, and I am receiving the same error.

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

 

 

Partial fix only ---   

We had the same issue after running the August PBIRS upgrade.  After modifying both config files following the directions outlined by jtarquino, the report builder based reports successfully loaded ( so far, for the ones we tested)

 

With the input from others, problem below was from the Chrome cache, that needs to be cleared out.....

Thanks  @pdbenbow@adrez86

But,  the Power BI Desktop reports are NOT  now WORKING.  They just hang, with the 'loading data' spinning round and round.

Tried uploading the PBI Desktop reports from PBI desktop, but that did not do anything.

Now what?  did changing the ProcessingObjectModel  break the newer PBI desktop reports, while allowing the older Report Builder reports to work?  

 

 

@PBIuser01, what browser are you using? If Chrome, I suggest you run the reports in incognito mode and see if the problem still occurs. If the reports run OK in incognito mode, then return to regular Chrome and purge your browser cache, then try again.

 

I experienced the same issue you're describing after completing the upgrade, as did some of our business users, but only in Chrome. Using incognito mode will give you a hint as to whether it's a problem with your browser, and purging the cache should remedy the issue.

Thanks!!  10,000 points

@pdbenbow   Great info - I'm running Chrome, and once I ran a sample report in incognito mode the report works.  The help desk is going to love me!

Have you tried deleting the cache on the browser you're using? That worked for me on the loading hangup for BI reports

Helpful resources

Announcements
July 2024 Power BI Update

Power BI Monthly Update - July 2024

Check out the July 2024 Power BI update to learn about new features.

July Newsletter

Fabric Community Update - July 2024

Find out what's new and trending in the Fabric Community.