Forum Discussion

Helper II

8 years ago

Solved

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 'Micros...

Power BI Report Server

jtarquino

8 years ago

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

jtarquino

Microsoft Employee

8 years ago

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

Anonymous

Not applicable

8 years ago

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

jtarquino
Microsoft Employee
8 years ago
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
- pdbenbow
  Resolver II
  8 years ago
  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>
  - jtarquino
    Microsoft Employee
    8 years ago
    Please update the web.config with my suggestion and let me know if that fix your issue
- PBIuser01
  Frequent Visitor
  8 years ago
  ~~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?~~
  - adrez86
    Helper I
    8 years ago
    Have you tried deleting the cache on the browser you're using? That worked for me on the loading hangup for BI reports

Forum Discussion

August release - Failed to load expression host assembly

Related content

Number of Core Products sold through assemblies

Preparing a pricelist - products and assemblies

Sales through sets (assemblies)

Help!!! Expression Error

Regular expression