Skip to main content

Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098)

While accessing the active directory (AD) and authorization manager (AZMAN) , If you get “  Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098) “ message check the  account that is being used to get the LDAP query from AD . 

ERROR DETAILS

Exception Details: System.Runtime.InteropServices.COMException: Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098)

Source Error:
Line 154:    'Session("FullName") = System.Security.Principal.WindowsIdentity.GetCurrent.Name.ToString()
Line 155:
Line 156:    If Not User.IsInRole("Role1") Then
Line 157:          Response.Redirect("./Login.aspx")
Line 158:    End If

 Stack Trace : ....

SOLVE IT

Steps to do check the app pool rights:

  1. Click on the website name that you are having problem with in IIS 
  2. In the right panel you will see 'Basic Settings'. Click It.
  3. Select the specific pool option and enter the name of the account@domain and the password. 
Please note that this app pool account will have the same domain user name . Sometimes having different names causes problems.
  1. Click Ok
  2. Test the site. 

WHY DID WE DO IT

The app pool account is being used to get the LDAP query from AD did not have rights to read the role


Having set multiple sites I have seen the major cause of problem is the rights of the account pool that is messed up. Even if it displays correctly sometimes just reentering it , solves it.

Comments

Popular posts from this blog

JavaScript Interview Questions

This is a compilations of all the interview questions related to Javascript that i have encountered.  Q: Difference between window.onload and onDocumentReady? A: The onload event does not fire until every last piece of the page is loaded, this includes css and images, which means there’s a huge delay before any code is executed. That isnt what we want. We just want to wait until the DOM is loaded and is able to be manipulated. onDocumentReady allows the programmer to do that. Q:  What is the difference between == and === ? A: The == checks for value equality, but === checks for both type and value. Few examples: "1" == 1; // value evaluation only, yields true "1" === 1; // value and type evaluation, yields false "1" == true; // "1" as boolean is true, value evaluation only, yields true "1" === false; // value and type evaluation, yields false Q: What does “1″+2+5 evaluate to? What about 5 + 2 +...

SQL Server 2008 - Inline Variable Assignment

Microsoft SQL Server 2008 brings in a new feature of 'Declaring and Assigning' a variable all in a single line. Earlier, while using SQL 2005 and earlier versions, we had to declare a variable before assigning it. This feature is explained in detail below. In SQL 2005 and earlier versions we had to write: Declare @age int Declare @name nvarchar(25) Declare @date date Set @age = 25 Set @name = "Garry" Set @date = GETDATE() With SQL 2008 we can combine both these statements to write Declare @age int = 25 Declare @name nvarchar(25) Declare @date @date = GETDATE() Advantage : This helps us to write less code, yet get the same functionality. Even though this feature has been available it is not being used in many projects because of backward compatibility issue. If the same code is being used on both 2005 and 2008 server we would prefer writing in a format compatible to both. Do share with us :  Would you like to use this new method? If not, why?