| title | Errors | Microsoft Docs | |||||
|---|---|---|---|---|---|---|
| description | Errors | |||||
| ms.custom | ||||||
| ms.date | 06/14/2018 | |||||
| ms.prod | sql | |||||
| ms.prod_service | database-engine, sql-database, sql-data-warehouse, pdw | |||||
| ms.reviewer | ||||||
| ms.technology | connectivity | |||||
| ms.topic | reference | |||||
| helpviewer_keywords |
|
|||||
| author | pmasl | |||||
| ms.author | pelopes |
[!INCLUDEappliesto-ss-asdb-asdw-pdw-md]
[!INCLUDEDriver_OLEDB_Download]
OLE/COM objects report errors through the HRESULT return code of object member functions. An OLE/COM HRESULT is a bit-packed structure. OLE provides macros that dereference structure members.
OLE/COM specifies the IErrorInfo interface. The interface exposes methods such as GetDescription. This allows clients to extract error details from OLE/COM servers. OLE DB extends IErrorInfo to support the return of multiple error information packets on a single-member function execution.
[!INCLUDEssNoVersion] can return multiple errors. An application can retrieve server errors one at a time by calling IMultipleResults::GetResult combined with ISQLErrorInfo and IErrorRecords.
The OLE DB Driver for SQL Server exposes the OLE DB record-enhanced IErrorInfo, the custom ISQLErrorInfo, and the provider-specific ISQLServerErrorInfo error object interfaces.
For information about tracing errors, see Data Access Tracing. For information about enhancements to error tracing added in [!INCLUDEssSQL11], see Accessing Diagnostic Information in the Extended Events Log.