Sync "complaint" - Error Report: 1736348584

alandsloane
Zotero 2.0b7.1

I got a very terse error message after a lengthy sync operation on a computer which I hadn't sync-ed for, apparently, 76 days.

However, as far as I can see, everything looks fine - at least as far as downloading the new database entries.

Storage sync was enabled but had lost the username.
  • alandsloane
    I'm now getting another error "Unexpected status code 0 in Zotero.Sync.Storage._getStorageModificationTime()" (report 1535260059).

    I set up storage sync correctly and it went off spinning for a long time. Looking at the WebDAV server I can see that files have been uploaded, some megabytes and about a hundred files. Perhaps it's just a time-out, so I'll try again - maybe later when loads are less?
  • dstillman
    For the "status code 0" error, load the WebDAV URL in Firefox. There may be a self-signed certificate you need to accept. That or your system clock was off, which may actually have been the case, since it seems to have continued with the storage sync after that...
  • alandsloane
    I tried loading the URL and watching for certificate requests, but no such manifestation.

    However, I went through various resets - "File Sync History" and "Full Sync with Server" - and everything is now back and working again.

    Thanks for the help,
    Alan.

    BTW, I've turned off "sync automatically" because my system had become very slow and unresponsive whenever I made edits to Zotero entries. I admit to having insufficient memory installed, but turning off automatic sync seems to restore the responsiveness I had been used to. Of course, now I need to remember to sync manually ;-(

    I also changed from WebDAV over https to plain http, since I didn't see any value to having security for my PDF's while in transit.
  • dstillman
    I also changed from WebDAV over https to plain http, since I didn't see any value to having security for my PDF's while in transit.
    The encryption is for your login information for the WebDAV server.
  • alandsloane
    Thanks again! I guess I should have checked that out before displaying my ignorance in public>>>

    What I meant to say really was you could mark this thread "closed"
This discussion has been closed.