'exception: _com_error...' debug message
Posted: Thu Mar 07, 2019 10:31 pm
From a Windows 10 (64-bit) machine (within the Visual Studio 2013 IDE debugging session) the snippet of code listed below produces a _com_error exception message in the output window as follows:
'First-chance exception at 0x768318A2 in inwin.exe: Microsoft C++ exception: _com_error at memory location 0x0019F304.'
Before this exception message is shown, a dialog stating: "This action cannot be completed because the other program is busy. Choose 'Switch To' to activate the busy program and correct the problem." appears.
The error string created in the catch() section produces the following:
"ERROR: PDF-XChange Printer Driver caused exception! Code = 0x80080005"
try
{
PXC::IPXCControlExPtr m_pFactory = PXC::IPXCControlExPtr(__uuidof(PXC::CPXCControlEx));
.
.
.
}
catch (_com_error& e)
{
.
.
.
CString s;
s.Format("ERROR: PDF-XChange Printer Driver caused prgram exception! Code = 0x%08lx\n", e.Error());
}
Note that on the same Windows 10 machine, using identical source to build same EXE (release build) with Visual Studio 2008 tool the program closes automatically when attempting to create a PDF file. This same EXE on a Windows 7 (32-bit) machine DOES NOT crash!
I need help is resolving what why this Windows 10 machine specifically is producing the com_error.
'First-chance exception at 0x768318A2 in inwin.exe: Microsoft C++ exception: _com_error at memory location 0x0019F304.'
Before this exception message is shown, a dialog stating: "This action cannot be completed because the other program is busy. Choose 'Switch To' to activate the busy program and correct the problem." appears.
The error string created in the catch() section produces the following:
"ERROR: PDF-XChange Printer Driver caused exception! Code = 0x80080005"
try
{
PXC::IPXCControlExPtr m_pFactory = PXC::IPXCControlExPtr(__uuidof(PXC::CPXCControlEx));
.
.
.
}
catch (_com_error& e)
{
.
.
.
CString s;
s.Format("ERROR: PDF-XChange Printer Driver caused prgram exception! Code = 0x%08lx\n", e.Error());
}
Note that on the same Windows 10 machine, using identical source to build same EXE (release build) with Visual Studio 2008 tool the program closes automatically when attempting to create a PDF file. This same EXE on a Windows 7 (32-bit) machine DOES NOT crash!
I need help is resolving what why this Windows 10 machine specifically is producing the com_error.