Article ID: 2781227 - View products that this article applies to.
When you try to start the ClickOnce version of Microsoft SQL Server Report Builder for Microsoft SQL Server 2012 on a client computer, you may receive an error message that resembles the following:
Unable to retrieve application files. Files corrupt in deployment.
Additionally, when you click Details on the error message dialog box, you see detailed error information that resembles the following:
ERROR *********** + Exception occurred loading manifest from file MSReportBuilder.exe: the manifest may not be valid or the file could not be opened. + Cannot load internal manifest from component file. *****************ERROR DETAILS Following errors were detected during this operation. * [10/31/2012 9:25:34 AM] System.Deployment.Application.InvalidDeploymentException (ManifestLoad) - Exception occurred loading manifest from file MSReportBuilder.exe: the manifest may not be valid or the file could not be opened. - Source: System.Deployment - Stack trace: at System.Deployment.Application.Manifest.AssemblyManifest.ManifestLoadExceptionHelper(Exception exception, String filePath) at System.Deployment.Application.Manifest.AssemblyManifest.LoadFromInternalManifestFile(String filePath) at System.Deployment.Application.DownloadManager.ProcessDownloadedFile(Object sender, DownloadEventArgs e) at System.Deployment.Application.FileDownloader.DownloadModifiedEventHandler.Invoke(Object sender, DownloadEventArgs e) at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next) at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles() at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState) 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) --- Inner Exception --- System.Deployment.Application.DeploymentException (InvalidManifest) - Cannot load internal manifest from component file.
This issue occurs because the Microsoft .NET Framework 4 or a later version of the .NET Framework is not installed on the client computer.
To resolve this issue, install the .NET Framework 4. The following file is available for download from the Microsoft Download Center:
Download the .NET Framework 4 package now.
Collapse this imageExpand this image
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
(http://support.microsoft.com/kb/119591/ )How to obtain Microsoft support files from online services
Restart requirementYou must restart your computer after you install this package, and then restart the Report Builder ClickOnce application.
For more information about the .NET Framework, go to the following MSDN website:
Introduction to the .NET FrameworkFor more information about the prerequisites for SQL Server 2012 Report Builder, go to the following MSDN website:
Prerequisites for SQL Server 2012 Report Builder
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2781227 - Last Review: November 16, 2012 - Revision: 1.0