Page 1 of 8

Analysis of "System Monitor Log.csv"

Report Generated at: 4/12/2012 9:11:17 PM

PALv2

On This Page Tool Parameters Alerts by Chronological Order 4/12/2012 11:43:18 AM - 4/12/2012 12:03:18 PM Alerts: (0) 4/12/2012 12:03:18 PM - 4/12/2012 12:23:18 PM Alerts: (1) 4/12/2012 12:23:18 PM - 4/12/2012 12:43:18 PM Alerts: (1) 4/12/2012 12:43:18 PM - 4/12/2012 1:03:18 PM Alerts: (1) 4/12/2012 1:03:18 PM - 4/12/2012 1:23:18 PM Alerts: (1) 4/12/2012 1:23:18 PM - 4/12/2012 1:33:18 PM Alerts: (1) 4/12/2012 1:33:18 PM - 4/12/2012 1:53:18 PM Alerts: (1) 4/12/2012 1:53:18 PM - 4/12/2012 2:13:18 PM Alerts: (1) 4/12/2012 2:13:18 PM - 4/12/2012 2:33:18 PM Alerts: (0) 4/12/2012 2:33:18 PM - 4/12/2012 2:53:18 PM Alerts: (1) 4/12/2012 2:53:18 PM - 4/12/2012 3:13:18 PM Alerts: (1) 4/12/2012 3:13:18 PM - 4/12/2012 3:23:18 PM Alerts: (1) 4/12/2012 3:23:18 PM - 4/12/2012 3:43:18 PM Alerts: (1) 4/12/2012 3:43:18 PM - 4/12/2012 4:03:18 PM Alerts: (1) 4/12/2012 4:03:18 PM - 4/12/2012 4:23:19 PM Alerts: (1) 4/12/2012 4:23:19 PM - 4/12/2012 4:43:19 PM Alerts: (1) 4/12/2012 4:43:19 PM - 4/12/2012 5:03:19 PM Alerts: (0) 4/12/2012 5:03:19 PM - 4/12/2012 5:13:19 PM Alerts: (0) 4/12/2012 5:13:19 PM - 4/12/2012 5:33:19 PM Alerts: (0) 4/12/2012 5:33:19 PM - 4/12/2012 5:53:19 PM Alerts: (1) 4/12/2012 5:53:19 PM - 4/12/2012 6:13:19 PM Alerts: (1) 4/12/2012 6:13:19 PM - 4/12/2012 6:33:19 PM Alerts: (1) 4/12/2012 6:33:19 PM - 4/12/2012 6:53:19 PM Alerts: (1) 4/12/2012 6:53:19 PM - 4/12/2012 7:03:19 PM Alerts: (1) 4/12/2012 7:03:19 PM - 4/12/2012 7:23:19 PM Alerts: (1) 4/12/2012 7:23:19 PM - 4/12/2012 7:43:19 PM Alerts: (0) 4/12/2012 7:43:19 PM - 4/12/2012 8:03:20 PM Alerts: (0) 4/12/2012 8:03:20 PM - 4/12/2012 8:23:20 PM Alerts: (0) 4/12/2012 8:23:20 PM - 4/12/2012 8:43:20 PM Alerts: (1) 4/12/2012 8:43:20 PM - 4/12/2012 9:01:40 PM Alerts: (1) Memory Memory Committed Bytes (Stats only) Process Process Private Bytes (Alerts: 0) Process Handle Count (Alerts: 22) Disclaimer Back to the top

Tool Parameters:
Name Log Time Range: Log(s): AnalysisInterval: Threshold File: AllCounterStats: RAID1Drives: RAID5Drives: TotalMemory: NumberOfProcessors: ThreeGBSwitch: SixtyFourBit: Back to the top Value 4/12/2012 11:43:18 AM - 4/12/2012 8:53:20 PM C:\mem\System Monitor Log.csv 18 Minute(s) 20 second(s) C:\Program Files\PAL\PAL v2.1\SystemOverview.xml False NULL NULL 8 1 True True

Alerts by Chronological Order

file://\\nbgx\nbshare\sdsmqa\SMSP\System_Monitor_Log_PAL_ANALYSIS_2012-04-12... 4/13/2012

Page 2 of 8

Description: This section displays all of the alerts in chronological order.

Alerts
An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter's respective analysis section for more details about what the threshold means. Time Range 4/12/2012 12:03:18 PM 4/12/2012 12:23:18 PM Condition Counter Min Avg Max 991 Hourly Trend

