Error 7391 New transaction cannot enlist in the specified transaction coordinator

  • I am struggling to get a distributed transaction accross 2 servers working: I cannot even get simple test code to work.....

    BOX_A is defined as a linked server on BOX_B. BOX_B is defined as a linked server on BOX_A.

    BOX_A Win2003 Server SP1 with SQL2K SP3a

    BOX_B Win2000 Server SP4 with SQL2K SP3a

    Network DTC Access is enabled on BOX_A (under add programs)

    MSDTC is running on both servers.

    The servers are on different IP subnets. The servers are members of different domains.

    I have configured the Linked Servers to use a specified sql login

    I have tried with and without Aliases.

    This works ok and returns a result (proves the linked servers are correctly configured)

    SET xact_abort ON

    SELECT * FROM [BOX_A].[RES].[dbo].tblversion

    GO

    This does not work:

    SET xact_abort ON

    BEGIN DISTRIBUTED TRANSACTION

    SELECT * FROM [BOX_A].[RES].[dbo].tblversion

    COMMIT

    GO

    The error message is:

    Server: Msg 7391, Level 16, State 1, Line 3

    The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.

    [OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]

    OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].

    I have the identical behaviour from BOX_A to BOX_B

    I can get 2 win2kSP4 machines with SQL2KSP3a to do this fine. They are on the same subnet and domain.

    Can anyone help please....

    Andy


    AndyM

  • This is happening because Win 2003 has a different MS DTC setup. By default MS DTC is not configured for network access on Win 2003 installations.

    I have already had this problem.

    To Solve this take a look at Ms Article: 329332.

    []´s

    Anderson Ferreira


    Anderson Ferreira

  • Start with the article for sure. If this is a cluster you will have to start DTC on the windows 2003 server before SQL comes online this is a known bug and will be fixed in a future patch (if it hasn't already I haven't checked in a couple of weeks)

    Wes

  • Hi!

    My english isn't very good, but i hope can help someone that had same problem that i had.

    In the Component Service, MSDTC's tab You must use the

    "No Authentication Required" transaction mode where one or more

    of the following conditions are true:

    - The network access is between computers that are running Microsoft

    Windows 2000.

    - The network access is between two domains that do not have a mutual

    trust configured.

    - The network access is between computers that are members of a

    workgroup.

     

    Tank's!

    Carlos Magno!

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply