Determining web page error details

I have a simple form that returns feedback for a given user account.
Works great for me.  Gave it to someone else and it worked fine.  Third person sent over a screen shot of a
Server Error in '/...' application
Runtime error
An application error occurred on the server.  The current error settings...prevent you from viewing...for security reasons...

How can I determine what went wrong in the application?  I have try/catch blocks in the only places that something would throw an exception (or so I thought).  Is there a way to dump these errors to a file so I can review?
LVL 67
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ramkisan JagtapLead DeveloperCommented:
This is a uncaught exception so your try catch will not work here.
So you need to modify your web.config in order to view the error.
Update the CustomErros="Off" as below in web.config:

        <customErrors mode="Off"/>

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sirbountyAuthor Commented:
Ok, that gives me this:

Request timed out.
  Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

 Exception Details: System.Web.HttpException: Request timed out.

Source Error:
 An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Stack Trace:
[HttpException (0x80004005): Request timed out.]

The app runs a shelled powershell script, returning the results.  The built script works fine, so I don't know why the time-out.  Is there a place to adjust that?
sirbountyAuthor Commented:
I got the time out increased in the web.config, but it's still taking too long - the script runs fairly quick... Not sure why it's not returning the data in time.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Ramkisan JagtapLead DeveloperCommented:
Please try debug the application and find where the application is returning that error.
Cant predict anything as there is no reference to code here.
sirbountyAuthor Commented:
Unfortunately it won't be easy to debug... I have vs on my workstation, but missing some of the powershell modules that would allow it to complete.
If I run the generated script on the server, it completes in 4-6 seconds.  Timeout is set to 180 seconds.
So I'm not sure how to proceed to test further.
I can post the code if you'd like, but it's really a basic text box, and a button.  Click the button and the powershell script is generated, launched, and stdout returned to be provided to a label.  That's it.  And it works with 'most' IDs.  This ID has about double the results that are normally returned, but it's not an impossible amount of data.  Maybe 40 lines of results, versus normal 20.  And like I said, the script is producing the output, so the only thing I could think of is maybe the label control has a limit of data that can be returned?
sirbountyAuthor Commented:
Nope, that doesn't seem to be it either - changed label1.text to response.write and it still times out...
sirbountyAuthor Commented:
It doesn't seem to be coming out of this, but I'm not sure what could be preventing the stdout from being received.  It nearly immediately completes when I fire it off outside the web app...
Do Until p.HasExited
sirbountyAuthor Commented:
Increased timeout to 540, same results. :(
sirbountyAuthor Commented:
Is there nothing else that I can do to find out why it's timing out?
sirbountyAuthor Commented:
Weird - I took out the sleep loop and it completed... :\
sirbountyAuthor Commented:
This wasn't the solution, but helped me get there - thanks!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.