(1) It is possible that this has occurred on other versions of Windows, but I 
can only confirm that it has occurred on machines running Windows 10. The most 
recent cited occurrence was on Windows 10 Enterprise, version 1607, OS Build 
14393.1593
(2) We are using version 1.0.98.1.
(3) We aren't compiling SQLite so I don't think we are setting any compile-time 
options. We are using the following nuget package defined in our 
packages.config:
        <package id="System.Data.SQLite.Core" version="1.0.98.1" 
targetFramework="net452" />
(4) NTFS

Some other info that may or may not be useful:
- We are also seeing many occurrences of SQLite Error (5): Database is locked
- I assume they are pulled down as dependencies of the nuget package, but I am 
also seeing SQLiteInterop.dll v1.0.61.0, and Mono.Data.Sqlite.dll v1.0.61.0 in 
the bin of our solution.

Thanks,

Justin Esplin
Applications Dev II
Verisk Insurance Solutions - Xactware
Phone: +1.801.932.8039
jlesp...@verisk.com
http://www.verisk.com/insurance/



-----Original Message-----
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On 
Behalf Of Richard Hipp
Sent: Sunday, September 17, 2017 2:45 AM
To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org>
Subject: Re: [sqlite] Figuring out the Cause of SQLite Error 11: Corrupt 
Database

On 9/15/17, Esplin, Justin <jlesp...@verisk.com> wrote:
> I was able to access a computer which encountered these errors, about
> 10 minutes after they occurred. I ran "PRAGMA integrity_check" and it
> returned "ok". How/why would this have changed? I verified the user
> did not re-install our app or otherwise reconfigure the database.

You have not yet revealed to us:

(1) What operating system you are running on, including the specific version 
number
(2) What specific version number of SQLite that you are running
(3) What compile-time time options you are using
(4) What filesystem the database is stored on.

All of these things are important.

The only other time we have seen a problem like this, it turned out to be a bug 
in the file cache of the OS kernel, not in SQLite.  Just because SQLite is the 
software reporting the problem, does not necessarily mean that SQLite is the 
cause of the problem.  Details are important.  Please provide as much context 
as possible.
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__mailinglists.sqlite.org_cgi-2Dbin_mailman_listinfo_sqlite-2Dusers&d=DwIGaQ&c=birp9sjcGzT9DCP3EIAtLA&r=e6PxbQq9NdAJUZWHeJFpfhuVEDXWOo3XEghP1Z1arEs&m=07hq1KvkKn5WsEO9IVKerCbsYRYSpRRg-YhyIYSzxsA&s=cbIQ6kcghDi91HmDs_KkQOhHP7GmacRSYcgofZ60EFs&e=

________________________________

This email is intended solely for the recipient. It may contain privileged, 
proprietary or confidential information or material. If you are not the 
intended recipient, please delete this email and any attachments and notify the 
sender of the error.

________________________________

Xactware's opt-in mailing list allows you to receive Xactware News that is of 
interest to you. Visit my.xactware.com today to join or to update your email 
preferences!
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to