Hello Nathan, I'd install "Procmon" set it to filter just on the problem file (and journal files) and let the software run. When you get an error, you should see the details listed in procmon".
C Tuesday, February 8, 2011, 1:12:48 PM, you wrote: NB> I haven't tried that, but if we stop the application then restart it, NB> everything works again. That is until we get another Disk I/O error NB> which happens the next day. NB> I'm wondering if the virus scanner is blocking the database write. NB> On 2/8/2011 1:03 PM, Simon Slavin wrote: >> >> On 8 Feb 2011, at 5:59pm, Nathan Biggs wrote: >> >> > Once a day, not at the same time, we are getting a disk I/O error from >> > our application using SQLite. >> >> If you try to duplicate the database file do you get any kind of error >> then ? >> >> If not, use the command-line tool to run an integrity check: >> >> http://www.sqlite.org/pragma.html#pragma_integrity_check >> >> Simon. >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@sqlite.org >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> NB> _______________________________________________ NB> sqlite-users mailing list NB> sqlite-users@sqlite.org NB> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Best regards, Teg mailto:t...@djii.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
