How To Obtain Underlying Provider Errors by Using ADO.NET in Visual Basic .NET

This article was previously published under Q308043
This article has been archived. It is offered "as is" and will no longer be updated.
For a Microsoft Visual C# .NET version of this article, see 308650.
For a Microsoft Visual C++ version of this article, see 308651.
For a Microsoft Visual Basic 6.0 version of this article, see 167957.

This article refers to the following Microsoft .NET Framework Class Library namespace:
  • System.Data.OleDb


Managed providers can raise several exceptions. To obtain more detailed information about the cause, you need access to provider-specific error information. This article dicusses how to obtain the underlying provider errors when using ADO.NET in Visual Basic .NET.

back to the top


The following list outlines the recommended hardware, software, network infrastructure, and service packs that you need:
  • Microsoft .NET Framework
  • Microsoft Visual Basic .NET
This article assumes that you are familiar with the following topics:
  • Exceptions
  • Microsoft OLE DB
  • Error handling
back to the top

Steps to Obtain Underlying Provider Errors

To obtain more detailed information about the cause of an exception, wrap your code in a try-catch block, catch the exception, and process the Errors collection from the OleDbException class.
  1. Start Microsoft Visual Studio .NET, and then create a new Windows Application project in Visual Basic .NET. Form1 is created by default.
  2. Open Form1.vb in code, copy the following code, and paste the code at the beginning of the form:
    Imports System.Data.OleDb					
  3. Copy the following code into the Form1 Load event:
    Dim ex As OleDbExceptionDim cn As OleDbConnection = New OleDbConnection("Provider=SQLOLEDB.1;Data Source=MyWrongServerName")Try    cn.Open()Catch ex    Dim i As Integer    For i = 0 To ex.Errors.Count - 1        MessageBox.Show("Index #" + i.ToString() + ControlChars.Cr _           + "Message: " + ex.Errors(i).Message + ControlChars.Cr _           + "Native: " + ex.Errors(i).NativeError.ToString() + ControlChars.Cr _           + "Source: " + ex.Errors(i).Source + ControlChars.Cr _           + "SQL: " + ex.Errors(i).SQLState + ControlChars.Cr)    Next iEnd Try					
  4. Run the application. A message box should appear after 10 to 15 seconds.
back to the top


If you have a server named "MyWrongServerName," you may not receive an error.

back to the top
For more information on .NET managed providers, refer to the following MSDN Web site: back to the top

Article ID: 308043 - Last Review: 02/27/2014 21:10:08 - Revision: 2.3

Microsoft ADO.NET (included with the .NET Framework), Microsoft ADO.NET 1.1, Microsoft Visual Basic .NET 2002 Standard Edition, Microsoft Visual Basic .NET 2003 Standard Edition

  • kbnosurvey kbarchive kbhowtomaster kbsystemdata KB308043