Is this using the system.data.sqlite.dll library?

If you're using the network, you have to use the .ParseViaFramework (setting it to true) property.

Yes, I'm using System.Data.SQLite.dll I have already tried creating SQLiteConnection with parseViaFramework set to true, nothing changed.

Yes, exactly, that is the value passed to SQLiteConnection constructor. The same exception is thrown even if the path to database file in a redirected folder is hardcoded. It also doesn't seem to matter whether I'm using forward or backslashes in the path.

For the avoidance of doubt, and lets assume the server is called banana and the user is grape, what is the actual real path of the database? This would change for each user, but for a problematic one, would it be

\\banana\users\grape\profile\appdata\test1\test2\config.db

Is there a share on banana that the user grape can write to? eg, \\banana\documents ? If you set the path to that, does that work OK? This rules out network access issues, etc.

For one of our clients the path would be \bananaDocumentsgrapeAppDataRoamingconfig.db

For my test, I use the server that I have full admin rigths to. Using code there is no problem creating file \bananatest1test2Logslog1.log or \bananatest1test2file1.xml including creating folders to represent that path, but creating a SQLite db file throws an exception. Perhaps wrongly I assumed, it might be a SQLite bug, but I no longer have any ideas what to do with it.

Were you able to recreate that problem with a sample code I provided?

Not directly, as I don't run on a server - my code would return a local directory.

Was this test code then?

line 12 has private static string _filePath = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData), "test1", "test2", "config.db");

This is why I asked if it was in the test1\test2\config.db path - these folders are getting appended.

I assume this makes sense.

Yes, it was posted to show my approach to creating databases. For me it throws exception 100% of the time, when appdata folder is redirected to remote location. It doesn't matter whether I use SpecialFolder.ApplicationData, Desktop, MyPictures or any other, also if I use test1 and test2 tree, or just specify the special folder as a location to save the file.

I'm also sure, that at all times required paths existed.

OK, so on \\server\banana ensure there is a share the user grape can write to.

Set that database location temporarily in your code - \\server\grape\directory\config.db

No test1 or test2 combine statements - just 'hard code' that database location.

Theoretically, it should work. That'll at least prove if its your network, config, etc.

I've tried all that already - still doesn't work. Users have rights to write/read in that folder, also hardcoding different kinds of paths didn't solve the problem.

Two clients of ours have this problem already. One of them fixed it by 'changing the configuration of GPO profiles and changing local configuration', whatever it means. This worked for all but one computer for him, but he managed to get the last one working somehow anyway. He won't tell us any more details about what and why he did to make it work, but obviously he hasn't changed any of the code.

Also running the program as administrator solves the problem, but it's not acceptable solution for our clients - end users often can't have admin rights.

Do you have any more ideas about what to do next or how the problem could have been solved by the client? I have to have a solution soon, but I'm fairly stuck for about two weeks now.

system.data.sqlite.dll has no problems using a network path, apart from the additional switch I mentioned so the problem could be in the additional framework you're using? It's no SQLite bug though (system.data.sqlite.dll is just a wrapper which uses SQLite, so has nothing directly to do with SQLite...)

I wonder now whether it's Entity Framework related. Exception is beeing thrown when calling Database.Initialize(true), where Database object and it's Initialize method are defined in System.Data.Entity. I'm not sure is it more on SQLite or EF side.