Dear Customers
we have discovered a problem with Report Builder that ships with SQL Server 2008 R2 Service Pack 3.
If you installed SQL Server 2008 R2, have upgraded it to Service Pack 2 and then applied Service Pack 3, then Report Builder will fail to launch. It will raise the following error.
ERROR SUMMARY
Below is a summary of the errors,
details of these errors are listed later in the log.
* Activation of http://…/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application resulted in exception. Following failure messages were detected:
+ File,
Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
We are not planning to release a fix for this issue. Instead we recommend you implement one of the following workarounds.
- Client side workaround:
- Install and run Report Builder 3.0 of SQL Server 2008 R2 RTM from the following location: http://www.microsoft.com/en-pk/download/details.aspx?id=6116
- Or install and run Report Builder of SQL Server 2014 from the following location: http://www.microsoft.com/en-us/download/details.aspx?id=42301
- Server side workaround:
- Uninstall Service Pack 3 then uninstall Service Pack 2 and then reinstall Service Pack 3.
We acknowledge the inconvenience. Apologies for this.
Also, we are in the process of:
- Updating the SQL Server Release Services Blog post announcing the release of SQL Server 2008 R2 Service Pack 3 to add a note to proactively inform customers.
- Updating the download page of SQL Server 2008 R2 Service Pack 3 to add a note to proactively inform customers.
- Creating and publishing quickly a dedicated KB article about this issue.
- Responding to the two MSConnect items that we are aware of about this issue: 1001935 and 1001699.
Regards.
Jean-Yves Devant
Senior Program Manager – SQL Server.
The source of the problem is that Microsoft.ReportingServices.ComponentLibrary.Controls.dll was changed in SP2 and the manifest file in SP3 is unaware of this. What was changed in SP2, and why is this being rollbacked?
If you are doing a fresh install and either slipstream service pack 3 or install sql server then install service pack 3 only, would this work?
"We are not planning to release a fix for this issue."
Why?
I second this:
"We are not planning to release a fix for this issue."
Why?
Because Microsoft takes a hard line on its support policies. SQL Server 2008 R2 is out of mainstream support and this is not a security issue. This SP was a rare exception, but they were clear that even if it introduced bugs, there wouldn't be public fixes released. They might actually develop a fix for this, but you'll likely need an Extended Hotfix Support agreement to get it. The customer-focused thing to do would be to re-issue the SP, but that's not the Microsoft we've come to know and love.
Installing SP3 causes this issue and the fix is to uninstall SP3, then uninstall SP2 then reinstall SP3? That maybe an OK answer for a NonProd system but this isn't a good answer for a live production system. Understand that SP3 is the last patch for this version of SQL Server but if Microsoft rolls out a rollup Service Pack we have a right to have it not break anything that worked to begin with.
This is not a production solution, but we ran into this in our DEV environment and I copied the pre-SP3 folder Program FilesMicrosoft SQL ServerMSSQLReporting ServicesReportServerReportBuilder from a server backup over the service packed folder on the DEV server and the error goes away. Again, I would not do this in PROD. I'm hoping MSFT does make a patch available soon, but this is a quick fix.
What do you do if SP2 was installed as part of the initial install and not a SP? I can’t uninstall it.
About the server side workaround: what if I have to patch an instance where Reporting Services is not installed? Report builder will work if I will install Reporting Services subsequently, patching it directly to SP3?
Hello Claudio,
Yes, if you install a Reporting Services instance directly to RTM and then apply SP3, Report Builder will launch as expected.
Thanks,
Matt Jones
Hello Jeff,
Please verify that SQL Server 2008 R2 SP2 is not present in the Installed Updates within Add/Remove Programs.
Thanks,
Matt
Hello Jamw,
Good to know there may be additional solutions that we haven't come up with!
Thanks,
Matt
Hello Jared,
If you install RTM and then install SP3 or install SP3 slipstream (which does not include SP2), you will not hit this issue.
Thanks,
Matt
I used a server-side procedure very similar to what jamw did to resolve in our environments. This assumes default installation paths with a default 'MSSQLSERVER' instance:
1. In the lab environment, we installed SQL Server 2008 R2 (RTM) on a Windows 2008 R2 SP1 server.
2. Applied Service Pack 3 (Microsoft KB2979597) directly without the cumulative application of SP1 or SP2.
3. Created a zip archive of the contents of the C:Program FilesMicrosoft SQL ServerMSRS10_50.MSSQLSERVERReporting ServicesReportServerReportBuilder directory from the lab server. This zip archive now contains a version of the Report Builder ClickOnce deployment files with manifests that work.
4. Extracted (with file overwrite enabled) the contents of this zip archive to the C:Program FilesMicrosoft SQL ServerMSRS10_50.MSSQLSERVERReporting ServicesReportServerReportBuilder directory on all SSRS servers in our environments.
We are in the same boat where SP2 was not installed as an update, rather part of the initial installation, so we can't remove it. It's not listed in the Installed updates.
Is there an actual solution for our scenario? I haven't seen a response that addresses it.
Hello Matt Hartman,
Can you check in "Add or Remove Programs" and then click on "View Installed Updates"? You should find "SQL Server 2008 R2 Service Pack 2" even if you had done a slipstream installation.
Thanks,
Matt Jones
SQL Server Tiger Team
Everything hinges on one file that got back-reved in SP3. The file of interest is ReportBuilderRptBuilder_3Microsoft.ReportingServices.ComponentLibrary.Controls.dll.deploy . The RTM version of that file is 10.50.1600.1 and dates from 4/3/2010. The SP2 version of that file is 10.50.3721.0 and dates from 5/19/2012. The SP3 version of that file (assuming one uninstalls SP2 first before installing SP3) is 10.50.1600.1 and dates from 4/3/2010 as well. Since install programs generally don't update files with newer version numbers, installing SP3 over SP2 results in that file being left alone, and thus violating the manifest that presumes the RTM file.
I was 95% certain mucking with the manifest wouldn't work, but on a whim I attempted splicing the dependentAssembly section from the SP2 MSReportBuilder.exe.manifest file into the SP3 MSReportBuilder.exe.manifest file. Reassuringly, this resulted in a failure to launch due to the digital signature in the manifest file not matching the contents.
There are a lot of RptBuilder_3 DLLs that get updated from SP2 to SP3, so I think the preferred route is to use the RTM Microsoft.ReportingServices.ComponentLibrary.Controls.dll.deploy file in order to get the benefit of the fixes in all the other files, especially since that is technically what Microsoft tested and validated. As an example the ReportBuilderRptBuilder_3MSReportBuilder.exe.deploy file in RTM is 10.50.1600.1 and dates from 4/3/2010. That file in SP2 is 10.50.4000.0 and dates from 6/29/2012. That file in SP3 is 10.50.6000.34 and dates from 8/23/2014.
It is sort of interesting that on an SP2 install, all of the files that reved for SP2 have a 06/29/2012 date, but this one file has a date of 5/19/2012. It's like somebody patched it and the update file made it into SP2, but they didn't do a fresh build of this file from the source tree before packaging like they did all the others. That might explain why this file got missed in SP3.
In any event, copy the 10.50.1600.1 ReportBuilderRptBuilder_3Microsoft.ReportingServices.ComponentLibrary.Controls.dll.deploy file with a date of 4/3/2010 and a file size of 669,536 into place on your SP3 machine and you're good to go.
Wow, Toby Ovod-Everett you really put some effort into finding that!! It sounds like the Microsoft deployment team should do better quality control of their source code for deployments.
Has anybody gotten the client side workaround to work? I have installed ReportBuilder3.0 and still have the same problem.
If I attempt to uninstall SP3, the program asks for sql_rs.msi that I can't find. Where can I find this installation package. I tried to extract the SP2 installation package. Without any success. Do you have a solution for that?
Walter,
I referred the updater to the original installation CD when it was looking for MSI files during the installation of SP3.
Many thanks to Toby Ovod-Everett. His workaround fixed our problem and saved me re-installation and hours of downtime.
Toby – does the machine need to be rebooted after the copy and replace?
We are upgrading from SQL2008R2 SP2 to SP3 for MS15-058 so I can see I may have a few options.
1 – uninstalled SP2 then install SP3 followed by build 6220
2 – Copy the folder Program FilesMicrosoft SQL ServerMSSQLReporting ServicesReportBuilder to a safe place and then upgrade to SP3 and copy it back.
3 – Create a server with only RTM and copy the Microsoft.ReportingServices.ComponentLibrary.Controls.dll.deploy from there to any SP3 servers where we have configured Reporting Services.
Please correct me if I am wrong.
Chris
Looks like Toby Ovod-Everett is a magician. I installed a standalone Reporting Services instance on a test server and saved the Control.dll.deploy. I then upgraded to SP1 and saved that one too (Its the same version). Then I upgraded to SP2 and saved that one (It had changed). Next was the SP2 uninstall followed by SP3 and then I saved it (Same as the RTM and SP1 versions.
Then I contacted the user who had seen the problem and stopped Reporting Services and renamed the bad version and copied in the RTM one. The user can now use Report Builder without errors.
Looks like his method works.
Chris
Thanks Toby. I didn't have a previous version to copy from, so I installed the Report Builder 3.0 from the link MS provided above on a separate computer. Then I grabbed the DLL from the install folder, copied it to my Reporting Server, and added .deploy at the end. Worked perfectly.
Thanks Toby/ Max DiOrio,
I didn't have a previous version to copy from, so I installed the Report Builder 3.0 from the link MS provided above on a separate computer. Then I grabbed the DLL (copy the 10.50.1600.1 ReportBuilderRptBuilder_3Microsoft.ReportingServices.ComponentLibrary.Controls.dll.deploy) from the install folder, renamed exactly same to add .deploy at the end copied and replaced with DLL on Reporting Server. Worked perfectly.
This should be mentioned in the SP3 installer details, I don't recall any mention that Report builder would be pooched if I updated to it or any special mention to uninstall SP2 as generally it's not good practice to jump updates. Thanks Microsoft for the downtime >o|
Thanks to Toby for supplying a fix/workaround.
I found that the file Microsoft.ReportingServices.ComponentLibrary.Controls.dll.deploy can still be found on the SQL 2008 R2 SP3 Server in a C:WindowsInstaller$PatchCache$Managed…… folder (used search in Windows Explorer), although it is named Microsoft_ReportingServices_ComponentLibrary_Controls_dll_deploy_64. It does have the right size and date.
Copying the file, renaming it and overwriting the original worked for me. No reboot or other actions were necessary in my case.
Rene
Thanks Toby Ovod-Everet!!!
I had the same problem after applying SP3 to SQL in support of an SCCM upgrade to 1602. After the upgrade, I tried to edit an SCCM report but the report builder would not launch. Replacing the “Microsoft.ReportingServices.ComponentLibrary.Controls.dll.deploy” file by copying it from another SQL server build 10.50.1617.0 fixed the problem for me.
Path to the file on my server was:
c:\Program Files\Microsoft SQL Server\MSSRS10_50.(SqlServer)\Reporting Services\ReportServer\ReportBuilder\RptBuilder_3
Thanks to Rene and Toby…that fixed the issue. Never would have fixed this one without their input/comment. Had the same issue with the out of sync file after applying SP3. One thing though…my file size was 655 KB and not the 669 KB ???