header failing during import-csv #4
Description
The import-csv process fails when I am analyzing my iis logs, due to the header being null or empty. After doing some analysis, it certainly wasn't empty or null, but instead one of the header objects was null, and appeared at the last object in the headers array. So I fixed this by filtering out headers by piping that cmdlet's results to a where-object cmdlet. | where-object {$_ -notlike ''}
Not sure if this has anything to do with it because I'm not really an IIS guy, but my IIS logs were from a 2003 server.