Hey-You-1
asked on
Something is wrong with our website which is corrected when IIS is reset and I want to find out what the root problem is.
Something is wrong with our website which is corrected when IIS is reset. I want to find out what the root problem is.
We have a "web portal" (as my boss calls it) website which was created for our company by an outside contractor about 3 years ago. It sits on an EC2 instance we control. This web portal is used by our accountants for moving numbers around.
The problem is that approximately 10% of login attempts are unsuccessful, with correctly entered credentials. I have observed it myself. Any the failed login doesn't behave as one might expect. There's no error which appears on screen. Instead, the login screen simply 'resets' and appears as though no login has yet been attempted.
So I'm investigating, and I find that someone set a recurring task for IIS to reset every hour, indefinitely.
My boss wants a 100% success rate with logins using correct credentials. That's reasonable.
So, I need to determine what is going wrong, and is being temporarily corrected by resetting IIS. And I have no idea where to begin, other than looking at logs, but I'm not even sure what to begin looking at there either.
We have a "web portal" (as my boss calls it) website which was created for our company by an outside contractor about 3 years ago. It sits on an EC2 instance we control. This web portal is used by our accountants for moving numbers around.
The problem is that approximately 10% of login attempts are unsuccessful, with correctly entered credentials. I have observed it myself. Any the failed login doesn't behave as one might expect. There's no error which appears on screen. Instead, the login screen simply 'resets' and appears as though no login has yet been attempted.
So I'm investigating, and I find that someone set a recurring task for IIS to reset every hour, indefinitely.
My boss wants a 100% success rate with logins using correct credentials. That's reasonable.
So, I need to determine what is going wrong, and is being temporarily corrected by resetting IIS. And I have no idea where to begin, other than looking at logs, but I'm not even sure what to begin looking at there either.
Do you know what the logins authenticate against? Active Directory? Some proprietary database?
"...10% of login attempts are unsuccessful..."
Is this all the time? Just before the IIS reset takes place? Just after the IIS reset takes place? Does this symptom ever get better or worse?
"...10% of login attempts are unsuccessful..."
Is this all the time? Just before the IIS reset takes place? Just after the IIS reset takes place? Does this symptom ever get better or worse?
ASKER
@Scott Fell: I adjusted the IIS reset to every 24 hours - i'll be monitoring the w3wp.exe size during that time. Thank you for your suggestions!
@Paul MacDonald: I believe they authenticate against a database in HeidiSQL which I haven't encountered before. The 10% unsuccessful login rate is what I figure is the overall average throughout the day. I keep having users telling me that they "have been trying to get logged in all morning/day without success," and at the same time, others are logged in and getting the numbers moved around.
@Paul MacDonald: I believe they authenticate against a database in HeidiSQL which I haven't encountered before. The 10% unsuccessful login rate is what I figure is the overall average throughout the day. I keep having users telling me that they "have been trying to get logged in all morning/day without success," and at the same time, others are logged in and getting the numbers moved around.
You said, " which is corrected when IIS is reset."
I am not an iis expert, but from my own experience when this has happened I set the domain to be on it's own app pool to start with. Another thing to check on is database queries that continue to run or connections that do not close.
Try and recreate on your own and note the time and that will help you when looking in your log files.
I am not an iis expert, but from my own experience when this has happened I set the domain to be on it's own app pool to start with. Another thing to check on is database queries that continue to run or connections that do not close.
Try and recreate on your own and note the time and that will help you when looking in your log files.
Have you check you IIS App pools?
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers 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.
You can start with removing the scheduled task. My guess that leaves the person logged in indefinitely similar to what EE does when you are logged in. That is a business decision you need to make and update your code used in the portal if you don't want somebody logged in forever (which would be a good idea if this is financial data). However, there are going to be better options to manage log ins then a scheduled task.