Mrdenny   46795 pts.  |   Oct 7 2009  7:33AM GMT

The event viewer looking at the application log, and any log files which the application has created.

Carlosdl   29820 pts.  |   Oct 7 2009  1:39PM GMT

Yes, logs are usually the best option.

In a couple of special situations, we have needed to install a keylogger on the client computer, to be able to understand what was causing the error.

JennyMack   3330 pts.  |   Oct 7 2009  2:17PM GMT

Carlosdl,

Interesting. If you don’t mind my asking, which keylogger do you use?

Carlosdl   29820 pts.  |   Oct 7 2009  9:44PM GMT

We use and old version of Ardamax.

KevinBeaver   7610 pts.  |   Oct 9 2009  12:27AM GMT

Most of the people I know use Event Viewer or nothing at all (they just reboot!).

Coop   45 pts.  |   Oct 9 2009  3:16PM GMT

Interesting question. Everyone seems to assume you are asking how to diagnose a system crash. But maybe you want to know how best to keep track of your systems, keeping a record of errors and such?

You might want to try these programs

 <a href="http://spiceworks.com" title="http://spiceworks.
" target="_blank">spiceworks.com</a> - this is a free network manager. You can view your network, all the computers, and keep notes on them. You can even track support calls, etc. Its a pretty good solution for the price.

 <a href="http://logmein.com" title="http://logmein.
" target="_blank">logmein.com</a> - if you can afford to pay for the PRO version, this program gives you tons of info on your workstations etc. I mostly use the free version to access my users in the field, and to support other companies. but I do use the pro version on key systems! I love it.

 <a href="http://splunk.com" title="http://splunk.
" target="_blank">splunk.com</a> - if your interested in tracking log files, this may do the trick. I played with it a little, but then set it aside and not had time to get back to it.

Hope these help