1
Vote

CalculatePercentile : ERROR: $aSortedNumbers -isnot [System.Object[]]. This is most likely due to no counters in the threshold file matching to counters in the counter log

description

Kindly assist as I am getting the following error when trying to run PAL analyzer for checking what is using the processor.

CalculatePercentile : ERROR: $aSortedNumbers -isnot [System.Object[]]. This is most likely due to no counters in the
threshold file matching to counters in the counter log.
At C:\Program Files\PAL\PAL\PAL.ps1:2635 char:34
  • ... ventyth = $(CalculatePercentile -Values $alAllNumeric -Percentile 70) ...
  • ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
    • FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,CalculatePercentile
At C:\Program Files\PAL\PAL\PAL.ps1:2392 char:13
  • If ($iUBound -gt $aSortedNumbers.GetUpperBound(0))
  • ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : InvalidOperation: (:) [], ParentContainsErrorRecordException
    • FullyQualifiedErrorId : InvokeMethodOnNull

comments

ClintH wrote Jul 5 at 4:09 PM

This is most likely due to no counters in the threshold file matching to counters in the counter log. This most often happens if the counter log was recorded in a non-English language.

cornelsmit0001 wrote Jul 5 at 4:55 PM

I have checked found that I was able to successfully to analyze the performance counters on the server were I captured the logs from, but from my windows 10 machine it keeps on failing with error as per above.
I have checked now on my Windows 10 I have 2 languages for English setup. Could it be due to English (United States) and English (South Africa) ? Thanks for posting something. Could it be possible something to do with the PAL.ps1 file my Windows 10 Machine ?

ClintH wrote Jul 5 at 5:55 PM

They might be different versions. First, download and use the latest version (2.7.7) at http://github.com/clinthuffman/PAL to see if the problem reproduces with that version. Be aware that Codeplex.com is going away, so all future updates will be at GitHub.com.

wrote Jul 5 at 5:57 PM