I'm to get this to run but keep getting this error: Get-Counter : The specified counter path could not be interpreted.

Any insight into this issue would be appreciated.

param($destserver, $destDB)
$destserver = "CCIIT23"
$destDB = "SSIMS_Prod"

$Servers = Get-SqlData $destserver $destDb "Select ServerName From ServerNames"
write-output $Servers


$CounterList = Get-SqlData $destserver $destDb "Select Counter From MemoryCounterList"
write-output $CounterList

$Servers | Foreach-Object {
    $Serv = $_; $CounterList | Foreach-Object {
        Get-Counter -Computer $Serv -Counter $_ -SampleInterval 1
        }
    }

Hi ClayRP,

I'm not sure about the function Get-SqlData, However, Please make sure you have the right input format of the parameter -Counter in the cmdlet Get-Counter with "[\\<ComputerName>]\<CounterSet>(<Instance>)\<CounterName>".

To get the right counter example of Memory Counter set, try to run the cmdlet below:

(Get-Counter -ListSet memory).paths

I hope this helps.

• Edited by AnnaWYMicrosoft contingent staff, Moderator Thursday, January 09, 2014 2:41 AM
• Marked as answer by AnnaWYMicrosoft contingent staff, Moderator Saturday, January 18, 2014 10:49 AM

Hi ClayRP,

I'm not sure about the function Get-SqlData, However, Please make sure you have the right input format of the parameter -Counter in the cmdlet Get-Counter with "[\\<ComputerName>]\<CounterSet>(<Instance>)\<CounterName>".

To get the right counter example of Memory Counter set, try to run the cmdlet below:

(Get-Counter -ListSet memory).paths

I hope this helps.

• Edited by AnnaWYMicrosoft contingent staff, Moderator Thursday, January 09, 2014 2:41 AM
• Marked as answer by AnnaWYMicrosoft contingent staff, Moderator Saturday, January 18, 2014 10:49 AM
• Unmarked as answer by AnnaWYMicrosoft contingent staff, Moderator 10 hours 24 minutes ago

Thanks AnnaWY.  I figured out that the misleading error was because I didn't run the ISE as Administrator.  I had admin rights to the OS and to SQL.  Not sure why I had to run as Administrator.  Any ideas why?

Hello,

I`ve found this in powershell documentation:

"Performance counters are often protected by access control lists (ACLs). To get all available performance count
ers, open Windows PowerShell with the "Run as administrator" option."

Good luck)

• Edited by Kolomiets Sergei 2 hours 49 minutes ago

Hello,

I`ve found this in powershell documentation:

"Performance counters are often protected by access control lists (ACLs). To get all available performance count
ers, open Windows PowerShell with the "Run as administrator" option."

Good luck)

• Edited by Kolomiets Sergei 2 hours 43 minutes ago

Thanks AnnaWY.  I figured out that the misleading error was because I didn't run the ISE as Administrator.  I had admin rights to the OS and to SQL.  Not sure why I had to run as Administrator.  Any ideas why?

• Marked as answer by AnnaWYMicrosoft contingent staff, Moderator 10 hours 23 minutes ago

Hello,

I`ve found this in powershell documentation:

"Performance counters are often protected by access control lists (ACLs). To get all available performance count ers, open Windows PowerShell with the "Run as administrator" option."

Good luck)

• Edited by Kolomiets Sergei 19 hours 25 minutes ago

Hi ClayRP,

Thanks for your sharing.

As Kolomiets Sergei mentioned, this is because this cmdlet need to open Windows PowerShell with the "Run as administrator" option because of ACLs.

You can get this information when you run the cmdlet "get-help Get-Counter -online", which is listed in Notes part.

I hope this helps.