Error message 401.2.: Unauthorized: Logon failed due to server configuration. When application deployed

Question

I have an asp.net 4.0 application that works fine running under cassini but when i deploy to IIS i get the above error. It is running under the Default App pool which a number of other apps use and work fine. Here is a copy of my web config which may be the source:

<!--
  For more information on how to configure your ASP.NET application, please visit
  http://go.microsoft.com/fwlink/?LinkId=169433
  -->

<configuration>
  <connectionStrings>
    <add name="FMLconnect" connectionString="Server=192.168.20.125;Port=;Database=FML;Uid=******;Pwd=*****;pooling=false;" providerName="MySql.Data.MySqlClient"  />
  </connectionStrings>

  <system.web>
    <httpHandlers>
      <add path="ChartImg.axd" verb="GET,HEAD,POST" type="System.Web.UI.DataVisualization.Charting.ChartHttpHandler, System.Web.DataVisualization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="false"/>
      <add path="ChartImage.axd" type="Telerik.Web.UI.ChartHttpHandler" verb="*" validate="false"/>
      <add path="Telerik.Web.UI.SpellCheckHandler.axd" type="Telerik.Web.UI.SpellCheckHandler" verb="*" validate="false"/>
      <add path="Telerik.Web.UI.DialogHandler.aspx" type="Telerik.Web.UI.DialogHandler" verb="*" validate="false"/>
      <add path="Telerik.RadUploadProgressHandler.ashx" type="Telerik.Web.UI.RadUploadProgressHandler" verb="*" validate="false"/>
      <add path="Telerik.Web.UI.WebResource.axd" type="Telerik.Web.UI.WebResource" verb="*" validate="false"/>
      <add path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>
      <add type="Telerik.ReportViewer.WebForms.HttpHandler, Telerik.ReportViewer.WebForms, Version=5.1.11.928, Culture=neutral, PublicKeyToken=a9d7983dfcc261be" path="Telerik.ReportViewer.axd" verb="*" validate="true"/>
    </httpHandlers>
    <compilation debug="true" targetFramework="4.0" >
      <assemblies>
        <add assembly="Microsoft.Build.Framework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <!--<add assembly="Microsoft.ReportViewer.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>-->
        <add assembly="System.Data.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.Management, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.Web.DataVisualization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
      </assemblies>
    </compilation>




  </system.web>

  <system.webServer>
       <validation validateIntegratedModeConfiguration="false" />
    <modules runAllManagedModulesForAllRequests="true" />
  </system.webServer>
</configuration>

Michael G · Answer 1 · 2020-08-11T23:26:17.507

19

This always happens to our project after it's reloaded.

If you're using Windows Authentication, the problem might be as simple as updating your project properties to Enable Windows Authentication.

In Visual Studio, get to your project properties (I usually right-click a file > properties to open the properties window. Then click on my project). Make sure Windows Authentication is set to Enabled

edited Aug 11 '20 at 23:26

answered Jun 24 '20 at 16:11

Michael G

535
4
12

3

Sometimes the easiest answer is the best. Thanks for pointing it out. Fixed my problem – Tim Oct 05 '21 at 19:27

score 13 · Answer 2 · answered Sep 28 '12 at 13:03

13

With IIS, this really just sounds like you need to check the authentication settings for your app in IIS Admin. Try this link: http://support.microsoft.com/kb/253667

This is for IIS6, you didn't mention whether you were using IIS 6 or 7. For IIS 7, try this: http://support.microsoft.com/kb/942043

answered Sep 28 '12 at 13:03

imjohnking

335
1
6

1

It's IIS 7. Seen those support articles earlier, made no difference. – user1240615 Sep 28 '12 at 14:03
4

For me, Windows Authentication was not installed by default with IIS 7. – roadsunknown Dec 28 '12 at 00:54
Thanks imjohnking, for some reason Windows Authentication was not installed on my either. The resolution steps on http://support.microsoft.com/kb/942043 helped me get my application working. – hatsrumandcode Jan 08 '14 at 09:34
Links are dead now. – Spencer Jan 08 '21 at 13:30
Strange enough my other apps using authentication mode="windows" are working without checking the IIS option. But one particular app doesn't work without checking it. – Cal Aug 19 '21 at 19:36

