Syncing error...with issue number

I added a few items to our group library today. Once I added them this issue popped up. Issue # 1621712463 Three of my colleagues have had corrupted libraries today (1st time in 7 months of using zotero) while syncing to the group site. I am not sure if they are related, but I thought I would mention it. I also dont know if this is related to my previously posted problem (http://forums.zotero.org/discussion/13421/syncing-tags-content-not-showin-up/).
  • Three of my colleagues have had corrupted libraries today
    What does that mean?
  • They get errors like this. "The Zotero database 'zotero.sqlite' appears to have become corrupted."
  • After restarting Firefox and going to the Advanced pane of the Zotero preferences, does the database integrity check fail?
  • There has been no issues with the database according to that. I have done that multiple times today, as I have seen my colleagues have problems. I did that about 20 minutes before I got my corruption. I got my corruption right after the error I logged.
  • To be clear, Zotero itself can't corrupt a database—only Firefox can. We haven't seen actual database corruption bugs in years (since Firefox 2.0), though. All corruption issues we've seen since then have been due to disk errors or people using external sync programs (e.g. Dropbox).

    It's possible that the error from your report either A) made Zotero think the database was corrupted or B) actually triggered database corruption in Firefox. The latter is highly unlikely and would be very bad, but they'd have to upload their supposedly corrupted databases (which they should be able to find in the Zotero data directory) to the DB Repair Tool and send the Upload ID to support@zot...org for us to know for sure.

    In any case, I'm fixing the issue you're hitting above, which results from having a tag applied to over a thousand items.
  • Thanks for fixing that tagging issue. I am guessing its a firefox issue then. We are not using an external sync program. Do you want me to try to upload my database that gave me that error to the DB repair tool, to check?
  • If you look in your Zotero data directory you should see a file marked as damaged. You should upload that to the DB Repair Tool and send the Upload ID via e-mail.
  • OK, you can try the latest 2.0 Branch XPI, which should fix the syncing error you were getting above. After syncing successfully, you can and should switch back to 2.0.3. Be sure to install the 2.0 Branch XPI and not the Trunk XPI.
  • Your zotero.sqlite.damaged file was fine—no corruption—so it was indeed a spurious error message triggered by the tag issue above.
  • Should everyone that had the corruption use the 2.0 Branch XPI. Thanks for all your help on this. It was very responsive.
  • It's possible everyone was hitting the same error due to the particular data in the group library, in which case, yes, the 2.0 Branch XPI would fix it for everyone. Once everyone is in sync, they can probably switch back to 2.0.3.
  • Dan,

    I had everyone in our group use the 2.0 Branch XPI and things seemed to work ok until today. One of our group member got the same error as above error # 1607684534. I assume this is related to the number of tags in the library like before. Should we switch back to the Branch XPI again?
Sign In or Register to comment.