This bug has been added to the tracker:
https://winscp.net/tracker/1813
https://winscp.net/tracker/1813
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- PieterB
Thanks for sharing me that debug version of WinSCP. Attaching the debug files (sanitized) for you to this conversation.
- martin
Re: WebDAV: Sync to local not work for specific folder(s) - Error listing directory
Thanks for your report.
I have sent you an email with a debug version of WinSCP to the address you have used to register on this forum.
I have sent you an email with a debug version of WinSCP to the address you have used to register on this forum.
- PieterB
WebDAV: Sync to local not work for specific folder(s) - Error listing directory
I'm attempting to synchronize directories and files using WebDAV from a remote server to a local directory. For the majority of this, it works without any problems yet on occasion I do encountered a scenario that a given directory cannot be synced by WinSCP.
Message returned by WinSCP is of the following format:
At log level=2 the following messages are captured:
It does not give me any good indication of what could possibly be the reason for this failure. Content wise, I do have access to all the files and any subfolders.
Attaching the full log (private) for the complete details.
Message returned by WinSCP is of the following format:
Error listing directory '...[folder name here]...'.
Unknown error
At log level=2 the following messages are captured:
...
. 2019-11-28 12:35:07.183 WinSCP Version 5.15.7 (Build 10060) (OS 10.0.17763 - Windows 10 Enterprise)
...
. 2019-11-28 12:35:09.482 XML: end-element (268, {DAV:, lockscope})
. 2019-11-28 12:35:09.482 XML: char-data (267) returns 0
. 2019-11-28 12:35:09.482 XML: start-element (267, {DAV:, depth}) => 270
. 2019-11-28 12:35:09.482 XML: char-data (270) returns 0
. 2019-11-28 12:35:09.482 XML: char-data (270) returns 0
. 2019-11-28 12:35:09.482 Got depth: Infinity
. 2019-11-28 12:35:09.482 XML: end-element for 270 failed with -1.
. 2019-11-28 12:35:09.482 XML: end-element (270, {DAV:, depth})
. 2019-11-28 12:35:09.482 XML: XML_Parse returned 1
. 2019-11-28 12:35:09.482 sess: Closing connection.
. 2019-11-28 12:35:09.482 sess: Connection closed.
. 2019-11-28 12:35:09.482 Request ends, status 207 class 2xx, error line:
. 2019-11-28 12:35:09.482 207
. 2019-11-28 12:35:09.482 Running destroy hooks.
. 2019-11-28 12:35:09.482 Request ends.
. 2019-11-28 12:35:09.483 Asking user:
. 2019-11-28 12:35:09.483 Error listing directory '...[remove folder path here]...'. ("Unknown error")
< 2019-11-28 12:35:09.483 Script: Error listing directory '...[remove folder path here]...'.
< 2019-11-28 12:35:09.483 Script: Unknown error
. 2019-11-28 12:35:09.485 Script: Failed
. 2019-11-28 12:35:09.485 Session upkeep
. 2019-11-28 12:35:09.485 Script: Exit code: 1
. 2019-11-28 12:35:09.485 Script: Max roundtrip: 0
. 2019-11-28 12:35:09.486 sess: Destroying session.
It does not give me any good indication of what could possibly be the reason for this failure. Content wise, I do have access to all the files and any subfolders.
Attaching the full log (private) for the complete details.