Report ID 1822025540

sroever
This error is related to syncing in a group library. Another member of the group synced one day ago with no trouble. When I tried to sync, I get the same sync error repeatedly. I checked my Zotero version and saw that it was 2.0.3, so I downloaded the latest version, restarted both Firefox and the computer itself, and tried again to sync. Same error resulted, at about the same point mid-sync. The text of the error is [JavaScript Error: "Unexpected status code 403 for request 214923/FC4MAHSC in Zotero.Sync.Storage.Session.ZFS.downloadFile()" {file: "chrome://zotero/content/xpcom/storage/zfs.js" line: 265}]

[JavaScript Error: "[Exception... "'A file sync error occurred. Please try syncing again.
  • dstillman
    Provide a Debug ID for a sync attempt that generates this error.
  • sroever
    The Debug ID is D1012503408.
  • dstillman
    Try clearing your browser cache.
  • dstillman
    edited September 7, 2010
    Though, actually, that shouldn't help, because Zotero bypasses the cache already for the request in question. But it's worth a try.

    Are you connecting via a proxy server? Do you have some sort of security software installed that you can try disabling?
  • sroever
    Okay, I cleared the browser cache. I wasn't sure whether to do this just for today or "everything," so I tried just for "today."

    I am not connected via a proxy server. I am using a MacBook Pro so the only security software I have is whatever comes automatically with a MacBook.

    I have been using Zotero for maybe four months now, and had previously synced many, many times up until the end of July with no trouble. I was then basically off-line for six weeks, and so this is the first time I have tried to sync since late July or maybe early August. As far as I know, nothing has changed since then except whatever software updates have come through automatically via Software Update.
  • dstillman
    Can you provide another Debug ID, assuming the sync still fails?
  • sroever
    The Debug ID is D1600227113.

    This is after quitting Firefox and restarting the computer.

    The error always comes at the same point in the sync, when the blue progress bar is about 1/10th of the way across.
  • dstillman
    It's not actually failing at the same place—it's failing on different files each time, and you should see the total file count decreasing if you hover over the progress bar. And it looks like the error you're getting is coming from Amazon.

    I've put in some additional debugging in the latest 2.0 Branch dev XPI, so if you install that and generate another Debug ID we may be able to see the error from Amazon. It might just be an intermittent error from Amazon's storage service, which happens, but we usually don't see it with such regularity.
  • dstillman
    The 2.0 Branch dev XPI should be safe to use, by the way—it contains only fixes since 2.0.6. You can switch back to 2.0.6 after generating the output.
  • sroever
    Okay, I downloaded the 2.0 Branch dev XPI, restarted Firefox, and hit the sync button again. It did seem to make more progress (over 20% this time, thanks for telling me about hovering over the bar) but still got an error. Here is the Debug ID:

    The Debug ID is D858157423.

    I am fairly low-tech so I don't know what it means to use 2.0.6 vs. the 2.0 branch. Is there some reason I should switch back to 2.0.6?
  • dstillman
    Actually, it looks like getting the full error message from Amazon is going to be a bit tricky.

    But...check your system clock. Is it correct?

    Re: branch, there's no great harm with being on it, but it's slightly less tested code and you'll get frequent update notifications (every time we make a change). So you should switch back to 2.0.6.
  • sroever
    Okay. I don't know what a system clock is or how to check it. Could you explain? (If it's something more technical than seeing if the clock on my computer is showing the right time.)

    And for switching back to 2.0.6, what do I do -- just download it again?

    Many thanks for your ongoing help with this!
  • dstillman
    If it's something more technical than seeing if the clock on my computer is showing the right time.
    It's not—but make sure it's the exact right time.
    And for switching back to 2.0.6, what do I do -- just download it again?
    Yes.
  • sroever
    Okay. According to http://www.timeanddate.com/worldclock/, yes it is the exact right time (down to the minute, at least). Would it matter for some reason that I am in the GMT+2 time zone (so 10 hours ahead of Seattle)?
  • dstillman
    No, assuming your time zone is set correctly as well.
  • dstillman
    Unfortunately there's not a great way to debug this without getting fairly technical, so for now I'd recommend just keeping syncing until all your files are transferred. Once they are, it's possible you won't see this on subsequent syncs.

    If you do, we can investigate further at that point.
  • sroever
    Okay, will do. Thanks again for your help.

This is an old discussion that has not been active in a long time. Instead of commenting here, you should start a new discussion. If you think the content of this discussion is still relevant, you can link to it from your new discussion.