Skip to main content

Loop Back Issue in Sharepoint


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.
6. Exit Registry Editor
7. Restart your computer.
Labels:

Comments

Post a Comment

Popular posts from this blog

How to find Sharepoint DB

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.
86 comments
Read more

Ajax Integration with sharepoint

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"
4 comments
Read more

Creating Custom Timer Job

Timer Job is something which comes into mind when you are looking for batch process in sharepoint.In most of the realtime sharepoint site requires Pulling data from some other application and update the data in sharepoint.In some other scenario we need to synchronize information or Updata date in every day, or give the admin a flexibility execute some batch processing.Its realy good idea to create a Custom Scheduled Job.Let see a Basic skelton code. using Microsoft.SharePoint; using Microsoft.SharePoint.Administration; //Class should inherit from  SPJobDefinition Public class SampleJob :  SPJobDefinition {        //You could Define Custom properties         [Persisted()]         public string MyCustomProperty; ///Implement Following three constructors public SampleJob (): base(){  } public SampleJob (string jobName, SPService service, SPServer server, SPJobLockType targetType): base (jobName, service, server, targetType) { } public SampleJob (string jobName, SPWebAp
5 comments
Read more