"New transaction cannot enlist in the specified transaction coordinator" Error When Using COM+ on Win 2003

Posted on 2007-10-18
Last Modified: 2013-12-04
I'm getting an error when running some simple VB6 code that accesses a COM+ application which attempts to connect to SQL 2000.   The error is...

"New transaction cannot enlist in the specified transaction coordinator."

The error occurs on the ADODB.Connection open statement.

In the event log, I get the following:

Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event Id: 529
User: NT Authority\System

Logon Failure:  
   Reason:  Unknown user name or password
   UserName:  xxxxxx$

where xxxxx is the name of the sql server to which I'm trying to connect.

The simple test application is VB6 and COM+.  The COM+ piece was written in version 1.0 and loaded in COM+ 2.0 under Win 2003.  The application is running under Win 2003 std SP2, NTLMV2 only.

I'm using MS DTC, DCOM to DCOM.  DTC service is turned on for both servers. The target server is a Win 2003 server with SQL 2000 sp3a.

This works fine on Windows 2000.

Can you please offer any advise?

Question by:reed1989a
    LVL 17

    Accepted Solution

    You need to set your DTC on the Win2003 machine to allow no authentication.

    Author Comment

    Thanks for the suggestion.  The current requirement that I have is to use authentication.   That said, are there other configuration settings you can recommend for COM+ or DTC?
    LVL 17

    Expert Comment

    The solution I posted is what Microsoft will tell you on their website.  We have a requirement to use authentication too but according to Microsoft it can't be done between a 2000 and a 2003 server so we have to use their workaround and document it.

    I don't know of any other config that will get around this.

    Author Comment

    Thanks for the posting.  I have a solution.  Sorry I wasn't clearer about the two servers being Windows 2003.  

    I fixed the problem by adding a local security policy setting of LAN Manager Authentication Level, with local setting "Send NTLMv2 Response Only\refuse LM & NTLM".   This was done on the target server. This resolved the error.


    Author Comment

    Thanks for the help.  Your advice was factual and helpful, but not quite what was needed to solve the problem.  I'm giving you the points anyway because I appreciate your time and effort in assisting me to find the full solution.

    Featured Post

    Free Trending Threat Insights Every Day

    Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

    Join & Write a Comment

    Recently, I read that Microsoft has analysed statistics for their security intelligence report. It revealed: still, the clear majority of windows users do their daily work as administrator. An administrative account is a burden, security-wise. My ar…
    International Data Corporation (IDC) prognosticates that before the current the year gets over disbursing on IT framework products to be sent in cloud environs will be $37.1B.
    This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
    Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.

    729 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    16 Experts available now in Live!

    Get 1:1 Help Now