On Wed, Feb 26, 2014 at 9:04 AM, Akintoye Olorode (BLOOMBERG/ 731 LEXIN) < aolor...@bloomberg.net> wrote:
> I recompiled with v 3.8.3.1 and enabled sqlite3_log (lines starting with > "LOG:" in output). Result below. Thanks. > > Thanks for the enhanced log. Very helpful! > LOG: os_win.c:33842: (33) > winTruncate2(D:\blp\wintrv\smartclient\applications\appinfo.db-shm) - > プãƒã‚»ã‚¹ã ¯ãƒ•ã‚¡ã‚¤ãƒ«ã «ã‚¢ã‚¯ã‚»ã‚¹ã §ã 㠾㠛ん。別ã > ®ãƒ—ãƒã‚»ã‚¹ã Œãƒ•ã‚¡ã‚¤ãƒ«ã ®ä¸€éƒ¨ã‚’ãƒãƒ E‚¯ã —ã, > extended-result-code: 1546 > TRUNCATE file=34, rc=SQLITE_IOERR_TRUNCATE > LOG: os_win.c:35002: (33) > winShmMap2(D:\blp\wintrv\smartclient\applications\appinfo.db) - > プãƒã‚»ã‚¹ã ¯ãƒ•ã‚¡ã‚¤ãƒ«ã «ã‚¢ã‚¯ã‚»ã‚¹ã §ã 㠾㠛ん。別ã > ®ãƒ—ãƒã‚»ã‚¹ã Œãƒ•ã‚¡ã‚¤ãƒ«ã ®ä¸€éƒ¨ã‚’ãƒãƒ E‚¯ã —ã ¦ã E, > extended-result-code: 4874 > What happened here is that SQLite tried to invoke SetEndOfFile() on a shared-memory file in order to change its size from 0 bytes to 32768 bytes. But it got back an SQLITE_LOCK_VIOLATION error (windows error code 33). I'm not sure why this is happening. The file had just been created - could it be that some anti-virus software had the file locked down in order to scan it somehow? The unreadable text is the error message that Windows provided via FormatMessageW(). Clearly it is not in English. Do you know what the locale setting is for the machine that is generating this error? -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
