error ID 1291142937 Note "Archive" too long...

hlthenvt

[JavaScript Error: "[Exception... "'Note 'Archive...' too long' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "<unknown>" data: no]"]

I don't know what this means. The error occurs when trying to sync with server.

adamsmith

in general this means that a Note starting with "Archive" is too long for syncing - but I'd hold off on trying to fix this, there have been a number of reports like this and there might be a problem server-side. Also, if this was indeed a problem with your database, Zotero should be giving you a less technical and more helpful error.

mark

Colleague of mine has the exact same problem just now. ("Note 'References' too long".)
Error report ID 1480742882.

Trouble is Zotero doesn't provide enough detail to find the note. User has loads of notes starting with exactly that word. Some of them indeed are long. But what is too long?

Felix

Here's the user from the 1480742882 report. What makes this hard to deal with is that Zotero doesn't want to do any syncing before this note is fixed. So I hope a solution can be found relatively soon. I'm trying to set up syncing between a library on a Mac and a new library on a laptop. Right now all my refs are on the Mac, which refuses to sync.

dstillman

There should be a more helpful message now with more of the note in question. I've also increased the note length limit (which we recently reduced) a bit.

mark

Thanks. We'll see if the problem recurs. In general, though, would it be possible to let the rest of the syncing operation go through while marking the problematic items as "unsynced"?

The way things are organised now it seems that syncing of any and all changes is prevented by a simple problem with perhaps only one note. It seems more helpful to allow the rest of the sync to happen while notifying the user of a problem with one item.

dstillman

In general, though, would it be possible to let the rest of the syncing operation go through while marking the problematic items as "unsynced"?

Not currently, but we're working to make that possible.