New error on Windows 10: "Can't write to database. Unable to open database file [14]"

[1984btgn]

I use a few different wikis and this error is coming up for every one. Never happened before, up to a few weeks ago. The 'Reconnect' option under 'Maintenance' gives the same error. Occurs on versions 2.2, 2.3, and 2.4.

From the error log:

Version: 'wikidPad 2.3rc02' Session start: 2021-02-21 00:19:26
Traceback (most recent call last):
File "pwiki\wikidata\WikiDataManager.pyo", line 459, in connect
File "pwiki\wikidata\WikiDataManager.pyo", line 259, in call
File "pwiki\wikidata\original_sqlite\WikiData.pyo", line 207, in connect
DbWriteAccessError: unable to open database file [14]
Traceback (most recent call last):
File "pwiki\Configuration.pyo", line 508, in save
File "pwiki\Configuration.pyo", line 274, in save
IOError: [Errno 9] Bad file descriptor

Anyone else having this issue or had any luck solving it?

[BjornFJohansson]

Do you use the original sqlite or compact sqlite? For anyone who sees this, never use compact!

[vashnt707]

I have been using compact sqlite in Windows for years and faced no issues. Any reason not to use compact? Because it is custom wrapped?

[1984btgn]

@BjornFJohansson I'm using the original sqlite. Under 'About' it says I'm using version 3.6.15.

[BjornFJohansson]

@vashnt707 The original sqlite keeps each page as a text file in the file system. In case of corruption, these can always be used to recreate the DB. The compact sqlite file can be corrupted beyond salvation.

[BjornFJohansson]

@1984btgn then perhaps rebuild might help? I used to have RAM problems that led to frequent crashes and corruptions. I used to replace the "wikiovw.sli" file with one from an empty db and delete the wikiovw.sli-journal file. Then a rebuild and the wiki is as good as new.

[1984btgn]

@BjornFJohansson Thank you so much for your help. After some more poking around with the issue this morning, I discovered the problem was in Windows Security > Virus & Threat Protection > Ransomware Protection. Windows had stuck the program in read-only mode and not notified me about it. Seems to be working now though. Thanks all! :)