Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a .net exe installed in the client machine and it throws an exception..So how to debug and find the exact error..
Please note that
1-this is not remote debugging..
2-I dont have log files to check and the machine is Windows 7..
Please let me know if this is possible?
As per comments:
As I already told I dont have log files to verify and I dont have any stackrace as well..
So anybody else know how to find the exact error..????
Assuming the exe crashing (ie. the exception is unhandled) then if you are not able to install anything on the remote machine you will need to get a dump file from Windows Error Reporting.
For a managed executable you should configure WER to generate a full dump as the minidump will likely not have enough information.
Once you have this dump file on your machine you can analyze it using WinDbg and the SOS extension (assuming you have a matching pdb file for the exe that generated the dump file)