2

Closed

Unexpected token 'ToNetworkThreadsRatioPercentage'

description

Tried running PAL v2.1 x64 on a variety of machines from Windows 7 SP1 through Windows Server 2003 and every time I process a perfmon log file (using the MOSS 2007 with Search template) from the MOSS 2007 Index/Search server....I get the same error on every machine when it gets to processing network threads (even when running PAL on the MOSS 2007 Index/Search server). I've attached the PAL log file from my last attempt (English, Windows 7 SP1)...and getting the exact same error.
 
Processing: Threads Accessing Network
Counter data for ""...Done
Counter data for ""...Done
WARNING: Please post errors or problems with this tool to the PAL web site
located at http://www.codeplex.com/PAL with the following error message and a
brief description of what you were trying to do. Thank you.
Invoke-Expression : Unexpected token 'ToNetworkThreadsRatioPercentage' in expre
ssion or statement.
At C:\Program Files\PAL\PAL v2.1\PAL.ps1:3309 char:22
  • Invoke-Expression <<<< -Command $Code
    • CategoryInfo : ParserError: (ToNetworkThreadsRatioPercentage:St
      ring) [Invoke-Expression], ParseException
    • FullyQualifiedErrorId : UnexpectedToken,Microsoft.PowerShell.Commands.In
      vokeExpressionCommand

file attachments

Closed May 30, 2012 at 5:22 AM by ClintH
No response from the user in over 30 days.

comments

mdiorio wrote Apr 4, 2012 at 9:10 PM

I'm having the exact same issue. Running on Windows 7 SP1 x64. Perfmon log was taken using MOSS 2007 and Search exported template file.

Invoke-Expression : Unexpected token 'ToNetworkThreadsRatioPercentage' in expre
ssion or statement.
At C:\Program Files\PAL\PAL\PAL.ps1:3326 char:22
  • Invoke-Expression <<<< -Command $sCode
    • CategoryInfo : ParserError: (ToNetworkThreadsRatioPercentage:St
      ring) [Invoke-Expression], ParseException
    • FullyQualifiedErrorId : UnexpectedToken,Microsoft.PowerShell.Commands.In
      vokeExpressionCommand

mdiorio wrote Apr 5, 2012 at 3:29 PM

You can, for now, go into the XML template for MOSS Search and comment out the Network Threads section, then the rest of the analysis will run fine.

ClintH wrote Apr 10, 2012 at 3:17 AM

It looks like PowerShell might be resolving another variable name within that variable name. I did a quick change to the variable name to make it different than the others. Let me know if this works. If so, I let Ron Grzywacz (content owner of this threshold file) know about the change. Thank you.

Sign in to add a comment