ReportViewer 2010, IO.Exception \

Question

I have a problem that, in my opinion, is based on a machine, however I would like to know how to solve it if it appears on another machine.

I developed a WPF project (.NET 4) that I am installing with Installshield LE . A prerequisite for the program is also ReportViewer 2010, which I install earlier (if necessary).

I made the installation of the program to the following machines:

• Windows 7 64-bit SP1
• Windows 7 32-bit
• Windows XP SP3 (Case 1)
• Windows XP SP3 (Case 2)
• Windows XP SP3 (Case 3)

In all of the above machines, my reports work fine except for # 5 (case 3), where I get the following error:

  Microsoft.Reporting.WinForms.LocalProcessingException: An error occurred during local report processing. ---> Microsoft.Reporting.DefinitionInvalidException: The definition of the report '' is invalid. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing. ---> System.IO.IOException: The process cannot access the file 'C:\Documents and Settings\<WindowsLogOnName>\Local Settings\Temp\expression_host_2e380b8068bb4ef5a53225faab4ebcb4.dll' because it is being used by another process. 

All machines fall into the same database, and the report that I am testing is the same in each case.

Has anyone encountered this error before and has any hint?

Answer 1

I have heard that malware and antivirus programs block access to localreport temp files, because the expressions in the report are mostly VBScript. Try disabling them and try again. Here is the only source I found in this .

Otherwise, try a few things:

• Check the permissions of both the RDLC and temporary files. This requires access to NETWORK SERVICES, as well as to an ASP.NET user account. Make sure that it has FULL CONTROL, because it needs execution rights, as well as read and write.
• Check disk space
• Try using a process monitor, such as Process Explorer, to see if any other programs are held in the file descriptor.
• Try deleting the temporary file and restarting or reusing the application pool.
• Perhaps view the event viewer to learn more about the problem?

If this does not work, you might be better off reporting an MS problem directly.