Error "state.registry.registry[blobjr.strings.first_blob] is undefined"

benni3081983
Suddenly when I try to insert a citation in Word for Mac this error occurs: 'state.registry.registry[blobjr.strings.first_blob] is undefined' and Zotero isn't putting in the citation or the reference. I'm in the middle of a big project and having quite a situation here ;-) Can anybody maybe help me? Thanks, Ben
  • dstillman Zotero Team
    Report ID?
  • benni3081983
    Report ID is 1666893257. Thank you
  • dstillman Zotero Team
    4.0.29.11
    This is an outdated version of Zotero. You should've been auto-upgraded, but you can install the latest version from the download page.
  • benni3081983
    Thank you. I updated and still the same problem. The new report ID is 1854847368
  • benni3081983
    I just opened the File on PC, with another synched version of Zotero. Same error here. The report id the PC is 1854847368
  • benni3081983
    Oh, same id... ;-) Sorry, the ID for the PC is 1982009588
  • dstillman Zotero Team
    [JavaScript Error: "value is null" {file: "chrome://zotero/content/xpcom/citeproc.js" line: 8012}]
    This is likely due to a bug in the citation processor in that version. A few options:

    - Follow the Debugging Broken Documents steps.

    - Install the Zotero 5.0 Beta, which includes a newer version of the processor.

    - Install the latest Propachi plugin, which updates the citation processor, by downloading the XPI and dragging it into the Add-ons pane in Zotero. If you do this, you can uninstall it when you upgrade to Zotero 5.0.
  • benni3081983
    Unfortunately, none of the above-mentioned things helped. When I installed Zotero 5 Beta and started it, the following error appears:

    Error: Error(s) encountered during statement execution: database disk image is malformed
    ConnectionData.prototype<._executeStatement/pending<.handleCompletion@resource://gre/modules/Sqlite.jsm:807:25
    From previous event:
    Zotero.Schema</this.updateSchema<@chrome://zotero/content/xpcom/schema.js:136:24
    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/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

    Any further ideas? Im devastated...
  • dstillman Zotero Team
    edited May 4, 2017
    Unless this is happening in a new empty document as well, it's not really possible for the Debugging Broken Documents not to work — the point is that you're narrowing down a copy of the document until you find the problematic citation.
  • dstillman Zotero Team
    However, if you're getting that error trying to upgrade to 5.0, you should definitely check your database integrity from the Advanced → Files and Folders pane of the Zotero preferences. (And let us know if it doesn't find a problem.)
  • fbennett
    (I'll be watching this thread, just in case a processor issue is involved.)
  • benni3081983
    Thank you very much for your help to this point. I will try all the steps in den Debugging Broken Documents file and tell you the result. About that error in Version 5.0, It crashes after the error, so I can not my database integrity. But on my PC I have still version 4 on my PC. Maybe there i can check my database integrity,
  • benni3081983
    I checked the database integrity and it was corrupt. I used the repair tool (Upload ID 590b146a52841). But unfortunately it did not solve my problem. I will continue now with the Debugging Broken Documents file
  • benni3081983
    So I narrowed it down. Deleting the bibliography made the error disappear. But how could I get now a bibliography again?
  • benni3081983
    Now, after deleting the bibliography I get a different error with report ID 1322413355
  • dstillman Zotero Team
    I used the repair tool (Upload ID 590b146a52841). But unfortunately it did not solve my problem.
    Does the database integrity check now pass without errors, though?
  • dstillman Zotero Team
    If so, you should again try upgrading to the 5.0 Beta. You can almost certainly fix this with the Debugging Broken Documents steps, but 5.0 is more resilient to document errors in various ways.

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.