Active Directory Membership Provider An Operations Error Occurred
Contents |
here for a quick overview of the asp.net active directory membership provider site Help Center Detailed answers to any questions you might have Meta active directory membership provider example Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Randomly getting “An operations error occurred in ActiveDirectoryMembershipProvider” up vote 1 down vote favorite I have two application running on the same server, using the same forms based authentication:
(Nederlands)Polska (Polski)România (Română)Singapore (English)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)香港特別行政區 (中文) Microsoft Home Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Problem with AD membership provider version Dynamics > CRM Labs Solutions Question 0 Sign in to vote The portal seems to work ok and lead flows to CRM. But if i try and login, following error comes: any ideas? --- Server Error in / Application. Configuration Error Description: http://stackoverflow.com/questions/23699717/randomly-getting-an-operations-error-occurred-in-activedirectorymembershipprovi An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: An operations error occurred. Source Error: Line 39: for an ASP.NET Web Site is a really nice. It allows you to give users accounts based onSQLaccounts it creates. I however wanted to use Active Directory instead of SQL and do the userauthenticationthere instead of setting it on the entire IIS site. This also allows you to have a much prettier login page rather than the normal web browser's "basic access authentication" prompt. I figured that changing the ASP 4.0 WebSite to use Active Directory would be be a GUIwizardto do it but found a largeamountof confusion on the subjectwhen I was researching how. After Figuring it out for myself I figured I'd write a guide on how. Setup your machine Serveral of the problems I observed were people had problems with their website and Visual Studio install before they even started with change the website to use AD. Start by creating a WebSite from the "ASP.NET Web Site" using .Net Framework 4. Don't make a single change and build and run the project. Does the site come up. Can you register a user account and then login to that user account. If not don't proceed any further till you can. The cause for this for many people was that the website went to use the SQLEXPRESS instance only to find that it wasn't installed or running. As a result you'll get the following error from IIS. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) Changing the Template to use Active Directory Nearly everything nessory is done in the web sites root web.config file. Below is a copy of the complete file. Add connectionStrings "ADService" to domain your going to use.example"LDAP://nku.edu" (note i tried to alter this to use ) Notice that we remove theAspNetSqlMembershipProvider and addedAspNetActiveDirectoryMembershipProvider. Making sure to set AspNetActiveDirectoryMembershipProvider as the default membership provider. Setting attributeMapUsername tosAMAccountName