Link to home
Start Free TrialLog in
Avatar of Bart Spearen
Bart Spearen

asked on

With IIS 7.5, different error message displayed vs in logs

Pertinent info:
IIS 7.5
Win 7
Classic App Pool

I receive a 401.2 error on screen but 401.5 error in the logs. Have anyone else seen this?

I have 3 sister applications that usually all install on a machine (usually IIS 7) and work out of the box.  In this scenario (see above), 1 of the 3 fails with the 401.2 error displayed and 401.5 error in the logs.  The one that fails is developed by the same team as one of the working apps and their web config is almost exact (modules and handlers). The permissions on their folders are also identical.

Has anyone seen this before where two different error codes are displayed and is there a solution for such?

I can post more information if needed.

Thanks.
Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

the 401 series of errors all relate to logon failures. does iuser_machinename or iusers group have read access to the websites folders


The URL you attempted to reach has an ISAPI or CGI application installed that verifies user credentials before proceeding. This application cannot verify your credentials
HTTP Error 401.5 - Unauthorized: Authorization failed by an ISAPI/CGI application.
Internet Information Services (IIS)
Avatar of Bart Spearen
Bart Spearen

ASKER

Thanks for commenting. Sorry for the delay as I had to put it away since this is so stupid.

 To answer your question, yes, IUSR has Full Control.

The initial permissions were the inherited ones from wwwroot.  I have in turn given IIS_IUSRS, Administrators, IUSR, Users, Network Service, and Everyone Full Control and I received the same error.

The other apps I mentioned above have just the inherited ones from wwwroot and they work, btw.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.