I see my post was too late, but here's other ways to debug a script when you run into something like this in the future: In addition to Write-Debug, you might try debugging your script by setting up a PS breakpoint for the $ComputerName, $UserName, & $PrinterName variables to follow their values as the script runs. When you hit a breakpoint, it will tell you which variable it broke for, and whether it was a read or a write operation. For each time it breaks, you can manually dump out the variable. You might even put a Write-Debug statement before it breaks on reading the variables for the importing of the importing of the failures.csv file to say something like 'About to import the failures.csv.' That way, you can see what the value of each variable is when the import of the failures.csv is being done.
![Power shell import csv into excel Power shell import csv into excel](https://i.ytimg.com/vi/xE1Z3i9wnxo/maxresdefault.jpg)
Jan 19, 2012 - The Import-CSV cmdlet in PowerShell is incredibly useful. You can take any CSV file and pump objects to the pipeline. The cmdlet uses the.
![Import Import](/uploads/1/2/5/4/125492030/454280212.jpg)
Set-PSBreakpoint -Script -Variable ComputerName,UserName,PrinterName -Mode ReadWrite.