And does the generated script work?

---

Note that the generated script puts the password into session URL, where many symbols need to be encoded:
https://winscp.net/eng/docs/session_url#special
In your original script you had the password in -password switch, where encoding/escaping is not needed. Except for the double quote.

Thanks for your advice. I generated a script in WinSCP. With that script, I can connect to the server.
In this generated script, most special character is the password are replaced by %nn where nn is the hexavalue of the character.
The " at the end of the password is not a tippo

Have WinSCP GUI generate a script for you:
https://winscp.net/eng/docs/ui_generateurl

Though I do not see any really special character in your password. Maybe except for the trailing double-quote. I'm just not sure it is supposed to be part of the password or if it is a typo. If it is part of the password, you need to double it.
https://winscp.net/eng/docs/scripting#quotes

SFTP server
Automated

Winscp.exe GUI interface: We can connect to an SFTP server with the credentials we got from the provider.
When we want to connect to this server using a script in an automated scene, then the authentication fails,

script:

the scriptfile, screenshot and a logfile are send as attachments.

I suppose the strange characters in the password are the reason.
I asked a password with less characters and not that kind of characters, but, due to security reasons, the provider does not give another password.

Can somebody help me?
Greetings