"Failed to Enlist in DTC" ... intermittent error , when testing my app
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
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"
If so any way around it?
-- Android Development Center
-- Cloud Development Project Center
-- HTML5 Development Center
-- Windows Mobile Development Center