Post a reply

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

Thanks for your feedback.
GRR3

With development version running for several days, we have not received this error.

Thank you.
martin

OK, you are probably facing this problem:
https://winscp.net/tracker/1619

I'm sending you an email with a development version of WinSCP to the address you have used to register on this forum.
GRR3

Thank you, I have added the collection of the inner error to all my scripts.
I have not yet set all the scripts up with debug logs.
This is the first error I was able to collect.
Error: Error parsing session log file
Inner Exception: Root element is missing.
martin

We need to see the "inner exception": $_.Exception.InnerException.Message.

It would also help, if you set $session.DebugLogPath and attach that log too.
GRR3

Adding logs and script (private data removed, but please don't repost)

The session log doesn't show an error, but I catch errors and send them in an email.
Error: Error parsing session log file
Line number 57: $session.Open($sessionOptions)

Maybe I should catch these types of errors or do something different?

Thanks.
martin

Re: Error parsing session log file

The error must have more details for sure (an inner exception). What is it?
GRR3

Error parsing session log file

We have a number of Powershell scripts using the library. We recently updated to 5.13.

Since update, I've seen a few (three) errors of "Error parsing session log file".

Each time, I've enabled debug logs, but have not seen the error occur again on the same script.

Do you have any general thoughts on why this might occur or know of any steps I can take to prevent this?

Thanks.