Also, everything is fine if I run de application interactively through a
Terminal Server session or through Remote Debuging from the Visual Studio
environment running on my laptop.
The application works fine both interactivle and as a service under a local
account, on a Win2k development server as well as on my XP laptop.
In the cases where the application crashes, it always does it within MFC
function ProcessShellCommand.
The aplication was developed in Visual Studio 6.0, using the MFC AppWizard
(exe).
Has anybody had a similar experience? Why would ProcessShellCommand crash?
and why it works fine in many different scenarios as explained above? Any
ideas?
Thanks
Marcos B.
Marcos B. felt like saying: