FIX: Access Violation in MSDAER.DLL with _com_error Exceptions

Article translations Article translations
Article ID: 173645 - View products that this article applies to.
This article was previously published under Q173645
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


When using the compiler #import feature, ADO, the OLE DB 1.1 ODBC Provider, and trapping _com_error exceptions, an access violation occurs in MSDAER.DLL when closing an application.


A method created with #import can throw a _com_error exception. When it throws the exception, Release() is not called on the IErrorInfo pointer which is returned from GetErrorInfo(). This leaves the internal error object in the OLEDB ODBC Provider stranded which causes the access violation to occur as the application shuts down.


Create a macro which can be used to Release() the IErrorInfo interface at the end of the "catch" block. For example:
   #define BUGFIX_RELEASE_IERRORINFO(error) \ 
           IErrorInfo * pErr = error.ErrorInfo();  \ 
           pErr->Release();                        \ 
Here is an example of how you would use it:
     //.... call a #import generated method
     if ( m_connection == NULL )   {
      if(S_OK == m_connection.CreateInstance("ADODB.Connection.1", NULL,
         m_connection->Open(varDataSource, varUserId, varPwd);
   catch(_com_error & err)
     // Error handling code...
     ::MessageBox(NULL, (LPCSTR)err.Description(), _T("ADO Error"), MB_OK);



Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 3 and Visual C++ version 6.0.

For more information, please see the following article in the Microsoft Knowledge Base:
170365 INFO: Visual Studio 97 Service Packs - What, Where, and Why


Article ID: 173645 - Last Review: November 1, 2013 - Revision: 2.0
Applies to
  • Microsoft Visual C++ 5.0 Enterprise Edition
kbnosurvey kbarchive kbbug kbvc600fix kbvs97sp2fix KB173645

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from