Preparation for upgrading an SQL 2008 Reporting Services server in Integrated mode to 2008 R2

This is an information post really.

First up, install and run the upgrade advisor. Always a sensible step, they build these tools for a reason...

Mine cropped up a warning that seems to be fairly common, namely:

Upgrade Advisor detected one or more custom data processing extensions on the report server. Upgrade can continue, but you must move the data processing extension assemblies to the new installation folder.

A quick search revealed that this is due to having custom entries in the config sections of the Report Server setup. In my case I think this was just a red herring, but the necessary steps for resolution can be found here:

1. Details relating to this warning
2. Information on where to find the extensions (i.e. the deployment model for custom extensions)

Following these, I checked the web.config in the ReportServer folder and found the following:

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

      <dependentAssembly>

        <assemblyIdentity name="Microsoft.ReportingServices.Interfaces" publicKeyToken="89845dcd8080cc91" culture="neutral" />

        <bindingRedirect oldVersion="8.0.242.0" newVersion="10.0.0.0" />

        <bindingRedirect oldVersion="9.0.242.0" newVersion="10.0.0.0" />

      </dependentAssembly>

      <dependentAssembly>

        <assemblyIdentity name="Microsoft.ReportingServices.ProcessingCore" publicKeyToken="89845dcd8080cc91" culture="neutral" />

        <bindingRedirect oldVersion="9.0.242.0" newVersion="10.0.0.0" />

      </dependentAssembly> 

</assemblyBinding>

Based on my reading of the deployment model (second link above) this is what has caused the upgrade advisor to throw that warning. There's nothing there that was developed or deployed as a custom extension so I'm assuming it's just poor scripting not picking something up, after all, these look like pointers to later versions of existing core DLLs rather than anything that could be described as 'custom', presumably the result of a CU at some point...

In any case, from the documentation I know that what I need to do if things didn't go well is copy them across to the new installation folders and all should be well.

I will be running this upgrade within the next couple of days, so will post results after completion.

- rob