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

DaveW

Advocate II

8 years ago

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?

adrez86

Helper I

8 years ago

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

jtarquino

Microsoft Employee

8 years ago

Thanks a lot for your patience and help to diagnose the 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

kelly_darren
Advocate II
8 years ago
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.
jtarquino
Microsoft Employee
8 years ago
Dave it is by design it, the newVersion property for that library should be 14
adrez86
Helper I
8 years ago
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.
kelly_darren
Advocate II
8 years ago
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

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

The web config file in the bin folder had this entry
<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>

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.
DaveW
Advocate II
8 years ago
Thanks for the update, I notice there is a slight discrepancy with the Old and New for this one.
<assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" culture="neutral" />
<bindingRedirect oldVersion="10.0.0.0-15.0.0.0" newVersion="14.0.0.0" />
Does this matter that the new is 14 and the old is 15, should the new by 15?
DaveW
Advocate II
8 years ago
Thanks for that, I made these changes yesterday and could open the Power BI reports but a colleague couldn't even after he refreshed his cache.
Not sure this is related but it appears when you publish new reports to the Report Server and go to manage the report in the URL, there isn't the option to: As the Viewer Viewing the report. Has the upgrade changed this capability?
Could this be why my colleague is not able to open the reports. We have the Report Server on a separate box to the SQL Server.
Does this upgrade take into account any mods made for kerberos settings in the config file?
mgmeyer
Power BI Team
8 years ago
This sounds like a differant issue and unrelated to the config file changes. By 'As the viewer viewing the report' I assume you're referring to the DataSource properties settings. What type of DataSource are you trying to edit PBIX or RDL? Also what type of DataSource are you connecting to?

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