score 11 · Answer 3 · answered Apr 24 '14 at 15:26

If you're working with IIS Express, check the web.config

        <!--  AUTHENTICATION 
      This section sets the authentication policies of the application. Possible modes are "Windows", 
      "Forms", "Passport" and "None"
-->
    <authentication mode="Windows"/>
    <identity impersonate="true"/>
    <!--  AUTHORIZATION 
      This section sets the authorization policies of the application. You can allow or deny access
      to application resources by user or role. Wildcards: "*" mean everyone, "?" means anonymous 
      (unauthenticated) users.
-->
    <!--<authorization>
        <deny users="?"/>-->
        <!-- Allow all users -->
        <!--  <allow     users="[comma separated list of users]"
                         roles="[comma separated list of roles]"/>
              <deny      users="[comma separated list of users]"
                         roles="[comma separated list of roles]"/>
        -->
    <!--</authorization>-->

score 8 · Answer 4 · edited Mar 23 '17 at 15:26

I upgraded a VS2012 project to 2013 and it changed the Project property from Windows Authentication from Enabled to Disabled and I was then getting this error. Simple change solved the problem. Go to solution and click properties to change this.

If you are using IISExpress, the lines should look something like:

<IISExpressAnonymousAuthentication>disabled</IISExpressAnonymousAuthentication>
<IISExpressWindowsAuthentication>enabled</IISExpressWindowsAuthentication>

score 8 · Answer 5 · answered Feb 10 '16 at 17:31

8

I had the same problem just now. None of the fixes I found worked, so I'll just post here in case it helps someone.

For me the issue was solved this way:

Open IIS manager
Select "Application Pools"
Right click on the application pool you are using and select "Advanced settings"
Set "Enable 32-Bit Applications" to "True"
Click "OK" to close the dialog box
Right click on the application pool again and select "Recycle"

Hope that will help someone else out! This was driving me crazy.

answered Feb 10 '16 at 17:31

Blake

109
3
7

1

We're having this trouble on one particular server, but not others. Setting Enable 32bit "fixes" the issue but I don't know why (yet - I still hope to find a solution that makes sense to me). Thanks for the tip, at least it's now functional! – Jono Job Jun 22 '16 at 03:47
This was driving me crazy and turning on 32-bit made the site run again, but I have no idea why. I think it suddenly happened after I deleted the bin and obj folders in the presentation project, but I don't know if that was the case. Frustrating. – Kent Robin May 22 '17 at 12:16
Thank you sir, tried many other answers on different Q's and this resolved the issue – John Feb 08 '18 at 01:26

score 6 · Answer 6 · answered Jun 16 '14 at 16:27

Try this:

Open IIS Manager
Click on your web server (i.e. the server itself; not a site) in the connections bar.
Select Authentication from the IIS section.
Enable protocols as required. Anything disabled here will not be available to sites hosted on this server; anything enabled here will use the individual site's settings.
Restart IIS (start, run, cmd (run as admin), iisreset -noforce)

score 3 · Answer 7 · answered Jul 24 '18 at 15:11

3

For me, I had to change settings from the "Properties" panel to fix this issue. Select project and hit F4 (menu: View->Properties Window) and set properties accordingly.

Visual Studio 2015 - Properties panel screen shot

Hope this helps!

answered Jul 24 '18 at 15:11

Codac

31
1

score 3 · Answer 8 · answered Oct 11 '18 at 14:50

I resolved 401.1 and 401.2 authentication errors by adding BackConnectionHostNames to the registry using these directions: https://support.microsoft.com/en-us/help/896861/you-receive-error-401-1-when-you-browse-a-web-site-that-uses-integrate (Method 1)

Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
Right-click MSV1_0, point to New, and then click Multi-String Value.
Type BackConnectionHostNames, and then press ENTER.
Right-click BackConnectionHostNames, and then click Modify.
In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.
Quit Registry Editor, and then restart the IISAdmin service.

