1

Closed

error message with PAL 2.3.3 -

description

Hello,

I created a perfmon template file using the SQL thresholds to look at 2 instances and created the data collector set. This is running fine.

When I pass the blg file through PAL i get the following error

C:\Program Files\PAL\PAL>C:

C:\Program Files\PAL\PAL>cd "C:\Program Files\PAL\PAL"

C:\Program Files\PAL\PAL>Powershell -NoProfile ".\PAL.ps1" -Log H:\ASRL's\AS-SQL
-11_PAL_Microsoft_SQL_Server_2005_2008.blg -ThresholdFile 'C:\Program Files\PAL\
PAL\SQLServer.xml' -Interval 'AUTO' -IsOutputHtml $True -HtmlOutputFileName '[Lo
gFileName]_PAL_ANALYSIS_[DateTimeStamp].htm' -IsOutputXml $False -XmlOutputFileN
ame '[LogFileName]_PAL_ANALYSIS_[DateTimeStamp].xml' -AllCounterStats $False -Ou
tputDir '\meteurope.net\dfs\Location\GB-BSH\homedrives\sallen1\Desktop' -Number
OfThreads 1 -NumberOfProcessors '4' -ThreeGBSwitch $False -SixtyFourBit $True -T
otalMemory '16' -RAID5Drives 'NULL' -RAID1Drives 'NULL'
The string starting:
At line:1 char:566
  • .\PAL.ps1 -Log H:\ASRL's\AS-SQL-11_PAL_Microsoft_SQL_Server_2005_2008.blg -Th
    resholdFile 'C:\Program Files\PAL\PAL\SQLServer.xml' -Interval 'AUTO' -IsOutput
    Html $True -HtmlOutputFileName '[LogFileName]_PAL_ANALYSIS_[DateTimeStamp].htm'
    -IsOutputXml $False -XmlOutputFileName '[LogFileName]_PAL_ANALYSIS_[DateTimeSt
    amp].xml' -AllCounterStats $False -OutputDir '\meteurope.net\dfs\Location\GB-B
    SH\homedrives\sallen1\Desktop' -NumberOfThreads 1 -NumberOfProcessors '4' -Thre
    eGBSwitch $False -SixtyFourBit $True -TotalMemory '16' -RAID5Drives 'NULL' -RAI
    D1Drives 'NULL <<<< '
    is missing the terminator: '.
    At line:1 char:567
  • .\PAL.ps1 -Log H:\ASRL's\AS-SQL-11_PAL_Microsoft_SQL_Server_2005_2008.blg -Th
    resholdFile 'C:\Program Files\PAL\PAL\SQLServer.xml' -Interval 'AUTO' -IsOutput
    Html $True -HtmlOutputFileName '[LogFileName]_PAL_ANALYSIS_[DateTimeStamp].htm'
    -IsOutputXml $False -XmlOutputFileName '[LogFileName]_PAL_ANALYSIS_[DateTimeSt
    amp].xml' -AllCounterStats $False -OutputDir '\meteurope.net\dfs\Location\GB-B
    SH\homedrives\sallen1\Desktop' -NumberOfThreads 1 -NumberOfProcessors '4' -Thre
    eGBSwitch $False -SixtyFourBit $True -TotalMemory '16' -RAID5Drives 'NULL' -RAI
    D1Drives 'NULL' <<<<
    • CategoryInfo : ParserError: (:String) [], ParentContainsErrorRe
      cordException
    • FullyQualifiedErrorId : TerminatorExpectedAtEndOfString
C:\Program Files\PAL\PAL>

file attachments

Closed Oct 3, 2013 at 5:50 PM by ClintH

comments

ClintH wrote Apr 18, 2013 at 5:26 AM

The single quote in the path H:\ASRL's to the log file is causing Powershell to think that it is the beginning of a literal string. Analyze counter logs in a different file path that does not contain single quotes or other special characters.

CodedSteve wrote Apr 18, 2013 at 7:56 AM

Hi,

Changing the path has worked pefectly, thank you very much indeed,

Regards

ClintH wrote May 10, 2013 at 9:06 PM

FYI. I added a parameter check in v2.3.5 that will look for single quotes in the file path and if found will stop processing and point out the problem. There is nothing I can do about getting around it due to how Powershell handles single quotes a literal string delimiters.