Justalearner wrote:

I observe few strange issues with WinSCP(version 5.1.6.0). As a background we are using WinSCP for around 3 years now and never faced these issues before. Kindly provide your valuable suggestion.

Why did you put your problem in this thread? I do not see any relation. Please start a new thread.
Can you reproduce the problem with the latest version of WinSCP?

Hi,
Again one more observation. Strange though.

Server X has mapped network path Z (\\serverY\XXXX TempFiles\)
Now using command prompt from ServerX if I navigate to Z drive and type WinSCP.com in the prompt "Error retrieving product version" error message is coming.Please check the file named cmderror.jpg.

Please provide your feedback.

Hi,
I observe few strange issues with WinSCP(version 5.1.6.0). As a background we are using WinSCP for around 3 years now and never faced these issues before. Kindly provide your valuable suggestion.

Issue 1
---------
We have a SSIS package which is installed in a server say serverX. The package contains a Execute Process component which calls the WinSCP.com file stored in ServerY. Please check attached winscp.jpg
This setup was working perfectly for past 3 years and few days back it broke. I am breaking my head but no solution found yet.
As per the integration services catalog below is the error message
------------------------------
Execute Process Task:Error: In Executing "\\ServerY\XXXX TempFiles\WinSCP.com" "/script="Invoices.txt" /log="WinSCP.log"" at "\\ServerY\XXXX TempFiles", The process exit code was "2" while the expected was "0".
------------------------------

Issue 2
-------------

I have a mapped network drive Z which is mapped to \\ServerY\XXXX TempFiles.
Now from serverX if I just go to the network UNC path \\ServerY\XXXX TempFiles and double click the WinSCP.exe file I get a error message. Please look into attachment UNC_ERROR.jpg attached.

On the other hand if I just open the mapped drive and then double click the WinSCP.exe, the UI opens up nicely.
Is not this a strangest behavior? We are actually accessing same path from same ServerX.


Kindly provide your valuable feedback. Trust me this is how winSCP is behaving.

Yesss please help!

bump for support

I needed to move files from a UNC path to a nfs path mounted on a linux server. I used the symlink solution, but that made this a pretty clumsy process. I ended up switching to FileZilla which supports UNC paths out of the box. I didn't know about dragging from an explorer window into winscp, but that is still a bit of a kludge.

Both apps support sftp, which is what we have enabled on linux, so ease of use wins it for filezila in my case.

This product is a great product.

However, by issuing the dialog box "UNC paths are not supported" in the browse window, you have communicated to the users the message that the entire product does not support UNC paths, which is untrue.

Clearly, since folks have been asking you for this feature for 10 years, it must not be a trivial feature to add.

How about this: Modify the message from "UNC paths are not supported" to "UNC paths are not supported in the browser. Consider drag-and-drop to Windows Explorer window.". This will communicate the scope of the issue, and a useful workaround.

It will also decrease the number of people asking for a feature that you have had on the "back burner" for a decade.

This workaround is great! Thanks Martin.

It would be a nice tip in documentation about UNC use.