SQLite.Interop.dll: Exception 0xc00000fd
(1) By Florian (Flohack) on 2021-06-11 08:49:47 [link] [source]
Hi guys, I have no idea why, but a customer reports receiving that error code in a Windows Server 2016 VM during a sequence of INSERT statements, and, as there is no stack trace from that unmanaged part, I have no clue whats happening.
Does that error code even make any sense, can I look this up in the sources, for potential reasons? Also, are there debug builds available for the Interop or do we need to rebuild them ourselves?
Thanks BR Florian
(2) By mistachkin on 2021-06-11 16:13:13 in reply to 1 [link] [source]
The root cause of this will be extremely difficult to pin down without more details on the observed behavior, e.g. example code, example schema, stack traces, etc.
(3) By Florian (Flohack) on 2021-06-15 08:06:57 in reply to 2 [link] [source]
Alright, for the stacktrace: what would be my best way to debug released code (from Nuget), do you guy have debug builds available?
The other thing is that providing a sample code is next to impossible since it happens only in a customer´s Azure environment, and we are not able to access those or receive data files for analyis, nor give data files away. We might be able to get a dummy database if it crashes in the same way as with the production Db.
(4) By Florian (Flohack) on 2021-06-24 13:35:23 in reply to 2 [link] [source]
we have another now that also comes just out of nowhere, its basically
System.Data.SQLite.SQLiteException (0x80004005): unable to open database file
in the middle of a transaction even.
There are very low chances that the Db file just disappears under the hood. So the question is, in which cases that errors are being thrown? And how can I obtain a debug build for a released version including the unmanaged lib? Thanks!
(5) By Florian (Flohack) on 2021-08-24 07:55:11 in reply to 2 [source]
coming back to this, I got again a customer with that error, the application just closes, we do not get any useful error except that:
Event Viewer log:
So I ask again, how could I obtain a debug build with more information for that exact version of SQLite?
Faulting application name: xxx.exe, version: yy, time stamp: 0x5f7b23b7 Faulting module name: SQLite.Interop.dll, version: 184.108.40.206, time stamp: 0x59162856 Exception code: 0xc00000fd Fault offset: 0x00000000000c7dae Faulting process id: 0xbbc Faulting application start time: 0x01d7893dc9d15d5e Faulting application path: C:\Program Files (x86)\xxx\xxx.exe Faulting module path: C:\Program Files (x86)\xxx\x64\SQLite.Interop.dll
(6) By anonymous on 2021-08-24 10:52:14 in reply to 5 [link] [source]
The exception code
0xC00000FD corresponds to
this MSDN reference, so at least this case is a very general problem not
necessarily originating from