This project makes use of Eagle, provided by Mistachkin Systems.
Eagle: Secure Software Automation
Ticket Hash: bbdda6eae207d8f109b8065657e290be5302354b
Title: unable to open database file on a local network
Status: Closed Type: Documentation
Severity: Important Priority: Medium
Subsystem: Convert Resolution: Workaround
Last Modified: 2013-05-30 00:47:35
Version Found In:
User Comments:
anonymous added on 2013-05-25 16:23:52: (text/x-fossil-plain)
If the database is accessed from the local network the following error is returned: "SQLiteException : unable to open database file"
The address of the database as: "\\Network\Folder"

It worked with version 1.0.84

The error message is returned here :
Dim oCommand As New SQLiteCommand(stSQL)
Dim oDataAdapter As New SQLiteDataAdapter(oCommand)
oCommand.Connection() = oConnection
oDataAdapter.Fill(oDataset, stTableDTS)     '=> Error

anonymous (claiming to be Jason) added on 2013-05-25 19:52:43: (text/x-fossil-plain)
I can confirm this issue exists... upgraded this afternoon from .85 to .86 and can no longer connect to my database running off a vmshare.

mistachkin added on 2013-05-25 21:06:45: (text/x-fossil-plain)
There are several workarounds to this issue:

1. Double the leading two backslashes in the file name
   (e.g. "\\\\network\share\file.db").

2. Use a mapped drive letter.

3. Use the SQLiteConnection constructor that takes the parseViaFramework
   boolean argument and pass 'true' for that argument.

The root cause of this issue is the new connection string parsing algorithm
works.  Backslash is now the escape character when it is followed by another
reserved character.

mistachkin added on 2013-05-30 00:47:35: (text/x-fossil-plain)
I've added an environment variable that can be set to disable use of the new
connection string parsing algorithm named "No_SQLiteConnectionNewParser".

Also see check-in [4f933521a1].