Possible Handle Leak: More than 500 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 500 (SMSPControl)\Handle Count handles per hour 4/12/2012 12:23:18 PM 4/12/2012 12:43:18 PM Condition Counter

1,049 1,107 893 Hourly Trend

Min Avg Max

Possible Handle Leak: More than 500 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 500 (SMSPControl)\Handle Count handles per hour 4/12/2012 12:43:18 PM 4/12/2012 1:03:18 PM Condition Counter

1,252 1,324 1,397 897 Min Avg Max Hourly Trend

Possible Handle Leak: More than 500 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 500 (SMSPControl)\Handle Count handles per hour 4/12/2012 1:03:18 PM 4/12/2012 1:23:18 PM Condition Counter

1,517 1,590 1,662 888 Min Avg Max Hourly Trend

Possible Handle Leak: More than 500 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 500 (SMSPControl)\Handle Count handles per hour 4/12/2012 1:23:18 PM 4/12/2012 1:33:18 PM Condition Counter

1,788 1,860 1,931 887 Min Avg Max Hourly Trend

Possible Handle Leak: More than 500 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 500 (SMSPControl)\Handle Count handles per hour 4/12/2012 1:33:18 PM 4/12/2012 1:53:18 PM Condition Counter

2,042 2,042 2,042 829 Min Avg Max Hourly Trend

Possible Handle Leak: More than 500 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 500 (SMSPControl)\Handle Count handles per hour 4/12/2012 1:53:18 PM 4/12/2012 2:13:18 PM Condition Counter

2,193 2,262 2,332 811 Min Avg Max 771 Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 2:33:18 PM 4/12/2012 2:53:18 PM Condition Counter

1,614 2,458 392 Hourly Trend

Min Avg Max

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 2:53:18 PM 4/12/2012 3:13:18 PM Condition Counter

1,193 1,254 1,316 174 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 3:13:18 PM 4/12/2012 3:23:18 PM Condition Counter

1,472 1,528 1,584 246 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 3:23:18 PM 4/12/2012 3:43:18 PM Condition Counter

1,731 1,731 1,731 284 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count

1,875 1,936 1,998 316

file://\\nbgx\nbshare\sdsmqa\SMSP\System_Monitor_Log_PAL_ANALYSIS_2012-04-12... 4/13/2012

Page 3 of 8

handles per hour 4/12/2012 3:43:18 PM 4/12/2012 4:03:18 PM Condition Counter Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 4:03:18 PM 4/12/2012 4:23:19 PM Condition Counter

2,150 2,213 2,276 362 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 4:23:19 PM 4/12/2012 4:43:19 PM Condition Counter

2,426 2,486 2,546 400 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 5:33:19 PM 4/12/2012 5:53:19 PM Condition Counter

2,702 2,774 2,845 436 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 5:53:19 PM 4/12/2012 6:13:19 PM Condition Counter

1,490 1,548 1,606 133 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 6:13:19 PM 4/12/2012 6:33:19 PM Condition Counter

1,756 1,810 1,864 169 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 6:33:19 PM 4/12/2012 6:53:19 PM Condition Counter

2,016 2,076 2,136 203 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 6:53:19 PM 4/12/2012 7:03:19 PM Condition Counter

2,291 2,351 2,411 234 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 7:03:19 PM 4/12/2012 7:23:19 PM Condition Counter

2,554 2,554 2,554 253 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 8:23:20 PM 4/12/2012 8:43:20 PM Condition Counter

2,676 2,751 2,826 269 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 8:43:20 PM 4/12/2012 9:01:40 PM Condition Counter

1,665 1,741 1,817 113 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour

1,966 1,966 1,966 134

Memory
Memory Committed Bytes
Description: Committed Bytes is the amount of committed virtual memory, in bytes. Committed memory is the memory which has space reserved in RAM and on the disk paging file(s). There can be one or more paging files on each physical drive. This counter displays the last observed value

file://\\nbgx\nbshare\sdsmqa\SMSP\System_Monitor_Log_PAL_ANALYSIS_2012-04-12... 4/13/2012

Page 4 of 8

only; it is not an average. This analysis checks if the amount of total committed memory (Commit Charge) exceeds the amount of physical RAM installed. If so, the page file needs to be used to help store the committed memory and performance might degrade. To alleviate this, try to identify which process is consuming the most committed memory by looking at process Private Bytes and looking for a potential memory leak (the consumption of memory over a long period of time without releasing it). Adding more RAM to the computer will help alleviate this issue, but if it is a memory leak, then the problem might return.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average. \Memory\Committed Bytes Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed

