By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,937 Members | 1,532 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,937 IT Pros & Developers. It's quick & easy.

Error Handling Question

P: n/a
I have an application running on Windows Server 2003 that was installed
using an MSI package. Every once in a while (maybe once a week), I'll see,
by looking at the database that the app is not reporting as it should.

When I go back and look at the machine, the app is still running, but
there's a dialog open telling me about enabling JIT debugging. The problem
is that it doesn't really detail what the error is at all, it just tells me
about the loaded assemblies.

This is production critical information and it causes a lot of problems if
the app is down. So I guess my question is - is there a way to handle errors
at the application level? Or perhaps someone could explain to me the best
way to deal with this situation. I realized I could enable JIT debugging but
if there's any other way I'd love to hear about it.

Thanks a lot,

Jason
Nov 20 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Cor
Hi Jason,
This is production critical information and it causes a lot of problems if
the app is down. So I guess my question is - is there a way to handle errors at the application level? Or perhaps someone could explain to me the best
way to deal with this situation. I realized I could enable JIT debugging but if there's any other way I'd love to hear about it.

There are a lot of posibilities for error handling in the vb.net language,
look for it to the
Try, end try, catch and finally statements.

I hope this brings you on the route

Cor
Nov 20 '05 #2

P: n/a
* "Jason MacKenzie" <jm***************@formet.com> scripsit:
I have an application running on Windows Server 2003 that was installed
using an MSI package. Every once in a while (maybe once a week), I'll see,
by looking at the database that the app is not reporting as it should.

When I go back and look at the machine, the app is still running, but
there's a dialog open telling me about enabling JIT debugging. The problem
is that it doesn't really detail what the error is at all, it just tells me
about the loaded assemblies.


What does it tell you?

--
Herfried K. Wagner
MVP VB Classic, VB.NET
<http://www.mvps.org/dotnet>
Nov 20 '05 #3

P: n/a
Perhaps I wasn't clear in my question. I use try..catch extensively
throughout the application. Something though is getting past that. What I
want to know is, is there a way an the application level of trapping any
errors that get through (or any other methodology, for that matter)? The
dialog I see on the screen doesn't really tell me anything.
"Cor" <no*@non.com> wrote in message
news:eJ**************@TK2MSFTNGP09.phx.gbl...
Hi Jason,
This is production critical information and it causes a lot of problems if the app is down. So I guess my question is - is there a way to handle

errors
at the application level? Or perhaps someone could explain to me the best way to deal with this situation. I realized I could enable JIT debugging

but
if there's any other way I'd love to hear about it.

There are a lot of posibilities for error handling in the vb.net language,
look for it to the
Try, end try, catch and finally statements.

I hope this brings you on the route

Cor

Nov 20 '05 #4

P: n/a
It tells me about the loaded assemblies and then it tells me the process to
enable JIT debugging.

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:bn*************@ID-208219.news.uni-berlin.de...
* "Jason MacKenzie" <jm***************@formet.com> scripsit:
I have an application running on Windows Server 2003 that was installed
using an MSI package. Every once in a while (maybe once a week), I'll see, by looking at the database that the app is not reporting as it should.

When I go back and look at the machine, the app is still running, but
there's a dialog open telling me about enabling JIT debugging. The problem is that it doesn't really detail what the error is at all, it just tells me about the loaded assemblies.


What does it tell you?

--
Herfried K. Wagner
MVP VB Classic, VB.NET
<http://www.mvps.org/dotnet>

Nov 20 '05 #5

P: n/a
Cor
Hi Jason,
It does if you don't catch the execption.
by catch ex as exception (for the kind of exception, this is the standard
one, you have to look for the methods to see all exception possibilities)
Then you can say
messagebox.show(ex)

You can catch more exceptions, but watch to set this general one as the
last.

I don't know if this anwers your question ?

Cor

Nov 20 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.