What are the best practices /steps to investigate if an ASP.net web application hosted on IIS with SQL server is not responding.
from programmer prospective i do start with the exact error message details.
I would like to know for an application available in production and if i have to start troubleshooting from production.
What if there is no specific error message (a blank page / delay in loading the page or may be while submitting or requesting for a specific action on a page).
Starting from IIS to SQL and then debug the same in VS if the issue is due to code,
what are the basic things i should be checking in IIS as a programmer ?
so that i can check if its SQL(including sql sp and trigger) via profiler or the source code (the c# code for business logic ) via VS.
Its been asked to me multiple times in interviews, and i always felt confused myself on this.
Guest UserPosted Jul 12, 2014, 9:50 PM
Please connect with me on twitter @sumitjolly and I'll follow you also!
Ashish SrivastavaPosted Jul 8, 2014, 2:42 PM
Guest UserPosted Jul 8, 2014, 12:43 AM
- Logging: look for logs generated at application, generally stored at App_Data folder
- If you've production credentials then point your local code web.config with production database
- Then change mode to DEBUG and you can debug your application using F5 (ensure debug=true in web.config)
twitter @sumitjolly