[5.0 Beta]: Cannot open Zotero standalone with unknown error

till.grallert
I cannot open the most recent beta even after completely disabling the Firefox add-on. The beta produces and "unknown error" and the following message

Zotero.DBConnection.prototype.backupDatabase<@chrome://zotero/content/xpcom/db.js:1068:4
From previous event:
Zotero.Schema</this.updateSchema<@chrome://zotero/content/xpcom/schema.js:123:10
From previous event:
_initFull<@chrome://zotero/content/xpcom/zotero.js:572:25
From previous event:
this.init<@chrome://zotero/content/xpcom/zotero.js:394:11
From previous event:
ZoteroService@file:///Applications/Office-Research/Reference%20Manager/Zotero.app/Contents/Resources/components/zotero-service.js:343:4
XPCOMUtils__getFactory/factory.createInstance@resource://gre/modules/XPCOMUtils.jsm:387:19
@chrome://zotero/content/include.js:1:14
  • dstillman
    edited February 24, 2017
    Open Terminal, paste this command in (all in one line), and press Enter:

    /Applications/Office-Research/Reference\ Manager/Zotero.app/Contents/MacOS/zotero -ZoteroDebug

    That should start Zotero with a separate window with debug output. You should be able to submit the output and generate a Debug ID from that window.
  • till.grallert
    Thank you very much for the quick reply. The error seems to be slightly different:

    Database upgrade error

    TypeError: connection is undefined
    Zotero.DBConnection.prototype.backupDatabase<@chrome://zotero/content/xpcom/db.js:1068:4
    From previous event:
    Zotero.Schema</this.updateSchema<@chrome://zotero/content/xpcom/schema.js:123:10
    From previous event:
    _initFull<@chrome://zotero/content/xpcom/zotero.js:572:25
    From previous event:
    this.init<@chrome://zotero/content/xpcom/zotero.js:394:11
    From previous event:
    ZoteroService@file:///Applications/Office-Research/Reference%20Manager/Zotero.app/Contents/Resources/components/zotero-service.js:343:4
    XPCOMUtils__getFactory/factory.createInstance@resource://gre/modules/XPCOMUtils.jsm:387:19
    @chrome://zotero/content/include.js:1:14
  • dstillman
    Submit it to the server from that window and provide a Debug ID.
  • dstillman
    Actually, before you do that, upgrade to the latest build, 154, which fixes one related issue here.
  • asplundj
    I get the same error after updating to the latest beta today:

    I can't provide Debug ID because zotero won't start. I just get this message and the option to check for update or quit. It finds no update and then it just quits.

    Database upgrade error

    Win error 32 during operation move on file C:\Users\johaas\Zotero\zotero.sqlite.tmp (The process cannot access the file because it is being used by another process.

    )
    (No stack trace)
    From previous event:
    Zotero.Schema</this.updateSchema<@chrome://zotero/content/xpcom/schema.js:123:10
    From previous event:
    _initFull<@chrome://zotero/content/xpcom/zotero.js:572:25
    From previous event:
    this.init<@chrome://zotero/content/xpcom/zotero.js:394:11
    From previous event:
    ZoteroService@file:///C:/Users/johaas/AppData/Local/Zotero%20Standalone/components/zotero-service.js:343:4
    XPCOMUtils__getFactory/factory.createInstance@resource://gre/modules/XPCOMUtils.jsm:326:19
    @chrome://zotero/content/include.js:1:14
  • dstillman
    edited February 26, 2017
    @asplundj: Sorry about that — try the latest build, 155.
  • asplundj
    Thanks, 155 works
Sign In or Register to comment.