CODEWITHSUNDEEP
exceptionpowershell
David Thomas
David Thomas

Reputation: 2349

PowerShell catching typed exceptions

I'm having an issue with PowerShell where it will not catch an exception even when the exception is explicitly mentioned in the catch command.

In this case, I'm trying to determine if a ProcessID is still running, and if not then it will take some actions.

The sample code block that I am struggling with is:

    try {
      Get-Process -Id 123123 -ErrorAction 'Stop'
    } 
    catch [Microsoft.PowerShell.Commands.ProcessCommandException] {
      "Caught by Exception Type: Process is missing"
    }
    catch {
    if ($_.Exception.getType().FullName -eq "Microsoft.PowerShell.Commands.ProcessCommandException") {
      "Caught by Catch All: Process is missing"
      }
    }

When this code block is executed the output is:

Caught by Catch All: Process is missing

You would expect the first catch condition to trigger as it names the exception being thrown correctly, but it doesn't trigger.

To make things worse, when the second catch command runs (which catches anything) it queries the name of the exception type and checks if it is "Microsoft.PowerShell.Commands.ProcessCommandException" (which it is) and then takes appropriate steps.

I know I can work around this, but I feel I'm missing a fundamental way about how PowerShell handles Exceptions.

Can anyone shed light on this for me?

Upvotes: 18

Views: 18118

Answers (2)

Grzes
Grzes

Reputation: 1

Maybe cause you are missing an error action

try 
{ 
    kill 1234567 -ErrorAction Stop 
} 
catch 
{ 
    Write-Host "Blam!" 
}

Upvotes: -1

Shay Levy
Shay Levy

Reputation: 126912

When you set ErrorAction to Stop, non-terminating errors are wrapped and thrown as type System.Management.Automation.ActionPreferenceStopException, this is the type you want to catch. 

try 
{
    Get-Process -Id 123123 -ErrorAction Stop
} 
catch [System.Management.Automation.ActionPreferenceStopException]
{
    ... do something ...
}

Upvotes: 28

Related Questions