Thank you Richard. I have full rights to that directory tree and to the main database file, but it turns out the journal was created by a service, and so the journal was only writable by the service account. That solved it.
Thanks again -- one small stress removed from my life :) > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 19, 2007 12:49 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Trying to understand SQLITE3_BUSY > > "Doug" <[EMAIL PROTECTED]> wrote: > > Well, I'm stuck. If I use the CLI I get: > > > > D:\dev\SQLite\3_4_1\Bin>sqlite3 myproj.db > > SQLite version 3.4.1 > > Enter ".help" for instructions > > sqlite> pragma synchronous=0; > > SQL error: database is locked > > sqlite> .quit > > > > However, I find I can copy the database and journal and do the same thing on > > the copy and everything works perfectly (journal file disappears). It would > > appear something does have a lock on the original file. I've moved it twice > > to different directories (to ensure my app, which isn't running, can't find > > it). I've rebooted twice (it's Windows), and run SysInternal's Handle app > > which shows all open files, and this file isn't open by anything. Renaming > > the original also has no effect. > > > > Can a file lock survive a reboot? > > > > Do you have read and write permission on all the files involved > and on the folder containing them? > -- > D. Richard Hipp <[EMAIL PROTECTED]> > > > ---------------------------------------------------------------------------- - > To unsubscribe, send email to [EMAIL PROTECTED] > ---------------------------------------------------------------------------- - ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
