Application Error only on some computers
-
I have Dell with Windows 2000; the application is a MFC EXE developed using Visual C++ 6.0 enterprise. After applying some modifications to the application, some of my client computers are receiving "Application Error" message. But this does not appeariing in the development computer. The client computers and the developer computer have the same model and RAM size. I am very frustrated. The "Application Error" is very difficult to trouble shoot. Eilzabeth
-
I have Dell with Windows 2000; the application is a MFC EXE developed using Visual C++ 6.0 enterprise. After applying some modifications to the application, some of my client computers are receiving "Application Error" message. But this does not appeariing in the development computer. The client computers and the developer computer have the same model and RAM size. I am very frustrated. The "Application Error" is very difficult to trouble shoot. Eilzabeth
This sounds like a case for .... CrashFinder[^] Article here[^].
-
I have Dell with Windows 2000; the application is a MFC EXE developed using Visual C++ 6.0 enterprise. After applying some modifications to the application, some of my client computers are receiving "Application Error" message. But this does not appeariing in the development computer. The client computers and the developer computer have the same model and RAM size. I am very frustrated. The "Application Error" is very difficult to trouble shoot. Eilzabeth
Let drwatson write the log and then you can use it to find your problem. C:\Documents and Settings\All Users\Documents\DrWatson\drwtsn32.log. Goto the last crash, and it will tell you the call stack around the crash. You will see fault in the margin for the line on which it crashed. Hopefully you will have enough information to trace it back to a line in your source. If not, build your release with debug information. Then let it crash, you should now see what function caused the crash and in what windows function. You might want to do this off the bat because drwatson is usually hard to read.
-
This sounds like a case for .... CrashFinder[^] Article here[^].
I downloaded and installed CrashFinder with the CLW file dated 5/6/2002. I received compilation errors: Compiling... CrashFinderDoc.cpp C:\download\CrashFinder\CrashFinderDoc.cpp(1107) : error C2065: 'SymDia' : undeclared identifier C:\download\CrashFinder\CrashFinderDoc.cpp(1107) : error C2051: case expression not constant Error executing cl.exe. Do I have the good version? Eilzabeth
-
Let drwatson write the log and then you can use it to find your problem. C:\Documents and Settings\All Users\Documents\DrWatson\drwtsn32.log. Goto the last crash, and it will tell you the call stack around the crash. You will see fault in the margin for the line on which it crashed. Hopefully you will have enough information to trace it back to a line in your source. If not, build your release with debug information. Then let it crash, you should now see what function caused the crash and in what windows function. You might want to do this off the bat because drwatson is usually hard to read.
I went to the folder and found drwtsn32.log. But it was created in 2001. Do I have to turn it on some how? I also modified the project setting to include the debug information. Hope it will help when my client comes back from vacation. Eilzabeth
-
I downloaded and installed CrashFinder with the CLW file dated 5/6/2002. I received compilation errors: Compiling... CrashFinderDoc.cpp C:\download\CrashFinder\CrashFinderDoc.cpp(1107) : error C2065: 'SymDia' : undeclared identifier C:\download\CrashFinder\CrashFinderDoc.cpp(1107) : error C2051: case expression not constant Error executing cl.exe. Do I have the good version? Eilzabeth
That's a newer version. I think it must use an imagehelp.dll installed with .Net or something. Try the older version available via the link in the original article.
-
That's a newer version. I think it must use an imagehelp.dll installed with .Net or something. Try the older version available via the link in the original article.
The problem is solved. The problem was in the Oracle ODBC driver. The client has an older version of the driver. After I upgraded the driver to version 9. The error went away. The problem was from one of the CLOB fields. I think some data is "bad" in that field because other CLOB fields do not cause problems. Thank you all very much for help. -Elizabeth Eilzabeth
-
I went to the folder and found drwtsn32.log. But it was created in 2001. Do I have to turn it on some how? I also modified the project setting to include the debug information. Hope it will help when my client comes back from vacation. Eilzabeth
Problem solved. Please see my other reply. Thank you all. -Elizabeth Eilzabeth