These errors were occurring on a Windows 10 Professional install running version 1803, on a domain that is named differently than the site I was attempting to authenticate to.

score 3 · Answer 9 · answered Dec 18 '19 at 18:07

If you are using Windows Authentication, it could be your authorization settings. Open web.config file:

  <system.web>
    <authentication mode="Windows"></authentication>
    <identity impersonate="false" />
    <authorization>
        <allow roles="domain_name1\group_name1,domain_name2\group_name2" />
      <deny users="*" />
    </authorization>

Make sure you have assigned the correct roles. If you need to include all users, use:

<allow users="*" />

score 2 · Answer 10 · edited May 23 '17 at 11:33

This might be a very late answer, but the problem in my case was a mis-configured Publish profile (Using Web Deploy). As soon as I deselected the Precompile during publishing option (below) and re-published, it came back to normal and I was able to access it.

I also tried activating/deactivating it a couple of time and that confirmed it was the sole reason. The problem appeared when I activated it again and disappeared when I unchecked it.

enter image description here

And to be honest, I still don't have an explanation about what impact does this option have exactly and why it is the cause of such problem. I found this question but I am still investigating.

score 1 · Answer 11 · answered Dec 18 '18 at 06:24

I had a similar issue and resolved it by setting optimizeCollections to false in web.config and immediately reverting the change after verifying that it worked.

  <system.web>
    ..
    <compilation debug="true" targetFramework="4.7.1" optimizeCompilations="false" />
    ..
  </system.web>

Perhaps the same thing could have been achieved by deleting asp.net temp folder..

score 1 · Answer 12 · answered Mar 22 '19 at 14:46

what helped to me is commented out the lines below in the web.config

<system.web>
    <compilation debug="true" targetFramework="4.5.2" />
    <httpRuntime targetFramework="4.5" />
    <!--  
    <authentication mode="Windows" /> 
    <authorization>
        <deny users="?" />
    </authorization>
    <identity impersonate="false" />
    -->
    <customErrors mode="Off" />
</system.web>

score 0 · Answer 13 · answered Nov 17 '15 at 02:59

I was also getting this error trying to run an existing ASP.NET WebForms application under IIS Express (but this probably also applies to IIS).

The application was configured in the applicationhost.config to use the Clr4IntegratedAppPool application pool. Changing the applicationPool attribute to Clr4ClassicAppPool solved the problem for me.

score 0 · Answer 14 · answered Jun 17 '19 at 04:23

0

If it is a windows authentication based app, then enable Windows Authentication for your site in IIS and disable Anonymous Authentication.

answered Jun 17 '19 at 04:23

Sajithd

529
1
5
11

score 0 · Answer 15 · answered Nov 17 '20 at 09:34

I had the same error, where the application is running fine locally, but gives Unauthorized error when running from IIS. I tried several methods but no luck. I finally used the below method:

I was using Anonymous Authentication, which was not able to work correctly as it was unable to find path to the code files. Therefore, I set the Windows Authentication to True and VOILA! it worked.

You can find Windows Authentication by clicking your application name in the left hand side pane - Select Authentication - Windows Authentication (set to Enabled).

Also, if you cannot fine Windows Authentication here, you need to select it from Control Panel - Program featutes - Turn windows fetures on or off - IIS - World wide web services - Security- Windows authentication (check it). Now go to IIS and you will find it.

score 0 · Answer 16 · edited Feb 22 '22 at 05:25

0

Click on your project inside the Solution Explorer to select the project.
Press F4 (for properties).
In the Properties pane for your project:
1. Set "Anonymous Authentication" to "Disabled".
2. Set "Windows Authentication" to "Enabled".

Then run the project.

edited Feb 22 '22 at 05:25

the Tin Man

158,662
42
215
303

answered Feb 20 '22 at 15:59

ANEESH BHASKAR

1

Error message 401.2.: Unauthorized: Logon failed due to server configuration. When application deployed

16 Answers16

Linked