All geek questions in one place

Internal error in .NET Runtime?

Possible duplicate:
Application Error with "Internal Error in .NET Runtime"

I have a windows service that runs 24x7. At regular intervals, the service will contact SQL Server to process some data. In some cases, the SQL link will stop working. All the code that processes this is in the try / catch block. However, my service is still down. When I check the event log in the box on which my service is running, I see the following error:

"The process was aborted due to an internal error in the .NET Runtime on IP 66587CB5 (664E0000) with exit code 80131506."

Is this really a mistake in the .NET framework by bringing my service down, or is it in response to my SQL timeout error?

I am using .NET 4.

Thank you very much.

+4
source share
2 answers

Is this really a bug in the .NET framework bringing my service, or is it in response to my SQL timeout error?

This cannot be answered. This is a structure error, but may occur due to an error in unmanaged (!) Code in the database driver. If the database is SQL Server, this is unlikely - if it is an oracle, there are significant driver errors;) In unmanaged code.

It CANNOT be the result of a managed code problem unless a runtime problem exists. The whole point of pure managed code is that runtime integrity is isolated. Well, one of the reasons.

I would point fingers at an unmanaged code - or at a faulty RAM.

+2
source

Naturally, you will need a few more error logs - we had something very similar to one of our sites, although we caught errors globally (global.asax), there are some exceptions (stream interruption, one) that will bypass normal error handling .

Perhaps this question on handling global exclusions in Windows services might be useful in finding / getting more information?

+3
source

Source: https://habr.com/ru/post/1387028/

More articles:


All Articles