Month: January 2012

List of performance counters for SharePoint web parts/application

Home | Performance Tuning | List of performance counters for SharePoint web parts/application

While troubleshooting one of the SharePoint application performance issues, one of my colleague asked me a question “What are the list of performance counters  to be considered for SharePoint application performance Diagnostics ?”. Here is the the indicative list of performance counters that can be considered for SharePoint webpart / application performance diagnostics.

Basic system related performance counters

No Counter Frequency of measurement
1 CPU Usage Longer intervals, once in 2-3 hours
2 Virtual Bytes Longer intervals, once in 2-3 hours
3 Private Bytes Longer intervals, once in 2-3 hours
4 Pool Paged Bytes Longer intervals, once in 2-3 hours
5 Pool nonpaged Bytes Longer intervals, once in 2-3 hours
6 Working set Longer intervals, once in 2-3 hours
7 Thread Count Longer intervals, once in 2-3 hours
8 Average CPU usage Shorter intervals, once in 2-5 minutes
9 Average Virtual Bytes Shorter intervals, once in 2-5 minutes
10 Average Private Bytes Shorter intervals, once in 2-5 minutes
11 Average Pool Paged Bytes Shorter intervals, once in 2-5 minutes
12 Average Pool nonpaged Bytes Shorter intervals, once in 2-5 minutes
13 Average Working set Shorter intervals, once in 2-5 minutes
14 Average pages/sec Shorter intervals, once in 2-5 minutes
15 Average interrupts/sec Shorter intervals, once in 2-5 minutes

Counters for ASP.NET and ASP.NET application

No Counter Frequency of measurement
1 Average request Shorter intervals, once in 2-5 minutes
2 Average request execution time Shorter intervals, once in 2-5 minutes
3 Average request wait time Shorter intervals, once in 2-5 minutes
4 Average request executing Shorter intervals, once in 2-5 minutes
5 Request total Longer intervals, once in 2-3 hours
6 Output cache hits Longer intervals, once in 2-3 hours
7 Output cache misses Longer intervals, once in 2-3 hours
8 Average output cache entires Shorter intervals, once in 2-5 minutes

Counters for W3WP (worker process)

No Counter Frequency of measurement
1 Average aggregated CPU usage process information Shorter intervals, once in 2-5 minutes
2 Average virtual bytes Shorter intervals, once in 2-5 minutes
3 Average private bytes Shorter intervals, once in 2-5 minutes
4 Average pool paged bytes Shorter intervals, once in 2-5 minutes
5 Average pool nonpaged bytes Shorter intervals, once in 2-5 minutes
6 Average working set Shorter intervals, once in 2-5 minutes
7 Average thread count Longer intervals, once in 2-3 hours
8 Average handle count Longer intervals, once in 2-3 hours
9 Average number deployed Longer intervals, once in 2-3 hours

 Subscribe to my blog

WCF error: The service cannot be activated because it does not support ASP.NET compatibility

Home | WCF | WCF error: The service cannot be activated because it does not support ASP.NET compatibility

I got the following error when I was trying to host my WCF service in IIS 7.5 using WsHttpBinding

The service cannot be activated because it does not support ASP.NET compatibility. ASP.NET compatibility is enabled for this application. Turn off ASP.NET compatibility mode in the web.config or add the AspNetCompatibilityRequirements attribute to the service type with RequirementsMode setting as ‘Allowed’ or ‘Required’.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.InvalidOperationException: The service cannot be activated because it does not support ASP.NET compatibility. ASP.NET compatibility is enabled for this application. Turn off ASP.NET compatibility mode in the web.config or add the AspNetCompatibilityRequirements attribute to the service type with RequirementsMode setting as ‘Allowed’ or ‘Required’.

Solution:

One of the  solution is to turn-off ASPNet compatibility in service configuration file

<serviceHostingEnvironment aspNetCompatibilityEnabled="false"/>. It worked for me.

WCF error: SOAP security negotiation failed for target

Home | WCF | WCF error: SOAP security negotiation failed for target

I got this error when I tried to host the WCF service in the IIS 7.5 using WSHttpBinding.

Exception
[System.ServiceModel.Security.SecurityNegotiationException] {"SOAP security negotiation with ‘http://localhost/Migraton/MigrationService.svc’ for target ‘http://localhost/OrderService/OrderService.svc’ failed. See inner exception for more details."}

Inner Exception
[System.ComponentModel.Win32Exception] {"The Security Support Provider Interface (SSPI) negotiation failed."}

Solution

The solution was to change the following userPrincipalName in the <userPrincipalName value="MACHINENAMEASPNET" /> to <servicePrincipalName value="host/localhost" /> . This did the trick and solved the issue.

Microsoft MVP 2012

Home | General | Microsoft MVP 2012

Year 2012 is off to a great start. Received my MVP renewal.

Congratulations! We are pleased to present you with the 2012 Microsoft® MVP Award! This award is given to exceptional technical community leaders who actively share their high quality, real world expertise with others. We appreciate your outstanding contributions in SharePoint Server technical communities during the past year.