"Failed to Enlist in DTC" ... intermittent error , when testing my app


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 2 of 2

Thread: "Failed to Enlist in DTC" ... intermittent error , when testing my app

  1. #1
    John Harkin Guest

    "Failed to Enlist in DTC" ... intermittent error , when testing my app


    Hi All,
    Using MTS , SQL Server 7.0 , nt 4.0 with latest SP.
    When testing my app i intermittently get the following error in the event
    log :


    The description for Event ID ( 0 ) in Source ( COM Contexts ) could not be
    found. It contains the following insertion string(s): Failed to enlist in
    DTC: SQL state 01000, native error 85, error message [Microsoft][ODBC SQL
    Server Driver][SQL Server] .


    The components are on the same machine as the SQL Server 7.0 database

    I have read the following the msdn
    If you only see the "failed to enlist" error intermittently, then using Named
    Pipes rather than TCP/IP may be the cause of the problem. Using Named Pipes
    can result in intermittent "Failed to Enlist" errors.
    Microsoft strongly recommends that you configure the SQL Server to use TCP/IP
    rather than Named Pipes. Using Named Pipes can result in Intermittent "Failed
    to Enlist" errors.

    However also on the MSDN it mentions :
    "When the application is on the same computer as SQL Server, Windows Interprocess
    Communication (IPC) components, such as local named pipes or shared memory,
    are used. "


    I have configured my ODBC connection to use tcp/ip as recommended but i get
    these intermittent errors.


    Could it be due to fact as that as sql server is on same machine as conponents
    then tcp/ip is not be used and hence getting intermittent "failed to enlist"
    problem?
    If so any way around it?


    Share on Google+

  2. #2
    George Guest

    Re: "Failed to Enlist in DTC" ... intermittent error , when testing my app


    Poor John,

    I got this error too. The only things I can think of :
    1) reduce the transaction to smaller pieces;
    2) increase the timeout time in MTS;
    3) blame Microsoft.

    George



    "John Harkin" <john.harkin@singularity.co.uk> wrote:
    >
    >Hi All,
    >Using MTS , SQL Server 7.0 , nt 4.0 with latest SP.
    >When testing my app i intermittently get the following error in the event
    >log :
    >
    >
    >The description for Event ID ( 0 ) in Source ( COM Contexts ) could not

    be
    >found. It contains the following insertion string(s): Failed to enlist in
    >DTC: SQL state 01000, native error 85, error message [Microsoft][ODBC SQL
    >Server Driver][SQL Server] .
    >
    >
    >The components are on the same machine as the SQL Server 7.0 database
    >
    >I have read the following the msdn
    >If you only see the "failed to enlist" error intermittently, then using

    Named
    >Pipes rather than TCP/IP may be the cause of the problem. Using Named Pipes
    >can result in intermittent "Failed to Enlist" errors.
    >Microsoft strongly recommends that you configure the SQL Server to use TCP/IP
    >rather than Named Pipes. Using Named Pipes can result in Intermittent "Failed
    >to Enlist" errors.
    >
    >However also on the MSDN it mentions :
    >"When the application is on the same computer as SQL Server, Windows Interprocess
    >Communication (IPC) components, such as local named pipes or shared memory,
    >are used. "
    >
    >
    >I have configured my ODBC connection to use tcp/ip as recommended but i

    get
    >these intermittent errors.
    >
    >
    >Could it be due to fact as that as sql server is on same machine as conponents
    >then tcp/ip is not be used and hence getting intermittent "failed to enlist"
    >problem?
    >If so any way around it?
    >
    >


    Share on Google+

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center