'annotation' not loaded for item

dheider
Hello,

I got this error: [JavaScript Error: "'annotation' not loaded for item (6/1/PBL8RZ3J)"]. I cannot tell where it came from, but it seems to be keeping me from syncing my library.

The report ID is 180040610.

Thank you for your help.

  • dstillman Zotero Team
    (It's in the error report, but be sure to always mention when you're running the beta version.)

    Can you provide a Debug ID (different from a Report ID) for a sync that produces this error?

    After doing that, can you reproduce this after restarting Zotero? If so, can you provide another Debug ID for Zotero startup through getting this error, using the "Restart with Logging Enabled…" option?
  • dheider
    Got it, thanks for the heads up on the beta version.

    The first Debug ID (for a sync that produces this error) is: D190932652

    The second Debug ID (after restarting) is: D1102720053

    Thanks for your help!
  • erazlogo
    edited March 11, 2021
    looks like it's my issue as well
    https://forums.zotero.org/discussion/88283/beta-sync-broken-after-mass-conversion-from-linked-to-stored-files#latest
    I get "annotation' not loaded for item (2134683/1/WF794QSV)"
    Debug ID D458870208
    Debug ID after restart D1869582840.
  • dstillman Zotero Team
    @dheider: If you don't mind, could you upload your database to the DB Repair Tool and provide the Upload ID the tool gives you? You can ignore the download link the tool provides, which won't help, but the Upload ID will let us run some tests on the database to figure out how this might have happened. For @erazlogo this was due to a problem with "Convert Linked Files to Stored Files" and annotations in the beta, but it doesn't look like that's the case for you.
  • dheider
    Hi @dstillman thanks for your help. The Upload ID is 604b84a9d602e.
  • dstillman Zotero Team
    Thanks. We’ve actually pushed out a new beta that likely fixes any problems you were having. You should make a backup of your data directory and then upgrade to the latest version and see if that fixes this for you.
  • dheider
    @dstillman the problem is now resolved. Thanks for your help!

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.

This discussion has been closed.