topic Re: August release - Failed to load expression host assembly in Report Server

August release - Failed to load expression host assembly

Ccparkhill — Thu, 16 Aug 2018 15:56:07 GMT

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.

Re: August release - Failed to load expression host assembly

messerjc — Thu, 16 Aug 2018 16:04:07 GMT

Sounds like the same issue @DaveW and @CB1 was/is having? Tagging them here to get their attention...

Re: August release - Failed to load expression host assembly

pdbenbow — Thu, 16 Aug 2018 16:32:33 GMT

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.

Re: August release - Failed to load expression host assembly

mgmeyer — Thu, 16 Aug 2018 16:51:22 GMT

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.

Re: August release - Failed to load expression host assembly

pdbenbow — Thu, 16 Aug 2018 16:56:56 GMT

That was not the case for us. I upgraded our dev report server first in order to regression-test all our reports before proceeding with the upgrade to the test and production servers, and none of our dev reports use cached snapshots.

Re: August release - Failed to load expression host assembly

messerjc — Thu, 16 Aug 2018 16:59:34 GMT

Is there any way force a refresh of the cache if that is the case? I'm hoping to upgrade our dev and qa servers with this today and it's all older paginated reports, so I'll report back if I run into the same issue.

Re: August release - Failed to load expression host assembly

mgmeyer — Thu, 16 Aug 2018 17:07:58 GMT

We're investigating it now, will update shortly.

Re: August release - Failed to load expression host assembly

jtarquino — Thu, 16 Aug 2018 18:04:40 GMT

@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

Re: August release - Failed to load expression host assembly

Anonymous — Thu, 16 Aug 2018 20:26:34 GMT

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

Re: August release - Failed to load expression host assembly

jtarquino — Fri, 17 Aug 2018 00:11:08 GMT

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

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

Re: August release - Failed to load expression host assembly

pdbenbow — Fri, 17 Aug 2018 01:11:57 GMT

@jtarquino, thanks for the suggestion. I opened up the config files and here is what we have:

web.config

      <dependentAssembly>
        <assemblyIdentity name="Microsoft.ReportingServices.ProcessingObjectModel"
             publicKeyToken="89845dcd8080cc91"
             culture="neutral" />
        <bindingRedirect oldVersion="9.0.242.0-14.0.0.0"
                         newVersion="2018.8.0.0" />
      </dependentAssembly>

ReportingServicesService.exe.config

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

Re: August release - Failed to load expression host assembly

jtarquino — Fri, 17 Aug 2018 01:13:18 GMT

Please update the web.config with my suggestion and let me know if that fix your issue

Re: August release - Failed to load expression host assembly

DaveW — Fri, 17 Aug 2018 01:48:25 GMT

I found the same differences with the Web Config file and the ReportServicesService Config file

I made the change, stopped and started the Report Server, still the same issue.

From your text, should the old version be 2018.8.0.0 not 2018.0.0.0?

I noticed that the other DependentAssemblies in the Web Config file have the old version of "9.0.242.0-14.0.0.0"

Whereas all the DependentAssemblies in the ReportServicesService Config file have the old version of "9.0.242.0-2018.8.0.0"

Should we change all these also?

Re: August release - Failed to load expression host assembly

adrez86 — Fri, 17 Aug 2018 04:20:46 GMT

I too have the same results/question as DaveW. Looks like we have the exact same config files and the suggested change did not work

Re: August release - Failed to load expression host assembly

adrez86 — Fri, 17 Aug 2018 05:15:32 GMT

Update: I restarted the server and my paginated reports are now loading properly. I left the web config file with the changes. I'm going to leave it with the changes even though I'm not sure if it was both that fixed it or just the restart.

Re: August release - Failed to load expression host assembly

kelly_darren — Fri, 17 Aug 2018 09:51:54 GMT

I've encountered the exact same issue, in that my paginated reports are errorinng. Without changing the web config files a reboot of the server did not work.

The web config file at this location "C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\web.config"

had the below entry

The web config file in the bin folder had this entry

As suggested by @jtarquino I updated my first web config file only as it differed, saved it and refreshed my paginated report and it rendered successfully.

My paginated reports are not cached or snapshots, they are directly connected to our backend reporting DB.

Hope the above is of some help.

Re: August release - Failed to load expression host assembly

jtarquino — Fri, 17 Aug 2018 14:44:17 GMT

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

Re: August release - Failed to load expression host assembly

kelly_darren — Fri, 17 Aug 2018 15:13:35 GMT

@jtarquino are you recommending we replace the entire web config files with what you have posted?

Also when you do make a fix and update the .exe can any chance we can be kept informed that a new update is availible, because the last time only the changelog page was being updated and people didnt realise a fixed version was availible for download.

Re: August release - Failed to load expression host assembly

DaveW — Fri, 17 Aug 2018 21:44:45 GMT

Thanks for the update, I notice there is a slight discrepancy with the Old and New for this one.

Does this matter that the new is 14 and the old is 15, should the new by 15?

Re: August release - Failed to load expression host assembly

jtarquino — Fri, 17 Aug 2018 21:47:37 GMT

Dave it is by design it, the newVersion property for that library should be 14