Henrik,
Thanks, I have seen that post but it doesn't seem applicable - more geared towards a developer writing an application that accesses files on an SMB/DFS share.
to test further I've done three things:
1. Point the PowerShell task to the actual UNC path rather than using the mapped drive. This had no effect and we still got the error intermittently.
2. Entered the script in the PowerShell Script text box rather than pointing to a script file. This seems to have resolved the issue for us, but this isn't ideal as our workflow requires source control on our script repository.
3. disabled SMB secure signing on the computer where VisualCron is installed, per the instructions
here . This also did not change the behavior at all.
I also found this article that seems a bit related:
https://support.microsoft.com/en-us/kb/2756452 It's referring to windows 8, but we're running VisualCron on Server 2012R2. It seems to say that an occasional reboot or a re-mapping of the drive can fix this. Any further thoughts? Thanks!