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)

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)

after our reporting department discovered Power BI, our existing Reporting Server 2016 Enterprise (including SA) should be updated as soon as possible to the new SQL Server 2017 with Power BI Report Server.

After the installation the configuration will follow, and now it will be interesting:

The configuration must be set up on the same database, URL, etc. as was previously the case with the Reporting Server 2016.

After applying the URLs a warning comes up saying that the appropriate options existed already before and are updated now with the new attitudes.That’s OK and we move on to the next settings.

After the activation of the previous settings, the PBIRS can be reached under the same URL, has all reports activated with the same subscriptions that were there before.

The migration is now complete and you can now additionally upload Power BI reports to the new server.For communication with the server, an alternative PBI client is available with which Power BI reports can be uploaded directly from the client and loaded from them.