HTTP 401 errors are among the most common errors you may have to deal with in IIS. While the causes for these errors can vary greatly, the causes fall into a finite number of categories. Correctly identifying the category of the cause for your HTTP 401 error can decrease the amount of time needed to identify the root cause of the error.
This article describes the troubleshooting steps when you encounter HTTP 401.x errors (401.1, 401.2, 401.3, 401.4, 401.5) in Microsoft Internet Information Services (IIS):
- As an administrator or a developer, to troubleshooting HTTP 401.x error, firstly identify the substatus code (x) of the HTTP 401 error, and then use the corresponding resolutions to resolve this particular issue. Additionally, some recommended useful tools and Microsoft Knowledge Base articles for troubleshooting HTTP 401 errors are provided.
- As an end user, you have to contact the site administrator.
For IIS 6.0 or the later versions of IIS 6.0
Web logs. The Web logs are located in the following location:
the status, the substatus, and the Win32 status.
#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-Sub-status sc-win32-status2006-03-06 20:37:42 W3SVC1 192.168.1.101 GET /default.aspx - 80 - 192.168.17.45 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.1) 401 2 21480742542006-03-06 20:37:42 W3SVC1 192.168.1.101 GET /default.aspx - 80 - 192.168.17.45 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.1) 401 1 02006-03-06 20:38:36 W3SVC1 192.168.1.101 GET /default.aspx - 80 DOMAIN\user 192.168.17.45 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.1) 200 0 0
Microsoft makes no warranties and excludes all representations, warranties, and conditions whether express, implied, or statutory. These include but are not limited to representations, warranties, or conditions of title, non-infringement, satisfactory condition, merchantability, and fitness for a particular purpose, with regard to any service, solution, product, or any other materials or information. In no event will Microsoft be liable for any third-party solution that this article mentions.Until next time, thank you for your time, and have a great day. As always, feel free to submit ideas on topics you want addressed in future columns or in the Knowledge Base using the Ask For It form.
ID do Artigo: 907273 - Última Revisão: 14/02/2017 - Revisão: 1