The script would run perfectly if I ran it manually, but when I ran the task nothing would happen. As you might know this is a bit of a problem because schedule tasks don't not show the console, and won't allow you to see the errors. The Task's log are not very helpful either.
What helped me troubleshoot the problem is this little cmdlet:
Start-transcript -path C:\Temp\Filename.txt
Placing that command at the beginning of your script will create a transcript file. The transcript file will contain everything that would print into the console, and it should look a little like this:
-------------------------------------------------------------
**********************
Windows PowerShell transcript start
Start time: 20141114101902
Username : DOMAIN\S.AD.Util
Machine : HOSTNAME (Microsoft Windows NT 6.3.9600.0)
**********************
Transcript started, output file is C:\Temp\Transcript_11-14-2014.txt
ModuleType Version Name ExportedCommands
---------- ------- ---- ----------------
Script 1.0 tmp_scev4zye.pet {Get-DServerSetti...
-------------------------------------------------------------
If there is any errors they will show here, even if they are not stopping errors. Which is great because at one point my script was sending the email and successfully completing, but failing to create the report all together and sending a blank email.
I hope this might help someone out there!
No comments:
Post a Comment