How do I troubleshoot live application as users unable to login to system.

Question

0.00/5 (No votes)

See more:

Application is hosted successfully. But users are complaining that they are unable make login into system.
Application Pool is did not stopped.
SQL services also did not stopped.

What I have tried:

Checked whether application pool is working or not at IIS.
Checked SQL services also checked at IIS.

Posted 29-Jul-21 7:12am

abhimestry

Updated 29-Jul-21 8:06am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2021-07-29T08:06:00

Since it's a live system, you can't really use a debugger - so you will have to fall back on older, more long winded debugger techniques.

Start by "peppering" the appropriate code with logging statements: to a file, or a DB, or whatever is available. The idea is to store info on what is happening so that after the problem has occurred you can look at the log, and start working out where the problem is happening.
You then refine the logging to add more focussed info, and repeat until you have an idea what is wrong. then you fix it, and try again - with the logging still active.
When it's fixed and working, disable the logging and return to normal.

Sorry, but its a long process, and we can't help you at all!