Microsoft.ReportingServices.ReportViewerControl.Winform Throwing FatalExecutionEngineError

Mark Smith 10

I have a Visual Studio project using the NuGet package Microsoft.ReportingServices.ReportViewerControl.Winform

that is throwing exceptions. The project is using .Net Framework 4.8. The report is reading one SQL table.

I've sent multiple messages to the package owner using NuGet, and have not received a response, I'm therefore trying this forum to get help.

The exception is thrown anytime I have an object in the header or footer of a report, and move off the first page of the report. For example, if I add a page number to the report footer, the report viewer throws an exception. When there is no object in the header or footer the viewer works fine.

The full details of the exception is:

Managed Debugging Assistant 'FatalExecutionEngineError' 
  Message=Managed Debugging Assistant 'FatalExecutionEngineError' : 'The runtime has encountered a fatal error. The address of the error was at 0x7aa7ab2f, on thread 0x8184. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.'

Does anyone know how to solve this issue? Or how to contact the NuGet package owner?

Thank you.

S M Roy 10 Reputation points

2023-11-20T12:02:45.3133333+00:00

Hi Mark, have you had anymore insight into this problem? Our users suddenly started getting this error on an application that has been in production and stable for over a month. They're in the process of getting windows 10 updates which I believe is having an impact here. Edited to say that we're on .Net Framework 4.8.
Mark Smith 10 Reputation points

2023-11-20T14:39:59.01+00:00

The problem continues for me. At this point I've given up and moved onto another project. My hope is that enough other people have the same issue, then Microsoft will looking into the bug.

A little background, we too had a working point of sale system for many years. The reports are used monthly for by finance. Then the reports just stopped. I wrote a simple program, to troubleshoot where the problem was coming from. To me the problem is with 'built-in' field (like page numbers) in the header or footer. When I removed the information from the header and footer, the reports work correctly.

Mark
S M Roy 10 Reputation points

2023-11-20T14:54:51.9666667+00:00

What's odd is that everything was working fine until last week. We're still looking into it. Right now, the prime suspect is a Trellix (formerly McAfee) upgrade that was installed on the users machines recently.
Mark Smith 10 Reputation points

2023-11-23T13:46:43.7266667+00:00

I can confirm that Trellix (McAfee) is causing the problem.

We also use Trellix End Point Security. I've uninstalled it from a couple of our computers and the reporting exception stopped, and the reports work. I'm not sure how/why Trellix is causing the exception.

My company is in the process of switching to a new security software and dropping Trellix. Not because of this report problem. So I'm not going to troubleshoot anymore on this. Just moving the effected users to the new security software. and getting on with life.

Mark
S M Roy 10 Reputation points

2023-11-23T15:03:39.6066667+00:00

Yup, I can confirm it too. My company pushed a policy to work around it. I don't know the details except that it was End Point Security also.

1 answer

AniyaTang-MSFT 12,441 Reputation points Microsoft Vendor

2023-11-07T01:49:04.3066667+00:00

Hi @Mark Smith

The fatalExecutionEngineError managed debugging assistant (MDA) is activated when a fatal error in the common language runtime (CLR) has been detected. The process will be terminated. This is most often caused by data corruption, which can be caused by a number of problems, such as calls to malformed platform invoke functions and passing invalid data to the CLR. For more details, you can refer to this document: fatalExecutionEngineError MDA.

For report viewer control integration and NuGet packages you can check out these links:

Integrate Reporting Services Using the Report Viewer Controls - Get Started,

Microsoft.ReportingServices.ReportViewerControl.Winforms: https://www.nuget.org/packages/Microsoft.ReportingServices.ReportViewerControl.WinForms/.

If the answer is helpful, please click Accept Answer and Up-Vote for the same. If you have any questions, please feel free to let me know.

Best regards,

Aniya
Please sign in to rate this answer.
Mark Smith 10 Reputation points

2023-11-07T13:32:23.74+00:00

The CLR bug must be inside the Microsoft.ReportingServices.ReportViewerControl.Winforms NuGet package. I've built a very simple Visual Studio project. One form with the viewer control, and one report. When the report has a header and footer with a parameter the program throws the exception. When there is no header or footer with a parameter the report works, and there is no exception thrown. It is therefore my belief the problem is inside the control. It's a consistent reproducible error.

I've tried contacting the package owner multiple times through the NuGet site, but I have not received a reply. The owners of the NuGet package are Microsoft & SQLRSNuget.

Any help or recommendations are appreciated.

AniyaTang-MSFT 12,441 Reputation points Microsoft Vendor

2023-11-09T05:50:56+00:00

Hi @Mark Smith

Are your parameters set correctly? Is there an error in placing parameters in the report body?

Here is an example about passing parameters to rdlc report maybe you can check it out: https://www.youtube.com/watch?v=PNR5Zbh4QcA.

If everything is correct, such issues are often difficult to resolve since we cannot check the status of your server in the forum. I suggest you consider using the phone support service provided by Microsoft which can usually help you resolve your issue.
https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers
https://support.microsoft.com/en-us/supportforbusiness/productselection

Best regards,

Aniya

Mark Smith 10 Reputation points

2023-11-09T14:27:48+00:00

Hello,

The report parameter is not the problem. The parameter is put into a textbox in the header so the report header text is dynamic based on the options selected by the users. For example, it will show the date range selected for by the user.

If it helps understanding the problem, forget about report parameter. I've removed the parameter from the header.

The viewer will throw the exception with only the 'built-in' page number in the header or footer. When the report view is moved past the first page. If there was an issue with the data or server, would you not expect the error on the single page report and a multiple page report. Also, the report works fine without a page number in the header or footer, this there was a server issue then I'd expect the problem with and without a page number. The page number in the report footer should be independent of the data reported.

I feel the problem is inside the NuGet package.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Microsoft.ReportingServices.ReportViewerControl.Winform Throwing FatalExecutionEngineError

1 answer

Your answer