Can't sync to zotero, haven't tried for about 2 months

envsjam7
Error ID: 819486328
The green sync wheel in firefox finishes but it gives me an error that I can't describe too well. I have tried changing my password, emptying my trash and deleting an item from a previous error.
  • adamsmith
    "but it gives me an error that I can't describe too well"
    What does it say? Or why can't you describe it?
  • dstillman
    Component returned failure code: 0x80630003 (NS_ERROR_STORAGE_CONSTRAINT) [mozIStorageStatement.execute]" nsresult: "0x80630003 (NS_ERROR_STORAGE_CONSTRAINT)" location: "JS frame :: chrome://zotero/content/xpcom/db.js :: :: line 145" data: no] [QUERY: UPDATE tags SET name=?, type=?, dateAdded=?, dateModified=?, clientDateModified=?, libraryID=?, key=? WHERE tagID=?] [ERROR: columns libraryID, name, type are not unique]' when calling method: [nsITimerCallback::notify]"
    Provide a Debug ID for a sync attempt that produces the error.
  • envsjam7
    Right, so here is the error from the red exclamation mark after trying to sync.

    [Exception... "Component returned failure code: 0x80630003 (NS_ERROR_STORAGE_CONSTRAINT) [mozIStorageStatement.execute]" nsresult: "0x80630003 (NS_ERROR_STORAGE_CONSTRAINT)" location: "JS frame :: chrome://zotero/content/xpcom/db.js :: <TOP_LEVEL> :: line 145" data: no] [QUERY: UPDATE tags SET name=?, type=?, dateAdded=?, dateModified=?, clientDateModified=?, libraryID=?, key=? WHERE tagID=?] [ERROR: columns libraryID, name, type are not unique]

    Report ID: 128922198
  • adamsmith
    edited February 6, 2012
    see dan's post above - provide a debug id (he links to instructions) for a sync attempt that produces the error.
  • envsjam7
    Oh oops, here's what you wanted. Debug ID is D1953231422.
  • dstillman
    edited February 6, 2012
    The issue with this group has already been reported. See my latest response there. You can follow up in that thread.

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.