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

martin

Re: it doesn't help...

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

To generate the session log file, use /log=C:\path\to\winscp.log command-line argument. 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.
lamelle

it doesn't help...

Hi Martin,

it doesn't help.

I modified it with =* but it doesn't work.

The message, when triggered with the task planner in Windows is still the same. It asks me if I trust the computer...

Curious: When I manually start the same task in the task planner... it's working... but makes no sense.
lamelle

Hi Martin,

thank you for your reply.
The key itself doesnt't change. It's always the same.

It more looks like Windows Server whether 2012 or 2016 permanently stores the key correctly.
It seems like an error there. But I am not sure.
lamelle

Meldungen mit Zertifikatespeicher

Hallo zusammen,

wir haben hier ein Skript, welches immer nach einer Woche oder nach einem Neustart nicht mehr über die Aufgabenplanung funktioniert. Es muss dann einmal manuell ausgeführt werden, damit die Eingabe mit "Ja" bestätigt wird,

Die Meldung ist:
Der Rechnerschlüssel des Servers wurde nicht im Speicher gefunden. Es gibt keine Garantie, das der Server wirklich der Rechner ist, mit dem Sie sich verbinden wollten. Die RSA Schlüssel-Details des Servers lauten:

Wie kann das behoben werden?