How do you Troubleshoot ASP.NET problems?

I’d love to hear how people go about digging into various problems. I have heard of people using logging or tracing like log4net to allow some tracing, but what about other problems which that can’t help with? So here are the topics I’d like to hear from you about and how you handle them. Feel free to add others if you’d like:

High Memory
Slow performance
Deadlock
Loss of session

I look forward to hearing how you go about tracking these down. And I’d really like to hear about these problems in a production environment but development works as well.

Published 07 July 08 02:09 by Tom

Filed under: ASP.NET, Debugging, .NET

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# DotNetKicks.com said on July 7, 2008 2:10 PM:

You've been kicked (a good thing) - Trackback from DotNetKicks.com

# JV said on July 8, 2008 5:07 AM:

* Slow performance

> The stopwatch class in System.Diagnostics (If I'm correct) is great for timing performance, especially in combination with log4net it works like a charm.

# Ramesh said on July 8, 2008 11:46 AM:

For Deadlock - With the help of DBA (Since i dont have access to prod to get the blocking statement), i got the query which caused the blocking, i dig down my application and found that improper transaction handling cause this issue.

# radhai said on July 12, 2008 5:05 AM:

The header file path name.mdf is not valid db file header,

the file size property is in correct.

An attampt to attach an auto named db for file path is failed.A db with the same name exists,or specified file cannot be opened ,or it is located on UNC share

# Tom said on July 14, 2008 1:09 PM:

Radhai,

That isn't really what I was looking for on this post, this is about how you go about troubleshooting things, not to list a problem. Check if the file exists and you have permission to write to the folder. That is usually the problem. You can run filemon to check for that.

Name (required)
Your URL (optional)
Comments (required)

Enter Code Here: Required
Remember Me?

Search

This Blog

Home
Email

All my posts are provided "AS IS" with no warranties, and confer no rights. All the expressions expressed herein are entirely my own and not necessarily those of Microsoft. In addition, thoughts and opinions often change. Because a weblog is intended to provide a semi-permanent point-in-time snapshot, you should not consider out of date posts to reflect current thoughts and opinions.

Your country's flag: