Why error handling prevents script failure in PowerShell - See It in Action

Why error handling prevents script failure

📖 Scenario: You are writing a PowerShell script to process a list of files. Sometimes, files might not exist or have permission issues. Without error handling, the script stops when it hits a problem. You want to learn how to keep your script running even if some files cause errors.

🎯 Goal: Build a PowerShell script that tries to read content from a list of files. Use error handling to catch errors and continue processing all files without stopping the script.

📋 What You'll Learn

Create a list of file paths including some that do not exist

Add a variable to control error handling behavior

Use a try-catch block to handle errors when reading files

Print the content of files or an error message without stopping the script

💡 Why This Matters

🌍 Real World

Scripts often process many files or data sources. Errors like missing files or permission issues can stop scripts. Using error handling lets scripts continue working and handle problems gracefully.

💼 Career

Knowing how to handle errors is essential for automation, system administration, and scripting jobs. It helps create reliable scripts that don't fail unexpectedly.

1

Create a list of file paths

Create a variable called $filePaths and assign it an array with these exact strings: 'C:\temp\file1.txt', 'C:\temp\file2.txt', and 'C:\temp\nofile.txt'.

PowerShell

# Create the list of file paths
# Your code here

Hint

Use @( ... ) to create an array in PowerShell.

2

Add an error action preference variable

Create a variable called $ErrorActionPreference and set it to 'Stop' to make errors throw exceptions.

PowerShell

$filePaths = @('C:\temp\file1.txt', 'C:\temp\file2.txt', 'C:\temp\nofile.txt')
# Set error action preference to 'Stop'
# Your code here

Hint

This setting makes PowerShell treat errors as terminating, so try-catch can catch them.

3

Use try-catch to read files safely

Write a foreach loop using $filePath to go through $filePaths. Inside the loop, use a try block to read the file content with Get-Content $filePath. Use a catch block to print "Error reading $filePath" if reading fails.

PowerShell

$filePaths = @('C:\temp\file1.txt', 'C:\temp\file2.txt', 'C:\temp\nofile.txt')
$ErrorActionPreference = 'Stop'

# Loop through each file path and try to read content
# Your code here

Hint

Use try { ... } catch { ... } to handle errors and keep the script running.

4

Print the results

Run the script so it prints the content of existing files or the error message for missing files. The output should show the content of C:\temp\file1.txt and C:\temp\file2.txt or error messages for C:\temp\nofile.txt.

PowerShell

$filePaths = @('C:\temp\file1.txt', 'C:\temp\file2.txt', 'C:\temp\nofile.txt')
$ErrorActionPreference = 'Stop'

foreach ($filePath in $filePaths) {
    try {
        $content = Get-Content $filePath
        Write-Output $content
    } catch {
        Write-Output "Error reading $filePath"
    }
}

# Run the script to see output

Hint

If you see error messages for missing files but the script continues, your error handling works!

Practice

1. What is the main reason to use error handling in a PowerShell script?

easy

A. To change the script's output format

B. To make the script run faster

C. To add more comments to the script

D. To stop the script from crashing when an error happens

Solution

1. Step 1: Understand script failure

   Without error handling, a script stops running when it hits an error.

2. Step 2: Role of error handling

   Error handling catches errors so the script can continue running smoothly.

3. Final Answer:

   To stop the script from crashing when an error happens -> Option D

4. Quick Check:

   Error handling prevents crashes = A [OK]

Hint: Error handling keeps scripts running despite errors [OK]

Common Mistakes:

• Thinking error handling speeds up scripts
• Confusing error handling with commenting
• Believing error handling changes output format

2. Which of the following is the correct syntax to start an error handling block in PowerShell?

easy

A. try { }

B. catch { }

C. error { }

D. handle { }

Solution

1. Step 1: Identify error handling keywords

   PowerShell uses 'try' to start a block where errors might happen.

2. Step 2: Confirm correct syntax

   'try { }' is the correct way to begin error handling; 'catch { }' handles errors after try.

3. Final Answer:

   try { } -> Option A

4. Quick Check:

   Start error block with try = A [OK]

Hint: Error handling starts with try block in PowerShell [OK]

Common Mistakes:

• Using catch to start error handling
• Using non-existent keywords like error or handle
• Confusing try and catch roles

3. What will be the output of this PowerShell script?

try {
  Get-Item 'C:\nonexistentfile.txt'
} catch {
  Write-Output 'File not found, continuing script.'
}
Write-Output 'Script finished.'

medium

A. Get-Item : Cannot find path 'C:\nonexistentfile.txt' because it does not exist.

B. File not found, continuing script.
Script finished.

C. Script finished.

D. File not found, continuing script.

Solution

1. Step 1: Analyze try block

   Get-Item tries to get a file that does not exist, causing an error.

2. Step 2: Catch block runs

   The catch block catches the error and outputs 'File not found, continuing script.'

3. Step 3: Script continues

   After catch, the script outputs 'Script finished.'

4. Final Answer:

   File not found, continuing script. Script finished. -> Option B

5. Quick Check:

   Catch handles error, script continues = B [OK]

Hint: Catch block output runs, then script continues [OK]

Common Mistakes:

• Expecting script to stop on error
• Ignoring catch block output
• Thinking only last output prints

4. This script is meant to handle errors but the catch block doesn't run. What is the problem?

try {
  Get-Item 'C:\nonexistentfile.txt' -ErrorAction SilentlyContinue
} catch {
  Write-Output 'Error caught.'
}
Write-Output 'Done.'

medium

A. The -ErrorAction SilentlyContinue prevents catch from running

B. The catch block is missing

C. Get-Item syntax is wrong

D. Write-Output cannot be used inside catch

Solution

1. Step 1: Understand -ErrorAction SilentlyContinue

   This option stops errors from being thrown, so catch never triggers.

2. Step 2: Effect on error handling

   Since no error is thrown, catch block is skipped, but script does not crash.

3. Final Answer:

   The -ErrorAction SilentlyContinue prevents catch from running -> Option A

4. Quick Check:

   -ErrorAction SilentlyContinue blocks catch = D [OK]

Hint: SilentlyContinue stops catch from catching errors [OK]

Common Mistakes:

• Thinking catch block is missing
• Assuming Get-Item syntax error
• Believing Write-Output can't be in catch

5. You want your PowerShell script to try deleting a file, but if it fails, log the error and continue. Which script correctly uses error handling to do this?

hard

A. try { Remove-Item 'C:\file.txt' } catch { Write-Output 'Failed to delete file'; exit }

B. Remove-Item 'C:\file.txt' -ErrorAction Stop; Write-Output 'Continuing script'

C. try { Remove-Item 'C:\file.txt' } catch { Write-Output 'Failed to delete file' } Write-Output 'Continuing script'

D. Remove-Item 'C:\file.txt' -ErrorAction SilentlyContinue; Write-Output 'Failed to delete file'

Solution

1. Step 1: Check try-catch usage

   try { Remove-Item 'C:\file.txt' } catch { Write-Output 'Failed to delete file' } Write-Output 'Continuing script' uses try to attempt deletion and catch to log failure without stopping.

2. Step 2: Confirm script continues

   After catch, it outputs 'Continuing script', so script keeps running.

3. Final Answer:

   try { Remove-Item 'C:\file.txt' } catch { Write-Output 'Failed to delete file' } Write-Output 'Continuing script' -> Option C

4. Quick Check:

   Try-catch logs error and continues = C [OK]

Hint: Use try-catch and continue script after catch [OK]

Common Mistakes:

• Using exit in catch stops script
• Not using try-catch for error handling
• Using SilentlyContinue but logging error anyway