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.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

JMajeau

Well we eventually got to a fix, so you can consider this closed!
JMajeau

I've sent another email but just in case it's better I send it here, from what I understand we seem unsure what is happening still.

I was recommended to look into adding a delay to the sending of command lines (something we had already tested and found ineffective, unfortunately) and that it might be a Firewall issue, something that we've also ruled out.

Considering how the error only happens in german (and likely some other languages, but not english) and we're simply sending command lines that work perfectly in english, I was wondering what the next steps would be, what we could do or try to fix this or whatnot.
JMajeau

Rinse and repeat! Send another trace from another debug version I received.
JMajeau

Again, sent another trace file with the latest version I was provided.
JMajeau

After receiving yet another Debug WinSCP, I was able to replicate the issue this time, and I've sent the file created by the software. I hope this will help!
JMajeau

I've sent an email response with the file requested from the latest Debug WinSCP I was sent. Unfortunately the issue did not replicate with that specific software, but I'm now awaiting response on what we can do next to fix this.
JMajeau

I downloaded the Debug WinSCIP, it did not have any other language besides English.
So I followed the steps (Starting with the *Get More* button) and downloaded the Dutch language, proceeded to extract it at the same location as the .exe,
and then I could see the Dutch selection. However when I attempted to select it, it gave me an error message, and restarting WinSCP does not fix this.
(To be clear, the language is not changing, so I can’t test my problem).
JMajeau

I've registered and sent an email with the link.
martin

Re: Error when using WinSCP with privatekey (when WinSCP is set to Dutch)

Thanks for the logs.

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include a link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

You will find my address (if you log in) in my forum profile.
JMajeau

Session Log Files requested

I've attached both session logs, I've renamed them so that their language is apparent.
martin

Re: Error when using WinSCP with privatekey (when WinSCP is set to Dutch)

Please attach a full session log file showing the problem (using the latest version of WinSCP).

A log file from English version for comparison might be helpful too.

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
JMajeau

Error when using WinSCP with privatekey (when WinSCP is set to Dutch)

Hello, I'm a developer working to incorporate the support of WinSCP with our product, and we've just received a bug report from a user which we've been able to replicate.

Essentially, when WinSCP's language is set to dutch, it returns an error when we're trying launch it through our software (this does not present itself when WinSCP's language is set to English).

We're sending the parameters configured in the required way described, but is it possible that the parameter names are changed with the language of the software?

I have attached a screenshot of the error.