The application requires that the assembly microsoft.reportviewer.processingObjectModel version 11.0.0.0 be installed in the global assembly cache

Question

I have a small Windows forms application created in Visual Studio 2012 that uses ReportViewer version 11.0.0.0.

The target application framework is .NET 4.0, and the deployment method is ClickOnce

It installs on my computer, but on client computers, intallation fails with an error

The application requires the assembly microsoft.reportviewer.processingObjectModel version 11.0.0.0 to be installed in the global assembly cache.

On client computers, I installed

• .NET 4.0
• ReportViewer 2010
• Microsoft Report Viewer 2012 Runtime CTP
• SQLSYSCLRTYPES.msi

in the settings of the project application files, I set microsoft.reportviewer.processingObjectModel to publish the status to Enable (Auto) , in the links I also set the Copy local property to True .

What am I missing?

I even followed the instructions here http://msdn.microsoft.com/en-us/library/ms251723.aspx

Answer 1

you are missing the ProcessingObjectModel.dll file, find version 11.0.0.0 in the gac assembly C: \ windows \ assembly \ GAC_MSIL \ Microsoft.ReportViewer.ProcessingObjectModel and add it to the bin directory.

Answer 2

Here is the (possibly) best way to deal with this problem ... without downloading or installing any additional features. This worked with Visual Studio 2012 (Ultimate)

• Go to the main project in your solution (default project / statup)
• Right-click and select Properties / Select "Your Project" → Project → Properties
• Click the Publish tab to view publishing options.
• Go to "Installation and Settings Mode" → Click "Application Files" and a dialog box will open
• Go down and look for the items defined with "Publication Status"> Prerequisite
• You will find ReportViewer and several other preconditioned files.
• Change all published statuses to "Include" in the drop-down list
• I know that you only need ReportViewer Only, but this will fix the other potential problems that I have encountered.
• Now all the necessary files will be added to your installation, and it will be useful!
• For convenience, you can change the desktop icon in the section "Installation and Settings" → "Options"> "Mainfests"> "Create a short clipping of the desktop"

Answer 3

We had the same problem, but the fact is that it automatically adds it to the links (microsoft.reportviewer.processingObjectModel), if it EXCLUDES it from the properties of the publication (properties-> publish-> application files), it can fix it.

Answer 4

The best option would be to install the Microsoft Report Viewer 2010 SP1 redistributable package at: http://www.microsoft.com/en-us/download/details.aspx?id=6610

Your users will also need to install this package. If you just copy and paste the MS DLL, you will have to relocate it every time you update your application.

Answer 5

It depends on the type of installation you are using, but basically, it means that the required library is not on your server or computer. So that the application can be downloaded from the server (in the client-server architecture), you need to include the file in the project.

• Go to your application version and find the "Publish" tab
• Click "Application Files"
• In the next dialog box, select to enable all the libraries that you want to enable (or which are necessary to run your application on the client machine and click "OK")
• Create an application and publish it on the server.

I hope this works for you, it works for me in Visual Studio 2010 Professional

Answer 6

In the case of Windows 10, it will not work with the installation of Microsoft Report Viewer 2010 SP1, as described by user1236560. First, you need to establish the prerequisites for SQL Server management objects (SQLSysClrTypes.msi), which you must choose between x86 and x64 depending on your hardware. You can find it at: http://origin.www.ms.akadns.net/downloads/en/details.aspx?FamilyID=16BC778C-357B-46E9-8356-D575903AC831

After that, you need to install MICROSOFT® REPORT VIEWER 2012 RUNTIME, which you can find at: https://www.microsoft.com/en-us/download/details.aspx?id=35747

Both of these packages must be installed.

Answer 7

I ran into this error

---

System update required

Cannot install or run the application. The application requires that the assembly Microsoft.ReportViewer.ProcessingObjectModel version 11.0.0.0 be installed in the global assembly cache (GAC).

Contact your system administrator.

---

This error appeared when installing an application from Visual Studio that I am one of the clients

I have Visual Studio 2015 and Microsoft SQL Server 2014, and I did not know about Crystal Reports and other related materials. I am checking the version of my .NET Framework version 4.6.2.

I have several extension files and redistributable files uploaded and still not solving the problem.

I don’t know if I solve the problem as a whole, but I am able to successfully install the application

so I downloaded and installed ff:

• SAP Crystal Report for Visual Studio 2015 (the last one to be sure)
• Microsoft System CLR Types for Microsoft SQL Server 2012
• Microsoft Report Viewer 2012 runtime.

the problem took me about two days to avoid trouble, be careful when downloading and installing extension files and distributed files, because it will also miss some space.

Answer 8

If you use WinForms, it seems pointless to worry about installing this DLL in the GAC when it is used for a report viewer that is deployed with a click-once. This is not a large file, and you probably use it as a means of viewing reports in a form, nothing more. One possible solution is to:

• In Visual Studio, go to the link in the project for the Microsoft.ReportViewer.ProcessingObjectModel assembly and find the folder path for this assembly. Mine was version 12, so my file path was C:\windows\assembly\GAC_MSIL\Microsoft.ReportViewer.ProcessingObjectModel\12.0.0.0__89845dcd8080cc91
• Copy the path to the file of the folder in which the assembly is located and delete the link from your project (right-click the link and select "Delete").
• Win + R to get a Run prompt. Insert the path to the folder there and go directly to the folder of this DLL.
• To find the DLL, it should be the only file in this folder and copy it to the Visual Studio project folder. You do not have to worry about 100 kilobytes of extra disk space and I don’t think this DLL is needed for updating.
• Return to Visual Studio, right-click the link, add the link and find this DLL in the project folder. After adding the link, make sure the Copy Local property is set to true.
• Clean and rebuild, test the application on your local computer, and then deploy your ClickOnce again.

Now, when users install your application using ClickOnce, the link will not link to the GAC at all, and there will be no need to rely on the process of checking / installing the necessary components for this DLL, since you included it directly in your published application.

Answer 9

The best answer:

Here is the (possibly) best way to deal with this problem ... without downloading or installing any additional features. This worked with Visual Studio 2012 (Ultimate)

• Go to the main project of your solution (default project / statup)
• Right-click and select Properties / Select "Your Project" → Project → Properties
• Click the Publish tab to view publishing options.
• Go to the "Installation and Settings Mode" section → Click on "Application Files" and a dialog box will open.
• Go down and look for the items specified in the "Publish Status"> Prerequisite section. You will find ReportViewer and several other files configured for the prerequisites.
• Change all published statuses to "Include" in the drop-down list.

I know that you only need ReportViewer Only, but it will fix other potential problems that I encountered Now all the necessary files will be added to your installation, and it will be useful!

For convenience, you can change the desktop icon in the section "Installation and Settings" → "Options"> "Mainfests"> "Create a short clipping of the desktop"

This reduced all headaches.