Use ASP.NET Trace to figure out what went wrong

link -> How to: View ASP.NET Trace Information with the Trace Viewer:

I tried this on my local machine and it worked pretty well. Unfortunately I didn't have permissions to enable it on the machine that had the problem.