Program Error: *.exe has generated errors ... - Win 2K on target machine

  • Thread starter Thread starter florianhaag
  • Start date Start date
F

florianhaag

Hi,
I've written an app on Win XP with Delphi 7. I copied the exe file to
a directory on a server where it's available to all network users (all
using Windows 2000). Most users (at least 16) can run the program
without problems, however 4 users get the following message when they
double-click the exe file in Explorer:
"Program Error: PatAdmin.exe has generated errors and will be closed
by Windows. You will need to restart the program.
An error log is being created."

This error occurs only under certain users, other users (with exactly
the same rights, read, write and run) can run the same exe file (not a
copy, it's really the same file) at the same pc. This error doesn't
seem to be caused by the exe file, so is it a Windows error??

The app doesn't use any database stuff, no DLLs or ActiveX libraries,
no special low-level stuff and it doesn't access the registry.
The only thing outside of the exe file that is used by my application
is some files in a subdirectory (I get that on program startup via
ExtractFilePath(ParamStr(0)) ), but even if that subdirectory wasn't
accessible, I don't see how this could result in the error described
above as the app should just show up with a blank string grid then ...

Any clues how to fix that problem?

Thanks in advance
-- Florian Haag
 
Get a Dr. Watson log from the machines on which the app crashes. This will
tell you what thread caused the problem, the instructions around the
exception, and the call stack. Then read up on debugging using this log.

Otherwise, you can use the ole' trial and error method - execute reduced
functionality applications on these machines, repeat until you've isolated
which function/operation causes the exception. Debug from there.


{L}
 
LiquidJ said:
Otherwise, you can use the ole' trial and error method - execute reduced
functionality applications on these machines, repeat until you've isolated
which function/operation causes the exception. Debug from there.
Click to expand...

Hi,
found it - the users that got error msgs didn't have a default printer set.

Regards,
-- Florian Haag
 
Back
Top