Report Builder Click Once work OK with SQL Server 2008 SP1 but as soon as SP2 is installed we are getting the following error consistently in our Development boxes. Is anyone experiencing this problem? Looking at the installation folder path "\Program Files\Microsoft SQL Server 2008\MSRS10.SQL2008\Reporting Services\ReportServer\ReportBuilder"; it appears that a new Report Builder 2.0 application manifest file was NOT included with the SQL Server 2008 SP2 but new application build files did. PLATFORM VERSION INFO Windows : 5.1.2600.196608 (Win32NT) Common Language Runtime : 2.0.50727.3615 System.Deployment.dll : 2.0.50727.3053 (netfxsp.050727-3000) mscorwks.dll : 2.0.50727.3615 (GDR.050727-3600) dfdll.dll : 2.0.50727.3053 (netfxsp.050727-3000) dfshim.dll : 4.0.31106.0 (Main.031106-0000) SOURCES Deployment url : http://itbwxp19007:8080/ReportServer_SQL2008DEVED/ReportBuilder/ReportBuilder_2_0_0_0.application Server : Microsoft-HTTPAPI/1.0 X-AspNet-Version: 2.0.50727 Application url : http://itbwxp19007:8080/ReportServer_SQL2008DEVED/ReportBuilder/RptBuilder_2/MSReportBuilder.exe.manifest Server : Microsoft-HTTPAPI/1.0 X-AspNet-Version: 2.0.50727 IDENTITIES Deployment Identity : ReportBuilder_2_0_0_0.application, Version=10.0.4000.0, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86 Application Identity : MSReportBuilder.exe, Version=10.0.4000.0, 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://itbwxp19007:8080/ReportServer_SQL2008DEVED/ReportBuilder/ReportBuilder_2_0_0_0.application resulted in exception. Following failure messages were detected: + File, Microsoft.Data.ConnectionUI.Dialog.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/14/2010 1:39:08 PM] : Activation of http://itbwxp19007:8080/ReportServer_SQL2008DEVED/ReportBuilder/ReportBuilder_2_0_0_0.application has started. * [12/14/2010 1:39:08 PM] : Processing of deployment manifest has successfully completed. * [12/14/2010 1:39:08 PM] : Installation of the application has started. * [12/14/2010 1:39:12 PM] : Processing of application manifest has successfully completed. * [12/14/2010 1:39:17 PM] : Request of trust and detection of platform is complete. ERROR DETAILS Following errors were detected during this operation. * [12/14/2010 1:39:24 PM] System.Deployment.Application.InvalidDeploymentException (HashValidation) - File, Microsoft.Data.ConnectionUI.Dialog.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.FileComponent.Verify() 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.

Hi Whenriquez, From the error message "File, Microsoft.Data.ConnectionUI.Dialog.dll, has a different computed hash than specified in manifest.", I am sure you are right, the issue is caused by the Microsoft.Data.ConnectionUI.Dialog.dll is updated correctly, or the manifest file is not updated correctly. Based on my research, after updating to Service Package(SP) 2, the configuration setting for Microsoft.Data.ConnectionUI.Dialog.dll should like the following in the MSReportBuilder.exe.manifest: <dependentAssembly dependencyType="install" allowDelayedBinding="true" codebase="Microsoft.Data.ConnectionUI.Dialog.dll" size="402456"> <assemblyIdentity name="Microsoft.Data.ConnectionUI.Dialog" version="8.0.0.0" publicKeyToken="B03F5F7F11D50A3A" language="neutral" processorArchitecture="msil"></assemblyIdentity> The size for the Microsoft.Data.ConnectionUI.Dialog.dll.deploy is 402456. Could you please help to check if it is correct in your environment? Additionally, I uploaded the Microsoft.Data.ConnectionUI.Dialog.dll.deploy to http://cid-3c7e963ff6ccd974.office.live.com/self.aspx/.Public/Microsoft.Data.ConnectionUI.Dialog.dll.deploy You could Backup the Microsoft.Data.ConnectionUI.Dialog.dll.deploy Download the version I uploaded Replace the original file with the new one. Then check if it works. If you have any more questions, pleaes feel free to ask. Thanks, Jin Chen Jin Chen - MSFT

Hello Jin, Thanks for your reply. 1) I validate the entries in the MSReportBuilder.exe.manifest and they are as you stated. 2) The size for my Microsoft.Data.ConnectionUI.dll.deploy is 399,192. 3) I download the new file you posted with the size of 402,456 4) Replace the original file with the new one. The issue was NOT resolved.

Hi Whenriquez, There may have other files, which are not upgraded correclty too. I suppose the error message is a little different that the one we got before. Could you pleaes try to apply the hotfix again to check if the issue is solved? Thanks, Jin chenJin Chen - MSFT