Common symptoms of non-performing SharePoint code

The following are the common symptoms of a non-performing SharePoint code.

1. Frequent IIS Application Pool Recycling during the peak usage of the portal

The general practice is to allocate the IIS Application Pool Memory between 800MB – 1.5GB, assuming that at least 4GB RAM is available on the machine. The IIS App Pool recycle setting limit plays an important part in the recycling of app pool memory. The idea is that app pool re-cycle settings should not be too high or too low. The recommended app pool reset limit is 1 GB. Even after all this, the IIS App Pool resets frequently, then it has to be with SharePoint code. Make sure that the native SharePoint objects are disposed explicitly.

2. Poor Application Performance

Another symptom of a non-performing SharePoint code is the Poor Application performance. Meaning, during the peak load (when the memory usage increases), system would struggle to do paging and memory fragmentation, to compensate the load.

3. High Memory Usage for IIS Worker Process Memory

When the memory usage increases, the application would struggle to handle memory allocation. In many cases, this leads to “Out of Memory” exception, which leads to application crash, when unhandled in the code.

4. High Memory Usage for SQL

The common symptom of a non-performing SharePoint application is the high memory usage for SQL Process, when the system usage is not high. If the above symptoms persist, even after proper memory management in the code, then the Capacity Planning needs & sizing needs to be re-visited again.

 Subscribe to my blog

Installing SharePoint Foundation 2010 on Windows 7

One of the major improvement of SharePoint 2010 product is its ability to install and run on the client operating system like Windows 7. This article would elaborate the steps to install SP  Foundation 2010 on Windows 7 (X64). The configuration of my laptop is Intel I5 Processor, 4GB RAM and set up with Windows 7 Enterprise Edition (X64) & Visual studio 2010 Service Pack1.


Step1 –

Install WCF hotfix for Windows 7 located in


Install ADO.NET Data Services updates for .NET 3.5 SP1 located in


The next step is to install the other additional pre-requisites. The pre-requisite installer cannot be leveraged while installing SP Foundation 2010, unlike the installation of SP Server 2010. So the following pre-requisites have to be manually installed.


a) Microsoft Sync Framework

b) SQL Server Native Client

c) Windows Identity Foundation


Step 4

Enable the set of required Windows Features by running the following scripts

start /w pkgmgr /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures;^


Step 5

The next task is to extract the SharePoint Foundation installer (SharePointFoundation.exe), apply required attributes for the configuration file.

Copy the SharePointFoundation.exe in to the folder where you want to install.

Extract the installer by typing the following in the command prompt
c:YourFolderSharePoint /extract:c:YourFolder


Open the Config.xml located in c:YourFolderfilesSetupconfig.xml

Add the following snippet inside <configuration> tag
<Setting Id="AllowWindowsClientInstall" Value="True"/>

Please make sure the the installer (SharePointFoundation.exe) is extracted only using the Extract option in Command prompt. If it is extracted using Winzip, it will given an error like “The language of this installation package is not supported”

Run SharePointFoundation.exe and install it as ‘StandAlone’







Run the SharePoint Configuration Wizard. If you are doing a standalone setup of SP Foundation2010, there is no need to install Microsoft SQL Server 2008 KB 970315 x64  hotfix.

Now it’s all set the SP Foundation 2010 setup is complete.