Synching Problem with WEBDAV server

Report ID 1790200889

Before switching to 2.0 b7, I had no problems in synching libraries on 4 machines through a WEBDAV server. With the upgrade, only one machine synchs successfully with the server. The others return the error message:

Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove]

Upgrading to 2.0 b7v2 has not resolved the problem.
  • Could you generate debug output for the sync attempt from the Advanced pane of the Zotero prefs, submit it to the server, and post the Debug ID here? Thanks.
  • Many thanks, Dan, for your immediate response:

    The Debug ID is D1238941754
  • #
    Previously reported sync error has not been resolved by updating to b7.4

    Error message is: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove]

    report id is 332769272
    #

    * CommentAuthorDan Stillman
    * CommentTime1 day ago

    No need to create duplicate threads.
    ___________________
    Apologies for incorrect procedure in duplicating the thread.

    Just wondered if there was any progress on this issue. Have seen other reports & responses on problems with WebDAV sync but not sure whether to try some of the solutions suggested.

    It's testimony to the great work that you guys are doing that I've become so dependent on the program, and the facility to sync between multiple machines--all the more frustrating that something that was working superbly is no longer functioning.
  • This is mostly likely fixed in the latest dev build. If you'd like to test it, you can temporarily install the trunk XPI over 2.0b7.4 and try to sync. Using a trunk build isn't generally recommend for non-developers, but other than this fix there've been only a few minor UI fixes since 2.0b7.4, and it should be safe to try the current build, r5320. (Obviously you should make sure you have a backup anyway.)

    After verifying that it fixes the problem, you can either switch back to 2.0b7.4 or stay on r5320 until 2.0b7.5. If you stay on the trunk, be sure not to update to any later dev builds (which may be offered on a daily basis), and switch to 2.0b7.5 when it comes out.
  • Installed trunk XPI on one machine...and am delighted to report that the sync problem seems to have been resolved. Will wait until 2.0b7.5 before changing the other machines.

    Many thanks!
  • OK, great—thanks for testing. We'll get 2.0b7.5 out soon with this fix.
Sign In or Register to comment.