IIS 7 and Above
Known Issues and Workarounds
Web site on IIS 7.0 occassionally asks to choose the credentials you...
Last post May 26, 2016 06:15 AM by lextm
May 24, 2016 01:38 PM|ryguytheITguy|LINK
Hi I am using IIS 7.0 with server 2008. We are having an issue where we are logging into our website that is hosted on our intranet, that has us choose the credentials we want to use after a few minutes of already being logged on. It doesn't always happen
and when it does happen you could simply click out of the box and it will not kick you out of the website. We are using windows authentication. If anyone could point me in the direction Id appreciate any help at all, i know its more of a bit annoyance but
the goal is always to have no issues going on.
May 25, 2016 05:04 AM|lextm|LINK
That kind of issues indicates the web server returned an 401 error response to the web browser, but 401 is a big family,
You might hit any of them.
So overall if you want to really resolve this issue, you will have to start by collecting more data. If you don't think you are capable of handling that massive task, you can open a support case via
http://support.microsoft.com and let Microsoft support team assist.
May 25, 2016 11:11 AM|ryguytheITguy|LINK
Hey thank you for the response. Im looking in the logs right now is there any easy way to find the errors? Is it a specific line of words for lack of a better term? And so even those its getting a 40 error no error really shows up on the screen for an error
besides the re prompt. Is that normal for 4.xx errors? Is it the numbers at the end of each line. I have a bunch of 200 then i have something that goes 401 2 5 2059. Is that what I'm looking for?
May 25, 2016 11:39 AM|ryguytheITguy|LINK
Sorry to keep replying to the message but so far it looks like i have three 400 erros wich are 401.2 403.4 and 403.7. Ever seen any of those I'm looking in to them myself and will post if i find the answer
May 26, 2016 06:15 AM|lextm|LINK
Like I commented above, you really need to talk to Microsoft support team to get an action plan. For example, you should recall what time it was that a user experienced this problem. Then you dig into IIS log files to focus just on that time frame and for
that specific user.
It is never an easy task to analyze IIS log files (unless for support professionals), so I don't expect you locate the relevant portion in a short period of time.
Also if this issue happens really frequently, there can be other approaches to collect the data. So make sure you open a support case.