Announcement

Collapse
No announcement yet.

Webdav (Sharepoint) and Umlauts

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Webdav (Sharepoint) and Umlauts

    I'm testing the new Webdav possibilities to synchronize with a Sharepoint folder, but I have problems with pathes containing an Umlaut.

    A folder called "1 - Einführung" (German for introduction) becomes "1 - Einf�" in BC4 and the folder is marked not readable (and the content is not visible)

    A file with an Umlaut is listed, but when I open the file view I get a HTTP error 404: Not found.

    Anything I can do? (Beside renaming the folders and files in Sharepoint)

    I'm using Version 4.1.5 (build 21031) on Windows 7 and a SharePoint Server 2013.

  • #2
    Hello,

    If you transfer a file using BC4 that initially exists on the local side over to sharepoint, does it transfer correctly? If you disconnect and refresh does the file name maintain the correct characters? If opened, does it display and work as expected?

    Testing on our own Sharepoint test server (2013 Foundation) and WebDAV with other services (like Box), files transfer well. Folder names might have some trouble with Sharepoint WebDAV, which isn't a bug for our WebDAV support but is specific to Sharepoint's support.
    Aaron P Scooter Software

    Comment


    • #3
      Sorry for my late answer, I had no possibility to test earlier.

      I made your test and the copied file received a wrong filename in the BC4-view.

      In meantime I made a BC4-update and copying results in:


      When I refresh, I get:


      If I try a file compare before I refresh, I can compare the files:


      After the refresh I get a 404-error when I try to read the file from sharepoint.

      In sharepoint itself, the file names look ok:
      Attached Files

      Comment


      • #4
        Thanks. I've reproduced this on our own test environment, and will open a tracker to investigate. Not sure why files were working previously, as now I'm seeing some of the name corruption there as well.
        Aaron P Scooter Software

        Comment


        • #5
          Aaron, don't forget I reported a similar issue with WebDav and Ampersand in filenames last year. AFAIK, it has not been fixed yet.
          https://secure.scootersoftware.com/v...with-ampersand


          Edit - just checked - it's still broken:
          6/29/2016 5:50:07 PM Unable to copy https://dms.wi-sun.org/htcomnet/hcwe...al-logo/Master files/b&w_wi-Sun_logo3.psd: HTTP error 400: Bad Request
          6/29/2016 5:50:07 PM Unable to copy https://dms.wi-sun.org/htcomnet/hcwe...inal-logo/Logo 29102012/b&wwi-Sun_logo3.jpg: HTTP error 400: Bad Request
          6/29/2016 5:50:07 PM Unable to copy https://dms.wi-sun.org/htcomnet/hcwe...inal-logo/Logo 29102012/b&wlogo3.tif: HTTP error 400: Bad Request
          6/29/2016 5:50:07 PM Unable to copy https://dms.wi-sun.org/htcomnet/hcwe...inal-logo/Logo 29102012/b&wlogo.jpg: HTTP error 400: Bad Request
          6/29/2016 5:50:08 PM Unable to copy https://dms.wi-sun.org/htcomnet/hcwe...inal-logo/Logo 29102012/b&w_wi-Sun_logo3.gif: HTTP error 400: Bad Request
          6/29/2016 5:50:08 PM Unable to copy https://dms.wi-sun.org/htcomnet/hcwe...inal-logo/Logo 29102012/b&w_logo3.png: HTTP error 400: Bad Request
          6/29/2016 5:50:08 PM Unable to copy https://dms.wi-sun.org/htcomnet/hcwe...inal-logo/Logo 29102012/b&w_logo.jpg: HTTP error 400: Bad Request
          Last edited by timg11; 29-Jun-2016, 06:01 PM.

          Comment


          • #6
            Hello,

            Assuming this server type is Sharepoint, I see an error, but the error text is different and it also fails using Windows Explorer, which points towards a general Sharepoint limitation than a BC4 error. In the previous forum thread, I ask if it were possible to get a test account, which would help with testing; would that be possible?
            Aaron P Scooter Software

            Comment


            • #7
              Support for Unicode paths and filenames on SharePoint WebDAV servers should be fixed in Beyond Compare 4.1.7.
              Chris K Scooter Software

              Comment


              • #8
                Sorry for my late response, I missed the update.

                I can confirm, my problem is solved. (Version 4.1.8)

                Thanks for your update!
                Last edited by knut; 14-Sep-2016, 08:38 AM. Reason: Add version information

                Comment


                • #9
                  I'm running BC 4.1.9, and the problem with Ampersands in file names is is still not fixed.

                  "4/21/2017 3:28:17 PM Unable to copy https://......b&w_logo3.png: HTTP error 400: Bad Request"

                  Comment


                  • #10
                    Hello,

                    This may be a different issue. The above issue was fixed and confirmed by the user, but this might be server specific. Could you re-test with the latest BC 4.2 beta? If you are still having trouble, could we get a full file log? What kind of WebDAV server are you connecting to? Which OS are you running BC4 on?

                    You can publicly post here, or privately reach us at support@scootersoftware.com with a link back to this forum thread for our reference.
                    Aaron P Scooter Software

                    Comment

                    Working...
                    X