Re: My MFC VC++ app is crashing within ProcessShellCommand

Thanks for your response Joseph. Here are some clarifying details:

The application was developed as a regular MFC Windows application, but it
runs in production as a service using srvany.exe. The application just
displays one main window which shows the time when it connected to the
database.

Unfortunately I can't give you a lot of details about what the application
is doing before it crashes because I don't have Visual Studio installed in
the production server in order to run the application in the debugger. If I
do a remote debugging session from within VS in my laptop everything works
fine as I said in the original post. All I know (by writing some trace to a
text file) is that the last line executed before the crash is the call to
ProcessShellCommand.

Here is the portion of code that includes that call. I think most of this
code is generated by the Wizard:
//===================================================

BOOL CTT32CommServApp::InitInstance()
{
    AfxEnableControlContainer();

    // Standard initialization
    // If you are not using these features and wish to reduce the size
    // of your final executable, you should remove from the following
    // the specific initialization routines you do not need.

#ifdef _AFXDLL
    Enable3dControls(); // Call this when using MFC in a shared DLL
#else
    Enable3dControlsStatic(); // Call this when linking to MFC statically
#endif

    // Change the registry key under which our settings are stored.
    // You should modify this string to be something appropriate
    // such as the name of your company or organization.
    SetRegistryKey(_T("Local AppWizard-Generated Applications"));

    LoadStdProfileSettings(0); // Load standard INI file options (including MRU)

    // Register the application's document templates. Document templates
    // serve as the connection between documents, frame windows and views.

    CSingleDocTemplate* pDocTemplate;
    pDocTemplate = new CSingleDocTemplate(
        IDR_MAINFRAME,
        RUNTIME_CLASS(CTT32CommServDoc),
        RUNTIME_CLASS(CMainFrame), // main SDI frame window
        RUNTIME_CLASS(CTT32CommServView));
    AddDocTemplate(pDocTemplate);

    // Parse command line for standard shell commands, DDE, file open
    CCommandLineInfo cmdInfo;
    ParseCommandLine(cmdInfo);

    // If we didn't get the username from the command line, exit.
    if(username == NULL)
        return FALSE;

    // Dispatch commands specified on the command line
// if (cmdInfo.m_nShellCommand == CCommandLineInfo::FileNew)
// cmdInfo.m_nShellCommand = CCommandLineInfo::FileNothing;

    if (!ProcessShellCommand(cmdInfo)) // Don't open the document yet.
        return FALSE;

    // Kick off the thread that will connect to the database, open the document
and monitor our connection to the database.
    shutdownEvent = new CEvent(FALSE, TRUE, "Shutdown");

    dbMonitorThread = AfxBeginThread(MonitorDatabaseConnection, (LPVOID) this,
THREAD_PRIORITY_BELOW_NORMAL);

    // The one and only window has been initialized, so show and update it.
    m_pMainWnd->ShowWindow(SW_SHOWMAXIMIZED);
    m_pMainWnd->UpdateWindow();

    return TRUE;
}

//===================================================

What makes it more mysterious is the fact that it works fine when I do
remote debugger and when I run it interactively through Terminal Service.
However if I run it interactively by looging on to the serer at the console,
it crashes. Again like I said, the application runs fine both interactively
and as a service on a development server.

I hope this helps. Please let me know if you want some more details or
something spoecific that might give you a better idea.

Thanks again.

Marcos B.

"Joseph M. Newcomer" wrote: