SharePoint 2010 – HTTP Throttling & Request Monitoring

Experienced SharePoint administrators would know that over worked servers would drop requests randomly when it can’t handle the load. Sounds familiar?

You could now configure thresholds in SharePoint 2010 and every 5 seconds teach server checks various aspects of its performance such as available Server CPU, Memory, Request Wait Time and ASP.NET request queues.

After 3 unsuccessful checks, the server enters a throttling period and will remain in this state until a successful check is completed.

The following occurs during the HTTP Throttling period:

  • No new timer jobs will be started. Requests that were generated before the throttling mode will be completed.
  • The server will still continue to accept connections from existing sessions. This will, in theory, keep users from losing any current work when the server begins to throttle requests.
  • Any new HTTP GET and Search Robot requests will generate a 503 (Server busy) error message and will be logged in the event viewer.
  • The server continues to check itself every 5 seconds and stays throttled until the metrics fall back into the acceptable ranges.

Configuration:
Throttling can be configured per Web application and is enabled through the Central Administration user interface or through a Windows PowerShell™ command.
To configure via Central Administration:

  1. In SharePoint 2010 Central Administration, select Application Management -> Manage web applications.
  2. Select the web application you want to configure
  3. Click General Settings on the Ribbon
  4. Select Resource Throttling
  5. Select On or HTTP Request

After throttling is enabled, the Windows PowerShell commands can be used to view and adjust the throttling thresholds:
GetSPWebApplicationHttpThrottlingMonitor

SetSPWebApplicationHttpThrottlingMonitor

The image from TechNet (below) is an example of the GetSPWebApplicationHttpThrottlingMonitor Windows PowerShell command.

  • Share/Bookmark

fixmlindex.exe FAST Search Server 2010 for SharePoint 2010 – High CPU and Memory usage

FAST Search Server 2010 Backend

Symptoms: fixmlindex.exe process consumes high CPU and memory usage on FAST Search server 2010 for SharePoint 2010.

Cause: Adding many managed properties to schema over time may lead to high memory usage in the fixmlindex.exe process.

Solution: To work around this, either reinstall FAST Search and apply the schema changes in one go, or follow this procedure:

  1. Perform all schema updates before starting feeding.
  2. Stop the FASTSearchService
  3. Remove the file
  4. etc\config_data\Schema\webcluster\summaryclasses.xml
  5. Start the FASTSearchService
  6. Start feed.
  • Share/Bookmark

Microsoft Project Server 2010 Requirements

Been doing some reading on Microsoft Project Server 2010. Here are some essential requirements to factor in for your new Project Server 2010. My next post will point out the hardware and software requirements for Project Server 2010.

Microsoft SharePoint Server 2010
64 Bit Only Hardware
Internet Explorer 7 or Higher
Windows 2008 (SP2 or later or R2)
SQL Server 2005 SP3 CU3 or SQL Server 2008 SP1 CU2 or SQL Server 2008 R2
Setup and Migration Documentation

The setup and upgrade documentation is located here.  

http://technet.microsoft.com/en-us/library/cc197280(office.14).aspx

Videos

Deploy Project Server – Single Application Server Farm

Deploy Project Server – Multi Application Server Farm

Create Project Web Access Site:

Configure Reporting:

Add an Application Server to a Project Server Farm:

Reference: http://blogs.technet.com/b/projectadministration/archive/2009/11/18/microsoft-project-server-2010-requirements.aspx

  • Share/Bookmark

SharePoint disable loopback check (DisableLoopbackCheck dword in registry)

Ive found this very handy.. recently, I was working on a server and we were trying to access the local SharePoint site http://127.0.0.1 or http://nameoflocalserver/pages/default.aspx and I was constantly prompted for the username and password. in SharePoint 2010 it can really annoy you by not accepting your username password credentials in the popup window.

Its a ‘feature’ on the server that you need to disable as a workaround..

You would need to create a DWORD registry key in the registry called DisableLoopbackCheck and set it to 1.
Follow these steps:

Click Start, click Run, type regedit, and then click OK
In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Right-click Lsa, point to New, and then click DWORD Value.
Type DisableLoopbackCheck, and then press ENTER.
Right-click DisableLoopbackCheck, and then click Modify.
In the Value data box, type 1 and then click OK.
Quit Registry Editor, and then restart your computer.

For more information about this, click the following article number to view the article in the Microsoft Knowledge Base: 281308 (http://support.microsoft.com/kb/281308/ ) Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name.

  • Share/Bookmark