The administrator cannot browse the site from the server and recieves an error 401.1 Unauthorized

ISSUE DESCRIPTION
===================
=> SharePoint site is browsable from the client machine with the host header.
=> When browsing from the server, it prompts for credentials three times and then we get 401.1  
      Unauthorized error.
=> On server, we can browse the SharePoint site with server name

Cause :-  This behavior is by design
======

RESOLUTION
============
There are two methods to work around this issue, use one of the following methods, as appropriate for your situation.

1. Specify host names (Preferred method if NTLM authentication is desired)

2. Disable the loopback check (less-recommended method)

Please check the Below Url for More detailed Description and the steps to follow for the Resolution .

http://support.microsoft.com/kb/896861

February 2011 CU for SharePoint 2010

Download SharePoint Foundation 2010 February 2011 CU
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbln=en-us&kbnum=2475880

Download SharePoint Server 2010 February 2011 CU
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbln=en-us&kbnum=2475878

Download SharePoint Server 2010 with Project Server February 2011 CU
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbln=en-us&kbnum=2475879

After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.

For the 2010 Server Products it is sufficient to install the SharePoint Server 2010 package as it includes the SharePoint Foundation package.

However i would suggest to go ahead and try to install both MSF and SP 2010

Sharepoint 2010 : Troubleshooting tips for the Synchronization Service

Below is a list of requirements and common points of failure for the user profile synchronization service.

If you have an issue with the sync service failing to start, stuck starting or stopping, verify the items below in the Your environment.

=> Verify that the Sync account is a member of the local administrators group.
=> Verify the account is a member of the farm administrators group.
=> Verify that a profile service application has been created prior to starting the sync service.
=> Verify that the application pool for the UPA is leveraging the farm account.

Look for SQL alias issues using CLICONFG – should be fixed with the CU1 update.

Verify proper permissions in SQL for Sync account – As this is leveraging the farm account, it should have DBCreator and SecurityAdmin.

Look at the registry keys for the FIM components: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\FIMService] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\FIMSynchronizationService]

Monitor ULSViewer during the sync service configuration with a filter of Category contains Profile applied.

Check Application and System logs for errors during configuration
Consider rebuilding the FIM registry keys – See FIMService file in the resources section of this document.
Consider rebuilding the User Profile Application to obtain a new sync database.

In this process you need to back up the profile and social databases, then specify those names where appropriate in the new UPA creation

While entering a new name to create a new sync db. This will recreate the UPA while preserving the social and profile data

Consider using Process Monitor to look for Access Denied issues

Verify if the domain was upgraded from Windows 2000.

 If so add the sync account to the “Pre-Windows 2000 Compatible Access” and “Windows Authorization Access” groups. If in doubt add the account being used by the sync service to those groups in AD as appropriate.

If service is stuck in starting or stopping, consider setting the FIM services back to their default values of Disabled and Local System, and rebooting the server.

SharePoint 2010 Service Pack 1

**** On Tuesday Service Pack 1 (SP1) for SharePoint 2010 was made available****

SP1 contains a number of important fixes that improve the SharePoint experience for our customers.

With the recommendation to install SP1 for SharePoint came a recommendation to Also deploy the June Cumulative Update (CU) for SharePoint simultaneously.

SharePoint 2010 and Office Server 2010 SP1
http://support.microsoft.com/kb/2532120

The SharePoint Server 2010 cumulative update refresh package (SharePoint server-package): June 30, 2011
http://support.microsoft.com/kb/2536599

Please refer the below link for further queries : http://blogs.technet.com/b/stefan_gossner/archive/2011/06/30/sharepoint-2010-service-pack-1-has-been-released-on-tuesday.aspx

Some useful Links for downloading tools for Sharepoint which includes Moss 2007 and 2010

SPSFarmReport : http://spsfarmreport.codeplex.com/

SPSReport : http://spsreport.codeplex.com/

Microsoft Network Monitor 3.4: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=4865

Fiddler 2.x: http://www.fiddler2.com/fiddler/version.asp

SharePoint Content Deployment Wizard : http://spdeploymentwizard.codeplex.com/

Wireshark: http://www.wireshark.org/download.html

ECTS - Deployment and Operations Guide

http://www.codeplex.com/CKS/Release/ProjectReleases.aspx?ReleaseId=15529

www.cjvandyk.com/blog/WSSTemplates/ITTeamWorkspace/Knowledge%20Base/Release_Notes.rtf



Note : Please discuss your ECTS issues on this blog

Unable to add active directory users to the sharepoint groups

This was something really new we figured out while working on this sharepoint site. We were unable to add the active directory users to the exisiting sharepoint groups in the site. We encountered the following error message “Operation aborted (Exception from HRESULT: 0×80004004 (E_ABORT)”. We had no clue where to look at and how to move ahead! Had some SQL expert advice on this one and eventually figured out the cause. This is how we progressed to resolution…

We edited the web.config file of the affected virtual server in the IIS and set the value for “CallStack” as true and set the value for “Custom Error” as off. We saved the file and reset the IIS. We tried to reproduce the error again and found the following error thread as follows:

Operation aborted (Exception from HRESULT: 0×80004004 (E_ABORT)) at Microsoft.SharePoint.Library.SPRequestInternalClass.UpdateMembers(String bstrUrl, Guid& pguidScopeId, Int32 lGroupID, Int32 lGroupOwnerId, Object& pvarArrayAdd, Object& pvarArrayAddIds, Object& pvarArrayLoginsRemove, Object& pvarArrayIdsRemove, Boolean bSendEmail) at Microsoft.SharePoint.Library.SPRequest.UpdateMembers(String bstrUrl, Guid& pguidScopeId, Int32 lGroupID, Int32 lGroupOwnerId, Object& pvarArrayAdd, Object& pvarArrayAddIds, Object& pvarArrayLoginsRemove, Object& pvarArrayIdsRemove, Boolean bSendEmail)

Upon research found that there is option in the SQL Server Instance called XACT_ABORT under Default Connection Options which needs to be unchecked. How would we do that? Follow these simple steps. Open the SQL Server Management Studio and check for the properties of the SQL Server Instance. Select Connection and under Default Connection Options, uncheck XACT_ABORT and save changes. Now that we are done with this we were able to add the users from the active directory to the existing sharepoint groups with no errors.

Here is the cause explained:

When SET XACT_ABORT is ON, if a Transact-SQL statement raises a run-time error, the entire transaction is terminated and rolled back. So, if we look at a sharePoint content database, if SQL runs into a transaction that fails, it will roll the changes back, essentially editing the database. If you break the role inheritance on a group you get two membership adherence lines into the database for that group and then when you try to add new users, and you get a SQL exception error, something like ” Violation of PRIMARY KEY constraint “Webmembers_PK”. Cannot insert duplicate key in object ‘dbo.members’. SharePoint functionality is not hindered by this error message but if the “xact abort” SQL option is enabled on the SQL server in the properties of the default instance under connections, then the transaction is rolled back by the SQL server and this generates a HRESULT abort error in SharePoint. This option is turned unchecked by default.