Initial Sync up unsuccessful - ID 1485029345
Nothing seems to go up on a sync. I am using the standalone with about 4000+ references.
JavaScript Error: "[Exception... "'Uploaded data not well-formed (Report ID: 4f09848e53)' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "<unknown>" data: no]"]
JavaScript Error: "[Exception... "'Uploaded data not well-formed (Report ID: 4f09848e53)' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "<unknown>" data: no]"]
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.
http://forums.zotero.org/discussion/21223/
See my response there.
However the branch does not solve the problem.
I got both the not-wellformed data response but also server response messages
847614908 invalid response from server
1016970130 Third try
If you get that again, provide a Debug ID for a sync attempt that produces that error.
[JavaScript Error: "[Exception... "'Uploaded data not well-formed (Report ID: 4a4567c257)' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "<unknown>" data: no]"]
[JavaScript Error: "Uploaded data not well-formed (Report ID: 4a4567c257)" {file: "chrome://zotero/content/xpcom/sync.js" line: 895}]
[JavaScript Error: "Uploaded data not well-formed (Report ID: 4a4567c257)" {file: "chrome://zotero/content/xpcom/sync.js" line: 895}]
The REPORT ID is 380114146
I have actually zipped and unloaded my sqlite file to my dropbox account, if that helps you.
http://db.tt/CfR5sVeL
(You can remove that file from Dropbox. Thanks.)
If that doesn't work, you could also try syncing using Zotero Standalone, which might not be subject to the same bug. Zotero Standalone will default to using your existing data directory on first run.
We're looking into switching to a different processing method in the next version after 3.0 to work around this problem. If you're not able to get it to go through now, we may be able to provide another dev XPI that fixes it in the near future.
Thanks.