If you're using impersonation, you'll run into problems doing any
updates during the impersonation when sqlite tries to create any
temporary files or reopen any it has closed.
You can use Process Monitor from Sysinternals (now Microsoft) to see
exactly what the failure is with what file.
On 8/15/2012 10:19 AM, markus ruettimann wrote:
Hi,
We are facing problems when the sqlite database () is used within an
application that runs as a Win7 service under the local system account.
The application is written in Java and we use the sqlite-jdbc-3.7.2 JDBC
driver.
How ever we can create a new database, reading and writing to it withount
any problem. The only thing that is not working is the ATTACH DATABASE SQL
command. We constantly receive a CAN_NOT_OPEN error code.
When we start the same application under a local user everything works
fine. I have to add the both databases that are to be attached are in the
same folder and have been created by the Application itself. There are no
access restrictions on the database folders or files.
Does anyone know about this and / or has a solution?
Kind regards
Markus
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
