一同事将测试服务器从SQL Server 2008 R2 SP2升级到了SQL Server 2008 R2 SP3后发现Report Service的报表编辑时启动不了Report Builder，错误信息如下所示：
PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language Runtime : 4.0.30319.18408
System.Deployment.dll : 4.0.30319.18408 built by: FX451RTMGREL
clr.dll : 4.0.30319.18408 built by: FX451RTMGREL
dfdll.dll : 4.0.30319.18408 built by: FX451RTMGREL
dfshim.dll : 4.0.41209.0 (Main.041209-0000)
SOURCES
Deployment url : http://localhost/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application?ReportPath=/GLS/FlowCotton
Server : Microsoft-HTTPAPI/2.0
X-AspNet-Version: 2.0.50727
Application url : http://localhost/ReportServer/ReportBuilder/RptBuilder_3/MSReportBuilder.exe.manifest
Server : Microsoft-HTTPAPI/2.0
X-AspNet-Version: 2.0.50727
IDENTITIES
Deployment Identity : ReportBuilder_3_0_0_0.application, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86
Application Identity : MSReportBuilder.exe, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86, type=win32
APPLICATION SUMMARY
* Online only application.
* Trust url parameter is set.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://localhost/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application?ReportPath=/GLS/FlowCotton resulted in exception. Following failure messages were detected:
+ File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [12/30/2015 3:22:38 PM] : Activation of http://localhost/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application?ReportPath=/GLS/FlowCotton has started.
* [12/30/2015 3:22:40 PM] : Processing of deployment manifest has successfully completed.
* [12/30/2015 3:22:40 PM] : Installation of the application has started.
* [12/30/2015 3:22:44 PM] : Processing of application manifest has successfully completed.
* [12/30/2015 3:22:48 PM] : Found compatible runtime version 2.0.50727.
* [12/30/2015 3:22:48 PM] : Detecting dependent assembly Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil using Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil.
* [12/30/2015 3:22:48 PM] : Detecting dependent assembly System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil.
* [12/30/2015 3:22:48 PM] : Request of trust and detection of platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [12/30/2015 3:23:08 PM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
- File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
at System.Deployment.Application.ComponentVerifier.VerifyComponents()
at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
搜索了一下资料，居然发现官方有资料介绍了这个问题：Report Builder of SQL Server 2008 R2 Service Pack 3 does not launch.
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.
官方解释不打算修复这个问题（真是坑爹），它建议执行下面两个解决办法：
1： 客户端
从链接http://www.microsoft.com/en-pk/download/details.aspx?id=6116下载安装SQL SERVER 2008 R2 RTM的Report Builder 3.0
或者从连接http://www.microsoft.com/en-us/download/details.aspx?id=42301限制安装SQL SERVER 2014的Report Builder。
2：服务器端
卸载SP3，然后卸载 SP2，然后从新应用SP3来解决问题。