Please check before upgrading if you have one of the versions mentioned in the upgrade path.

https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades?view=sql-server-2017#upgrades-from-earlier-versions-to-

After upgrading the SSRS instance with SCCM reporting role installed, you might end up having the following issue when opening a report.

Failed to load expressions host assembly. Details: Could not load file or assembly ‘SrsResources. Culture=Neutral’ or one of its dependencies. The system cannot find the file specified.

This is usually coming from a mismatch in the configuration file of the reporting server and file path for custom assemblies.

In order to investigate you need to look for the file rsssvpolicy.config , which is located in the SSRS installation folder.

Check in the file if the path to the “srsresources.dll” is the proper one and change-it to the actual one if this is the case.

If you upgrade from SSRS 2008 to SSRS 2016 the following steps can fix the problem.

• Copy “srsresources.dll” from:

Source: <SQL Installation Path>\MSRS10_50.MSSQLSERVER\Reporting Services\Report Server\Bin

Destination: <SQL Installation Path>\MSRS13.MSSQLSERVER\Reporting Services\Report Server\Bin

• Copy “rssrvpolicy.config” (if it was not copied in the upgrade process) from:

Source: “<SQL Installation Path>\MSRS10_50.MSSQLSERVER\Reporting Services\Report Server”

Destination: “<SQL Installation Path>\MSRS13.MSSQLSERVER\Reporting Services\Report Server”

• Verify this file by searching for “srsresources.dll” and simply check the path to point to the proper location of the file.

• Copy the entire “SCCMErrorResources” folder from:

Source: “<SQL Installation Path>\MSRS10_50.MSSQLSERVER\Reporting Services\Report Server\Bin”

Destination: “<SQL Installation Path>\MSRS13.MSSQLSERVER\Reporting Services\Report Server\Bin”.

• If the file does not exist, copy and edit the file “perf-ReportServerrsperfctr.ini”, from:

Source: “<SQL Installation Path>\MSRS10_50.MSSQLSERVER\Reporting Services\Report Server\Bin”

Destination: “<SQL Installation Path>\MSRS13.MSSQLSERVER\Reporting Services\Report Server\Bin”

• Edit the path for “symbolfile” to “MSRS13”.

Please don’t forget this is just a workaround and you can use-it at your own risk.

The supported method is to reinstall reporting services. Take into consideration backing up all the custom reports you have in SSRS.

Adjust the source and destination to match your SSRS path.

A PowerShell sample script is available on the blog section to backup the RDL files from the server.

In case that you are receiving the error code (0x80092004) when installing the August 2019 released patches you need to know that this is a consequence of SHA 2 implementation for patch signing.

The following 2 patches should be installed on the machine in order to complete the installation.

• KB4474419 — SHA-2 code signing support update for Windows Server 2008 R2, Windows 7, and Windows Server 2008: August 13, 2019.
• KB4490628 — Servicing stack update for Windows 7 SP1 and Windows Server 2008 R2 SP1: March 12, 2019, not listed as a dependency.

Sometimes is hard to find the proper table or column in the available views.

The easiest way would be to use simple database query to search in the information schema. For Microsoft reference please check the url below. https://docs.microsoft.com/en-us/sql/relational-databases/system-information-schema-views/system-information-schema-views-transact-sql?view=sql-server-2017

SELECT DISTINCT table_name,column_name FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME LIKE ('v_%') AND COLUMN_NAME LIKE '%sourcepath%'
SELECT DISTINCT table_name,column_name FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME LIKE ('v_%') ORDER BY column_name