Can't access my library

I keep getting this error. Just updated the app and it happened afterward. I've tried restarting my computer and uninstalling and reinstalling the program and nothing is working. What do I do?

Database upgrade error

Error: Error(s) encountered during statement execution: disk I/O error [QUERY: PRAGMA foreign_key_check] [PARAMS: ] [ERROR: disk I/O error]
Zotero.DBConnection.prototype.queryAsync<@chrome://zotero/content/xpcom/db.js:669:13
From previous event:
Zotero.Schema</this.updateSchema/updated<@chrome://zotero/content/xpcom/schema.js:206:17
  • dstillman Zotero Team
    edited February 27, 2021
    Do you have your Zotero data directory on an external disk, in a cloud storage folder, or on a network share or server-mounted folder? This could potentially also be caused by security software on your system.

    A "disk I/O error" is a general problem with reading the disk. It's a problem outside of Zotero and unfortunately not something we can do anything about.
  • Nothing has changed on my computer since I used Zotero yesterday other than the update that ran for zotero this morning. Ever since then I can't open the program. The error box pops up and I can't do anything in the program, so I can't check where my data directory is (as the link you provided suggested) since I can't open the program. Could this have anything to do with trying to use zotero in a google doc for the first time yesterday? I have uninstalled and reinstalled the program twice so I really don't know what else to do.
  • Can you generate a Debug ID for Zotero startup, using the "Restart with Logging Enabled…" option?
  • I tried following the directions you linked, but for:

    "In the Help menu, go to Debug Output Logging and select Enable, or use “Restart with Logging Enabled…” to generate debug output from Zotero startup. (If you're not able to access the Help menu, see Reporting Startup Errors instead.)"

    I cannot get to the help menu, so I clicked on the "Reporting Startup Errors" link and followed those directions, but the debug output comes up completely blank.
  • What exactly did you try? What OS is this?
  • Windows 10.

    I typed ""C:\Program Files (x86)\Zotero\zotero.exe" -ZoteroDebug" into Run

    Nothing came up. But then I saw to try ""C:\Program Files (x86)\Zotero\zotero.exe" -jsconsole" and these came up:

    [JavaScript Warning: "unreachable code after return statement" {file: "resource://zotero/loader.jsm -> resource://zotero/bluebird/util.js" line: 205 column 4 source: " eval(obj);
    "}]

    [JavaScript Error: "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [mozIStorageService.backupDatabaseFile]" {file: "chrome://zotero/content/xpcom/db.js" line: 1010}]

    [JavaScript Error: "Error(s) encountered during statement execution: disk I/O error [QUERY: PRAGMA foreign_key_check] [PARAMS: ] [ERROR: disk I/O error]" {file: "chrome://zotero/content/xpcom/db.js" line: 699}]

    [JavaScript Error: "Error(s) encountered during statement execution: disk I/O error [QUERY: PRAGMA foreign_key_check] [PARAMS: ] [ERROR: disk I/O error]" {file: "chrome://zotero/content/xpcom/db.js" line: 699}]
  • dstillman Zotero Team
    edited February 27, 2021
    No separate Zotero logging window comes up if you use -ZoteroDebug, or something comes up but it's empty?

    Can you try with -ZoteroDebugText -console instead? If that produces output, can you email it to us at support@zotero.org with a link to this thread?
  • Something comes up but its empty. I did the other one and will email
  • dstillman Zotero Team
    edited February 27, 2021
    Using data directory C:\Users\[…]\Zotero
    OK, so your data directory is in the default location.

    I'm afraid there's not really anything we can tell you here other than that either something on your system (like security software) is interfering with Zotero or there's a genuine problem with your disk. You should see if you're even able to copy the zotero.sqlite file in your Zotero data directory to another location or whether you get an error doing so. If you are able to copy it, you can upload it to the DB Repair Tool just to see whether it's a valid database — you can ignore the download link the tool provides unless it tells you that it found errors.

This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.

Sign In or Register to comment.