Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message occurs when you use OLE DB Provider for SQL Server in ADO.NET: "Cannot start more transactions on this session"


This article refers to the following Microsoft .NET Framework Class Library namespaces:

  • System.Data
  • System.Data.OleDb
  • System.Data.SqlClient

↑ Back to the top


Symptoms

When you use Microsoft OLE DB Provider for SQL Server (OLEDBSQL) in ADO.NET, if you try to start more than one transaction in a session, you receive the following error message:

System.Data.OleDb.OleDbException: Cannot start more transactions on this session

↑ Back to the top


Cause

By design, OLE DB Provider for SQL Server does not allow nested transactions.

↑ Back to the top


More Information

Steps to Reproduce the Behavior

  1. Start Microsoft Visual Studio .NET.
  2. Create a Windows Application project in Visual Basic .NET. Form1 is created by default.
  3. Double-click Form1 to open the Code window.
  4. Replace the code in Form1 with the following code:
    Imports System.Data
    Imports System.Data.OleDb
    Imports System.Data.SqlClient

    Public Class Form1
    Inherits System.Windows.Forms.Form

    Dim cn As New OleDb.OleDbConnection()
    Dim cmd As New OleDb.OleDbCommand()
    Dim mycmd As New OleDb.OleDbCommand()

    #Region " Windows Form Designer generated code "

    Public Sub New()
    MyBase.New()

    'This call is required by the Windows Form Designer.
    InitializeComponent()

    'Add any initialization after the InitializeComponent() call

    End Sub

    'Form overrides dispose to clean up the component list.
    Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)
    If disposing Then
    If Not (components Is Nothing) Then
    components.Dispose()
    End If
    End If
    MyBase.Dispose(disposing)
    End Sub

    'Required by the Windows Form Designer
    Private components As System.ComponentModel.Container

    'NOTE: The following procedure is required by the Windows Form Designer
    'It can be modified using the Windows Form Designer.
    'Do not modify it using the code editor.
    <System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()
    '
    'Form1
    '
    Me.AutoScaleBaseSize = New System.Drawing.Size(5, 13)
    Me.ClientSize = New System.Drawing.Size(292, 273)
    Me.Name = "Form1"
    Me.Text = "Form1"

    End Sub

    #End Region

    Private Sub Form1_Load(ByVal sender As System.Object, _
    ByVal e As System.EventArgs) Handles MyBase.Load
    cn.ConnectionString = "Provider=SQLOLEDB;Data Source=YourServer;" & _
    "Initial Catalog=pubs;User ID=YourUserID;Password=YourPassword"
    cn.Open()
    cmd.Connection = cn
    mycmd.Connection = cn
    cmd.CommandText = "Insert into stores (stor_id) values('9876')"
    Dim myTrans As OleDb.OleDbTransaction
    myTrans = cn.BeginTransaction(IsolationLevel.ReadCommitted)

    cmd.Transaction = myTrans

    Try
    cmd.ExecuteNonQuery()

    myTrans.Begin()
    myTrans.Commit()
    Catch ex As Exception
    MessageBox.Show(ex.ToString)
    End Try

    End Sub
    End Class
  5. Modify the connection string as appropriate for your environment.
  6. Run the application. Notice that you receive the error that is listed in the "Symptoms" section.

↑ Back to the top


References

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

306649 PRB: Error When You Implement Nested Transaction with OLE DB Provider for SQL Provider

↑ Back to the top


Keywords: kb, kbsystemdata, kbprb, kbpending, kbvs2003swept, kbaspwpswept, kbado2applies, kbado2sweep, kberrmsg, kbtshoot

↑ Back to the top

Article Info
Article ID : 316872
Revision : 5
Created on : 8/20/2020
Published on : 8/20/2020
Exists online : False
Views : 133