I have included the console output and error message below:
Transcript started, output file is C:\Users\JAMES_~1\AppData\Local\Temp\PAL.log
PAL v2.0.8 (http://www.codeplex.com/PAL)
Written by: Clint Huffman (clinth@microsoft.com) and other contributors.
Last Modified: 09/09/2011 22:27:02
The information and actions by this tool is provided "as is" and is intended for
information purposes only. The authors and contributors of this tool take no re
sponsibility for damages or losses incurred by use of this tool.
Your locale is set to: English (United Kingdom)
SCRIPT ARGUMENTS:
-Log C:\Users\James_Worthington\Desktop\aaa\UKDC1S101_20111005-000
018\PAL_Microsoft_Internet_Information_Services_5.x_6.x_7.x.blg
-ThresholdFile C:\Program Files\PAL\PAL v2.0.8\AspDotNet.xml
-Interval AUTO
-OutputDir C:\Users\James_Worthington\Desktop\aaa\UKDC1S101_201110
05-000018\PAL Report
-IsOutputHtml True
-HtmlOutputFileName [LogFileName]_PAL_ANALYSIS_[DateTimeStamp]jfjf.htm
-AllCounterStats False
-IsOutputXml False
-XmlOutputFileName [LogFileName]_PAL_ANALYSIS_[DateTimeStamp].xml
-BeginTime 05/10/2011 07:00:03
-EndTime 05/10/2011 07:30:03
Creating session working directory...
Creating directory "C:\Users\JAMES_~1\AppData\Local\Temp\{b7b9a341-1aaa-4a16-965
4-0214c67e872a}"
Creating file "C:\Users\James_Worthington\Desktop\aaa\UKDC1S101_201
11005-000018\PAL Report\PAL_Microsoft_Internet_Information_Services_5.x_6.x_7.x_
PAL_ANALYSIS_2011-10-06_15-15-53jfjf.htm"
Creating directory "C:\Users\James_Worthington\Desktop\aaa\UKDC1S10
1_20111005-000018\PAL Report\PAL_Microsoft_Internet_Information_Services_5.x_6.x
_7.x_PAL_ANALYSIS_2011-10-06_15-15-53jfjf\"
Threshold File Load History:
C:\Program Files\PAL\PAL v2.0.8\AspDotNet.xml
SystemOverview.xml
QuickSystemOverview.xml
DotNet.xml
Generating the counter list to filter on...Done
Removing duplicate counter expressions from counter list...Done
relog.exe "C:\Users\James_Worthington\Desktop\aaa\UKDC1S101_2011100
5-000018\PAL_Microsoft_Internet_Information_Services_5.x_6.x_7.x.blg" -cf "C:\Us
ers\James_Worthington\AppData\Local\Temp\{b7b9a341-1aaa-4a16-9654-0214c67e872a}\
CounterListFilter.txt" -f csv -o "C:\Users\James_Worthington\AppData\Local\Temp\
{b7b9a341-1aaa-4a16-9654-0214c67e872a}\_FilteredPerfmonLog.csv" -y -b "10/05/201
1 07:00:03" -e "10/05/2011 07:30:03"
Input
----------------
File(s):
C:\Users\James_Worthington\Desktop\aaa\UKDC1S101_20111005-000
018\PAL_Microsoft_Internet_Information_Services_5.x_6.x_7.x.blg (Binary)
Begin: 5/10/2011 7:00:03
End: 5/10/2011 19:00:03
Samples: 2881
Error: The time range specified has no overlap with the input logs.
MergeConvertFilterPerfmonLogs : [MergeConvertFilterPerfmonLogs] ERROR: Unable t
o find the converted log file:"C:\Users\James_Worthington\AppData\Local\Temp\{b
7b9a341-1aaa-4a16-9654-0214c67e872a}\_FilteredPerfmonLog.csv"
At C:\Program Files\PAL\PAL v2.0.8\PAL.ps1:5107 char:38
+ MergeConvertFilterPerfmonLogs <<<< -sPerfmonLogPaths $Log -BeginTime
$global:BeginTime -EndTime $global:EndTime
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorExcep
tion
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
n,MergeConvertFilterPerfmonLogs
MergeConvertFilterPerfmonLogs : Relog.exe failed to process the log. Review the
results above this line. If relog.exe continues to fail, then try running Relo
g.exe manually and/or contact Microsoft Customer Support Servers for support on
Relog.exe only. PAL is not supported by Microsoft.
At C:\Program Files\PAL\PAL v2.0.8\PAL.ps1:5107 char:38
+ MergeConvertFilterPerfmonLogs <<<< -sPerfmonLogPaths $Log -BeginTime
$global:BeginTime -EndTime $global:EndTime
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorExcep
tion
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
n,MergeConvertFilterPerfmonLogs
Comments: ** Comment from web user: AceyMan **
I'm seeing a problem with "Restrict to a Date Time Range" as well, but it has (for me) a fix.
When I used the PAL wizard to select a range, the PAL tool ran AOK and made the html report without issue, but the range I chose was not honored -- the whole .blg was parsed. Hmmm.
The counters came from hosts with US dd/MM/yyyy date settings, but I run my workstation with ISO8601 date (yyyy-MM-dd) for the short form. After searching around, on a hunch I changed my workstation (where I was using the tool) to US format (which pained me greatly, heh), e.g., dd/MM/yyyy, and then re-ran the analysis on the same .blg files -- now the range I chose was honored. Whee.
This isn't a show stopper but it definitely is a puzzler for us right and proper souls who are ISO 8601 correct.
On a related note: when I used the 'Add to Queue' feature to restart the wizard from the top to select a new .blg for analysis, by choosing the new file the selected date range is reset. I suppose that makes sense, since the new log will most likely have different begin/end times, but it'd be slick to (optionally) preserve the chosen date range when choosing a new .blg to parse. For me, I'm analyzing a multi-tier web farm with MSSQL back end during load testing, so it's natural to only care about a common time window across every node in the farm; preserving the time range would be handy here.
Thanks for a great tool.