Whilst generating a PAL report (v 2.3.6 - Windows 7 32-bit) using 3 .blg files separated by a semi-colon in the Counter Log Path, the following error occurred. See attached screen print for better detail. The 3 .blg files generate reports successfully when executed separately. Might just be a case of the 3 .blg files being too big for 1 report?
The '-split' operator failed: Exception of type 'System.OutOfMemoryException' w
as thrown..
At C:\Program Files\PAL\PAL\PAL.ps1:2059 char:42
+ $aLine = $oCSVFile[$i].Trim('"') -split <<<< '","'
+ CategoryInfo : InvalidOperation: (:) [], ParentContainsErrorRec
ordException
+ FullyQualifiedErrorId : OperatorFailed
Comments: ** Comment from web user: ClintH **
The '-split' operator failed: Exception of type 'System.OutOfMemoryException' w
as thrown..
At C:\Program Files\PAL\PAL\PAL.ps1:2059 char:42
+ $aLine = $oCSVFile[$i].Trim('"') -split <<<< '","'
+ CategoryInfo : InvalidOperation: (:) [], ParentContainsErrorRec
ordException
+ FullyQualifiedErrorId : OperatorFailed
Comments: ** Comment from web user: ClintH **
Hi DianePill,
Unfortunately, this means that the PAL tool needs more virtual address space that 32-bit can't provide. I am not a professional developer and the tool can be quite the memory hog when working with large counter logs. I'm sorry, but the only way to solve this is to use the 64-bit version of PAL on 64-bit Windows or Windows Server.