Thanks for the insight. I noticed yesterday that there were wide gaps in the logs when this would run, I also found that the actual command was running from the "temp" folder under my profile. The gaps are because this is something that apparently runs when a login is made through RDP and then continues to run every hour while that user remained logged in. I can see now that it must be something in the script itself, and I forwarded the information to our systems team to get some insight into the script itself and why it might be causing these errors.

Edited by RWebster7 (2016-10-20 04:36 PM)