Condition

Min

Avg

Max

No SHAREAPP Thresholds

4,901,249,024 5,292,623,653 5,393,682,432 45,841,944 115,348,457 5,281,212,580 5,270,261,214 5,256,262,472

Alerts
An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter's respective analysis section for more details about what the threshold means. No Alerts Found Back to the top

Process
Process Private Bytes
Description: This analysis determines if the system leaking memory over time. A process consuming large portions of memory is okay as long as the process returns the memory back to the system. Look for increasing trends in the chart. An increasing trend over a long period of time could

file://\\nbgx\nbshare\sdsmqa\SMSP\System_Monitor_Log_PAL_ANALYSIS_2012-04-12... 4/13/2012

Page 5 of 8

indicate a memory leak. Private Bytes is the current size, in bytes, of memory that this process has allocated that cannot be shared with other processes. This analysis checks for a 10MBs per hour and 5MBs per hour increasing trends. Use this analysis in correlation with the Available Memory analysis. Use this analysis in correlation with the Available Memory analysis. If you suspect a memory leak condition, then install and use the Debug Diag tool. For more information on the Debug Diag Tool, see the references section. References: Debug Diagnostic Tool v1.1 http://www.microsoft.com/downloads/details.aspx?FamilyID=28bd5941-c458-46f1-b24df60151d875a3&displaylang=en

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average. Hourly Std Trend Deviation 0 87,595 0 159,095 10% of Outliers Removed 43,352,064 99,142,615 20% of Outliers Removed 43,352,064 99,138,856 30% of Outliers Removed 43,352,064 99,133,072

Condition OK OK OK OK OK OK OK

\Process(*)\Private Bytes SHAREAPP/SDMgmtSvc SHAREAPP/SMSPControl SHAREAPP/SMSPMedia SHAREAPP/SMSPService SHAREAPP/SMSPWeb SHAREAPP/SWSvc

Min 43,352,064

Avg

Max

43,352,064 43,352,064 99,146,240 99,176,448

SHAREAPP/SMSP2010StorageArchServ 98,066,432

337,465,344 368,673,426 379,756,544 3,360,980 6,274,979 367,760,835 367,231,340 366,497,267 189,689,856 195,965,221 198,287,360 623,337 49,811,456 95,170,560 61,238,638 63,463,424 95,887,287 97,124,352 627,035 204,738,560 208,958,903 211,415,040 392,908 1,670,539 195,689,923 195,449,469 195,211,369 2,010,691 61,019,423 95,745,884 60,824,144 95,640,235 60,530,688 95,560,520 1,282,560 208,756,408 208,576,330 208,362,260

-125,731 585,520

Alerts
An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter's respective analysis section for more details about what the threshold means. No Alerts Found Back to the top

Process Handle Count

file://\\nbgx\nbshare\sdsmqa\SMSP\System_Monitor_Log_PAL_ANALYSIS_2012-04-12... 4/13/2012

Page 6 of 8

Description: This analysis checks overall system to determine how many handles the system has open to determine if there is a handle leak. Handle leaks can be attributed to memory leak. If this analysis throws alerts, then you need to manually open the performance monitor log and look at the instances "\Process(*)\Handle Count" to determine which process is leaking handles. Note: The normal System Overview analysis checks all of the processes.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average. Hourly Std Trend Deviation 0 -1 0 2 10% of Outliers Removed 183 547 20% of Outliers Removed 183 547 30% of Outliers Removed 183 547

Condition OK OK

\Process(*)\Handle Count SHAREAPP/SDMgmtSvc

Min Avg Max 183 183 183 553

SHAREAPP/SMSP2010StorageArchServ 545 547

Possible Handle Leak: More than 250 handles between overall Min and overall Max SHAREAPP/SMSPControl and an increasing trend of more than 100 handles per hour OK OK OK OK SHAREAPP/SMSPMedia SHAREAPP/SMSPService SHAREAPP/SMSPWeb SHAREAPP/SWSvc

701 1,692 2,845 134

593

1,572

1,481

1,379

373 402 379 511 371 415 503 507

405 566 417 515

2 8 5 -1

4 36 9 4

402 505 414 506

402 501 414 505

401 496 414 505

Alerts
An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter's respective analysis section for more details about what the threshold means. Time Range 4/12/2012 12:03:18 PM 4/12/2012 12:23:18 PM Condition Counter Min Avg Max 991 Hourly Trend

