Sharepoint 2010

Master Page 1. Add the following tag just below the form tag of master page <asp:ScriptManager ID="ScriptManager1" runat="server" EnablePartialRendering="true" /> Web.Config 1. Add safe control <SafeControl Assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Web.UI" TypeName="*" Safe="True" /> 2. Add the http handler inside <httpHandlers> tag of web.config <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> <add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"

This is a common issue called Double Hope issue in IIS and troubles most Sharepoint / Asp.net application which consume the resource in other servers .In application development most of the one talks to different application resides in multiple servers. Problem This issue occurs when you try to access the resource outside server with current logged in user credentials. In this scenario first hope occurs when user access the page from client browser that time its authenticate the user with his own windows credentials. The second hope occurs when IIS try to access the other server with the current user credential. In SharePoint world most of the application uses windows authentication to authenticate the user and impersonation also set to true. Our application want talk to other application.Let say for example a webservice in another physical server or a sharepoint service in another Farm .In this scenario during the second hope IIS will pass the credentials with hashed password ,so

In sharepoint world you should know where the sharepoint database is to trouble shoot database related issues.Some one come to you and say i am getting unable to connect to database error or my sharepoint is down.So you may not know the details of the environment.In first step you need to identify the  servers so you have to find the configdb and content db servers. How to find the Config DB Configuration database connection string is stored in Registry key. So sharepoint look for that entry to identify the database. In Sharepoint 2007 you could see the config DB conection string in Following Registry Key My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ConfigDb In Sharepoint 2010 you could see the config DB conection string in Following Registry Key My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\Secure\ConfigDb The Next thing you have to find the Content DB attached to Web application.

Issue  Browse a SharePoint Web Application which uses a fully qualified domain name from a WFE in the farm you will get a 401.1. This error code means there is a problem with the user credentials but nothing to do with invalid credentials. Windows Server 2003 SP1 introduced a loopback security check. By default this feature enabled in Windows Server 2008. The feature prevents access to a web application using a fully qualified domain name (FQDN) if an attempt to access it takes place from a machine that hosts that application and shows a 401.1 Access Denied from the web server and a logon failure in the event log. How to Solve this You need to create a DWORD registry key called DisableLoopbackCheck and set it to 1. Steps 1. Start -> Run, type regedit 2. Go to following registry key    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa 3. Add a new DWORD Value in LSA key. 4. Type DisableLoopbackCheck , and then press ENTER. 5. Modify  DisableLoopbackCheck and set Value to 1 .