I have similar scripts to other vendors that do not get this error, so I think this could be a connection issue- but I'm open to the possibility that I have a configuration issue and hoped you might see something in the logs to indicate this.
I have reviewed documentation about this error, but had a question about:
In my scripts, I set up locations for session and debug logs that I know the account running the script has access to. Are these logs different than the log mentioned above?Alternatively, you can use (undocumented) property Session.XmlLogPath to change the log file location.
If so, would I set this (in Powershell) as:
$session.XmlLogPath = "\\location_of_log\"