Possible Handle Leak: More than 500 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 500 (SMSPControl)\Handle Count handles per hour 4/12/2012 12:23:18 PM Condition Counter

1,049 1,107 893

Min Avg Max

Hourly

file://\\nbgx\nbshare\sdsmqa\SMSP\System_Monitor_Log_PAL_ANALYSIS_2012-04-12... 4/13/2012

Page 7 of 8

4/12/2012 12:43:18 PM Possible Handle Leak: More than 500 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 500 (SMSPControl)\Handle Count handles per hour 4/12/2012 12:43:18 PM 4/12/2012 1:03:18 PM Condition Counter

Trend 1,252 1,324 1,397 897 Min Avg Max Hourly Trend

Possible Handle Leak: More than 500 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 500 (SMSPControl)\Handle Count handles per hour 4/12/2012 1:03:18 PM 4/12/2012 1:23:18 PM Condition Counter

1,517 1,590 1,662 888 Min Avg Max Hourly Trend

Possible Handle Leak: More than 500 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 500 (SMSPControl)\Handle Count handles per hour 4/12/2012 1:23:18 PM 4/12/2012 1:33:18 PM Condition Counter

1,788 1,860 1,931 887 Min Avg Max Hourly Trend

Possible Handle Leak: More than 500 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 500 (SMSPControl)\Handle Count handles per hour 4/12/2012 1:33:18 PM 4/12/2012 1:53:18 PM Condition Counter

2,042 2,042 2,042 829 Min Avg Max Hourly Trend

Possible Handle Leak: More than 500 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 500 (SMSPControl)\Handle Count handles per hour 4/12/2012 1:53:18 PM 4/12/2012 2:13:18 PM Condition Counter

2,193 2,262 2,332 811 Min Avg Max 771 Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 2:33:18 PM 4/12/2012 2:53:18 PM Condition Counter

1,614 2,458 392 Hourly Trend

Min Avg Max

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 2:53:18 PM 4/12/2012 3:13:18 PM Condition Counter

1,193 1,254 1,316 174 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 3:13:18 PM 4/12/2012 3:23:18 PM Condition Counter

1,472 1,528 1,584 246 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 3:23:18 PM 4/12/2012 3:43:18 PM Condition Counter

1,731 1,731 1,731 284 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 3:43:18 PM 4/12/2012 4:03:18 PM Condition Counter

1,875 1,936 1,998 316 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 4:03:18 PM 4/12/2012 4:23:19 PM Condition Counter

2,150 2,213 2,276 362 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 4:23:19 PM 4/12/2012 4:43:19 PM Condition Counter

2,426 2,486 2,546 400 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 5:33:19 PM 4/12/2012 5:53:19 PM Condition Counter

2,702 2,774 2,845 436 Min Avg Max Hourly Trend

file://\\nbgx\nbshare\sdsmqa\SMSP\System_Monitor_Log_PAL_ANALYSIS_2012-04-12... 4/13/2012

Page 8 of 8

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 5:53:19 PM 4/12/2012 6:13:19 PM Condition Counter

1,490 1,548 1,606 133 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 6:13:19 PM 4/12/2012 6:33:19 PM Condition Counter

1,756 1,810 1,864 169 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 6:33:19 PM 4/12/2012 6:53:19 PM Condition Counter

2,016 2,076 2,136 203 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 6:53:19 PM 4/12/2012 7:03:19 PM Condition Counter

2,291 2,351 2,411 234 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 7:03:19 PM 4/12/2012 7:23:19 PM Condition Counter

2,554 2,554 2,554 253 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 8:23:20 PM 4/12/2012 8:43:20 PM Condition Counter

2,676 2,751 2,826 269 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour 4/12/2012 8:43:20 PM 4/12/2012 9:01:40 PM Condition Counter

1,665 1,741 1,817 113 Min Avg Max Hourly Trend

Possible Handle Leak: More than 250 handles between overall \\SHAREAPP\Process Min and overall Max and an increasing trend of more than 100 (SMSPControl)\Handle Count handles per hour Back to the top

1,966 1,966 1,966 134

Back to the top

Disclaimer: This report was generated using the Performance Analysis of Logs (PAL) tool. The information provided in this report is provided "as is" and is intended for information purposes only. The authors and contributors of this tool take no responsibility for damages or losses incurred by use of this tool.

file://\\nbgx\nbshare\sdsmqa\SMSP\System_Monitor_Log_PAL_ANALYSIS_2012-04-12... 4/13/2012