Write-Error not showing errors?

PowerShell Universal
1 
Product: PowerShell Universal
Version: 2.11.1

$User = "First.last@domain.com"
Write-Host "Here is some host output"
Write-Error "Failed to find UserPrincipalName [ $User ]"

image
image1570Ă—546 18.7 KB

It used to work?

image
image1599Ă—542 24.6 KB

2

What’s your scripts ErrorAction set to? It might be hiding the error if it’s set to SilentlyContinue. You could change it to Continue.

3

This is literally the script…

$User = "First.last@domain.com"
Write-Host "Here is some host output"
Write-Error "Failed to find UserPrincipalName [ $User ]"
4

image

5

At some point we started to actually set ErrorActionPreference based on that setting and then it suppresses the error messages. If you change it to continue, it should show them.

6

Looks like that worked. I tend to check various scripts output types to handle errors from other PS processes. So when it was being suppressed the errors were slipping through.

    # Return all errors
    $JobError = $HostOutput | Where-Object { 
        $_.Type -eq [PSUJobOutputTypes]::Error 
    }

Not sure if this is the best way to handle this but its been working I guess…

Any idea why the errors tend to show up multiple times?

image
image1573Ă—609 24.4 KB

7

Now that seems like a bug. I’ll open an issue for it.

8

Appreciate the quick reply.

Ill set my scripts -ErrorAction “Continue” across the board.

1 Like
9

@adam

So we upgraded to version 2.12.2 and write-error with ErrorAction set to continue is not showing that the job failed? Is this intended?

image
image1522Ă—552 24.1 KB

However on version 3.0.0 it shows the job failed with that same ErrorAction preference.

image
image1220Ă—455 55.8 KB

I guess I’m not sure what is intended here. I would like to see the job failed when write-error happens so we can utilize triggers. This worked in version 2.11.1

Thanks,
Michael

10

The expected behavior is that Continue will not fail but will display errors. SilentlyContinue will not display errors or fail. Stop will fail the script and display errors.

I think the v3 behavior is incorrect.

11

Thanks for the quick reply. For our case we might want to set the ErrorAction to stop if that is the case.