<div>
Maybe this is what you need? <a href="https://blogs.msdn.microsoft.com/powershell/2006/09/15/errorlevel-equivalent/" rel="ugc">https://blogs.msdn.microsoft.com/powershell/2006/09/15/errorlevel-equivalent/</a>&nbsp;<a href="https://social.technet.microsoft.com/Forums/scriptcenter/en-US/7ec89f9a-23d2-421e-9e01-ed926f9f58f4/capturing-the-exit-code-of-a-powershell-script-from-batch-file?forum=ITCG" rel="ugc nofollow">or this one</a>
</div>


<div>
Are there any specific examples which illustrates the use of exit codes using the code that I have supplied ?<br />
<br />
Thanks
</div>


<div>
I don't quite understand why you are nesting powershell executables, and we can't tell what that actual script that is supposed to be running is? &nbsp;What are you actually trying to accomplish?<br />
<br />
In the mean time, for your 2nd powershell.exe command string, you could add a start-transcript &amp;&nbsp;end-transcript to catch everything? &nbsp;<br />
You can also add a -redirectstandarderror &lt;filename&gt; to the Start-Process that gets issued.. <br />
<br />
I think your nested powershell's would probably screw up your CMD error codes.. if you want the actual powershell errors, then there are far far better ways to catch &amp;&nbsp;handle them.. <br />
<br />
Coralon
</div>


<div>
Hi<br />
<br />
Thanks for getting back to me.<br />
<br />
The script highlighted:-<br />
<br />
@ECHO ON<br />
PowerShell.exe -NoProfile -Command &quot;&amp;&nbsp;{Start-Process PowerShell.exe -ArgumentList '-NoProfile -ExecutionPolicy Bypass -File &quot;&quot;%~dpn0.ps1&quot;&quot;' -Verb RunAs}&quot; <br />
<br />
runs in a DOS batch environment so it will be run as a scheduled task <br />
<br />
What I am trying to achieve is to try and report any errors if the script fails as you mentioned you can use catch statements? can you show me examples of using these commands please using the script I have mentioned ?<br />
<br />
Thanks
</div>


<div>
No response from user; unknown if this will accomplish what he was trying to do, but we were on the right track to getting the answer..
</div>


<div>
<div class="content wysiwyg-content">
Hi <br />
<br />
I have the following powershell script which is called within a DOS batch:-<br />
<br />
@ECHO ON<br />
PowerShell.exe -NoProfile -Command &quot;&amp;&nbsp;{Start-Process PowerShell.exe -ArgumentList '-NoProfile -ExecutionPolicy Bypass -File &quot;&quot;%~dpn0.ps1&quot;&quot;' -Verb RunAs}&quot; <br />
<br />
I need to include error conditions in the script, if the script fails and logs these entries to a log file or eventviewer please ?<br />
<br />
Thanks
</div>
</div>


Hi 

I have the following powershell script which is called within a DOS batch:-

@ECHO ON
PowerShell.exe -NoProfile -Command "& {Start-Process PowerShell.exe -ArgumentList '-NoProfile -ExecutionPolicy Bypass -File ""%~dpn0.ps1""' -Verb RunAs}" 

I need to include error conditions in the script, if the script fails and logs these entries to a log file or eventviewer please ?

Thanks

Powershell running within a DOS batch script to include error handling

Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to the Component Object Model (COM) and Windows Management Instrumentation (WMI), enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and Common Information Model (CIM) enabling management of remote Linux systems and network devices.

Powershell

Microsoft Disk Operating System (MS-DOS) was an operating system for x86-based personal computers, and traces of it are still found in the Windows operating system. DOS is still used in some embedded systems and for certain legacy 16-bit networks.