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.

This error appears in the report server log:

ASSERT: Assertion failed! un-named assertion fired for component processing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException
This error will appear in your web browser when accessing the report:

Reporting Services Error An internal error occurred on the report server. See the error log for more details (rsInternalError)

Solution:
Install SQL Server 2005 Service Pack 3

The cause is SQL server timing values may be incorrect when you use Cool’n'Quiet technology in AMD processors or SpeedStep technology in Intel processors. It can also occur on virtual servers on VMware (Intel or AMD).

Here are some links I hope you may find useful:

Link 1:
http://blogs.msdn.com/b/mariae/archive/2007/12/10/reporting-services-internal-error.aspx

Link 1: Mentions that AMD Cool’n’Quiet settings is the culprit, on further reading on the internet, I have found out that this can occur on intel systems (SpeedStep technology) as well.

Link 2:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;931279

Link 2: States that the issue is a drift may occur between CPU frequency values and the problem was first corrected in SQL 2005 SP 3.
The Microsoft KB article 931279 states that this can occur if we use the CPU stepping or various Windows OS ‘power schemes’ settings. While the former (CPU stepping) is a bit more tricky to check, it would be worth checking the power scheme settings (Start>run>powercfg.cpl).

Link 3:
http://support.microsoft.com/kb/955706/en-us (SQL 2005 SP 3)

Link 3 contains a list of bugs that are fixed by SP3. There evidence that it fixes the SQL server timing values – KB article 931279 (Link 2).

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.

No doubt, depending on your SSP functionality, there is excel services and the BDC which has seperate SharePoint 2010 Service Applications.

Search is now an OOTB Out of the Box ’service’ in SharePoint 2010. I have also written other posts in this blog on Search on SharePoint 2010 with specific focus on the more superior FAST Search for SharePoint 2010.

Here is the pathway you can follow to migrate your SSP into SharePoint 2010:
http://technet.microsoft.com/en-us/library/cc263299.aspx#SSP

Upgrade the shared services database

1. Create an application pool for the User Profile service.
2. Verify that the Managed Metadata service is enabled.
3. Enable the User Profile service and upgrade the SSP database.
4. Create a new proxy for the User Profile service application and associate it with the default proxy group.

 Here is the pathway you can follow to migrate your SSP into SharePoint 2010:
http://technet.microsoft.com/en-us/library/cc263299.aspx#SSP

Solution:
1. Ensure that no other users have checked-in the page. You may have to ensure that the page has been Checked-out for you to to edit the page.
2. Ensure you have the appropriate permissions to edit the page.

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

• Stream: http://go.microsoft.com/fwlink/?LinkId=169126
• Download: http://go.microsoft.com/fwlink/?LinkId=169127

Deploy Project Server – Multi Application Server Farm

• Stream: http://go.microsoft.com/fwlink/?LinkId=169128
• Download: http://go.microsoft.com/fwlink/?LinkId=169129

Create Project Web Access Site:

• Stream: http://go.microsoft.com/fwlink/?LinkId=169130
• Download:  http://go.microsoft.com/fwlink/?LinkId=169131

Configure Reporting:

• Streaming: http://go.microsoft.com/fwlink/?LinkId=169132
• Download: http://go.microsoft.com/fwlink/?LinkId=169133

Add an Application Server to a Project Server Farm:

• Streaming: http://go.microsoft.com/fwlink/?LinkId=169134
• Download: http://go.microsoft.com/fwlink/?LinkId=169135

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

The form cannot be rendered. This may be due to a misconfiguration of the Microsoft SharePoint Server State Service. For more information, contact your server administrator.

Solution:
You would need to install the ‘State Service’ via the Configuration wizard in Central Administration or via PowerShell.

To configure the State Service by using Windows PowerShell:
1. Click Start, Administrative Tools, Windows PowerShell Modules.
2. In Windows PowerShell, type $serviceApp = New-SPStateServiceApplication -Name “State Service”
3. Create a State Service database and associate it with a service application, by typing New-SPStateServiceDatabase -Name “StateServiceDatabase” -ServiceApplication $serviceApp
4. Create a State Service Application Proxy and associate it with the service application by typing New-SPStateServiceApplicationProxy -Name “State Service” -ServiceApplication $serviceApp -DefaultProxyGroup
(You can use another proxy group if necessary by changing the DefaultProxyGroup parameter)

Tip:

You can view a list of all State Service cmdlets in Windows PowerShell by typing gcm *spstate*

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.

Summary

ULSViewer allows users to open a ULS log file and display its contents in a user friendly format. Users can then perform advanced functions such as filtering, sorting, highlighting, loading logs, appending logs, etc in order to single out the data that is important to the user. This information can be used to diagnose problems with machines running ULS services, or to monitor machines and the events they create in realtime.

Introduction

This article discusses the ULS Viewer tool.

Warning: The ULSViewer tool is an unsupported application that can be used to analyze ULS log files. Microsoft does not provide support for this tool. Use this tool at your own risk. Microsoft Product Support Services (PSS) cannot answer questions about the ULSViewer tool.

ULSViewer allows users with access to ULS log files to view their logs in a more user friendly interface instead of using standard log file viewers. Logs opened can be filtered, sorted, highlighted, appended, etc in order to single out the data that is important to the user. This information can be used to diagnose problems with machines running ULS services, or to monitor machines and the events they create.
The ULSViewer tool runs on either 32 or 64 bit architectures of Microsoft Windows 2003 Server, Windows 2008 Server, Windows 2008 Server R2, Windows 7, Windows Vista, and Windows XP.
Features      
The ULSViewer tool performs various actions against the data from ULS log files in order to better analyze it.  ULSViewer allows the user to:

• Highlight data of importance to the user on the fly
• Bookmark log entries
• Append logs to other logs in order to track trends
• Hide unimportant data
• Only view critical log entries by sorting data by severity
• Write rules to prompt the user when certain events occur
• View your data in a spreadsheet instead of the text file ULS generates
• Monitor remote machines logs that are running ULS services
• Open multiple logs at the same time in order to compare log files.
• Open logs files from multiple machines at the same time.

Installation

To obtain the ULSViewer tool, follow these steps:

1. The following file is available for download from the MSDN Code Gallery ULSViewer site at: http://code.msdn.microsoft.com/ULSViewer

Download the ULSViewer tool now.http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=ULSViewer&DownloadId=7482)

1. In the File Download dialog box, click Save, and then save the file to your machine.
2. When the download is completed, click Close.
3. In the folder you saved the file, double-click ULSViewer.exe.

Usage Syntax

UI Detail

Glossary