Possible Duplicate:
Application Crashes With “Internal Error In The .NET Runtime”
I have a Windows service that runs 24×7. On a regular interval the service will communicate with a SQL Server to process some data. On occasion, the SQL communication will time out. All the code that handles this is in a try/catch block. Yet, my service is still brought down. When I check the Event Log on the box running my service, I see the following error:
“The process was terminated due to an internal error in the .NET Runtime at IP 66587CB5 (664E0000) with exit code 80131506”.
Is this really an error in the .NET framework bringing my service down, or is this in response to my SQL timeout error?
I’m using .NET 4.
Thanks very much.
This can not be answered. It is a framework error, buti t could be occuring due to an error in unmanaged (!) code in a database driver. If the database is SQL Server, this is highly unlikely – if it is oracle, there are significant bugs the drivers 😉 In not managed code.
It can NOT be the result of a managed code issue unless a runtime issue exists – the whole sense of pure managed code is that the runtime integrity is isolated. Well, one reason.
I would point my fingers at either unmanaged code – or defective RAM.