|00:47||• Closed ticket [bbdda6eae2]: unable to open database file on a local network plus 4 other changes artifact: 1bc4445158 user: mistachkin|
|00:44||Add DateTimeFormatString connection string property to allow the DateTime format string used for all parsing and formatting to be overridden. Disable use of the new connection string parsing algorithm when the No_SQLiteConnectionNewParser environment variable is set. Pursuant to [bbdda6eae2]. check-in: 4f933521a1 user: mistachkin tags: trunk|
|21:21||• Ticket [bbdda6eae2] unable to open database file on a local network status still Open with 3 other changes artifact: e1b8d21f66 user: mistachkin|
|21:10||Mark the connection string parsing algorithm change as potentially incompatible. Pursuant to ticket [bbdda6eae2]. check-in: 5567024344 user: mistachkin tags: trunk|
|21:06||• Ticket [bbdda6eae2] unable to open database file on a local network status still Open with 5 other changes artifact: 161221be43 user: mistachkin|
|19:52||• Ticket [bbdda6eae2]: 7 changes artifact: 551c52d2cf user: anonymous|
|16:23||• New ticket [bbdda6eae2]. artifact: bb8844ebb5 user: anonymous|
|Title:||unable to open database file on a local network|
|Last Modified:||2013-05-30 00:47:35|
|Version Found In:||22.214.171.124|
anonymous added on 2013-05-25 16:23:52:
Hello, 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 oDataAdapter.Dispose() oCommand.Dispose()
anonymous (claiming to be Jason) added on 2013-05-25 19:52:43:
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:
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:
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].