Occassional "New transaction cannot enlist in the specified ... DT

[Neal Walters]

We are doing a stree test of about 200 records. A Biztalk orch. starts by
based on an SQL receive port that polls this databsae. We run an SQL update
command to set the status flag on all 200 records, and away they go.

All 200 orchestrations run, but at the end of the process, we find that our
SQL receive port is disabled

The receive location "SQL://xxx/yyy" is shutting down. Details:"The error
threshold has been exceeded. The receive location is shutting down.".

Looking back in the log find this 4 warning messages that say this (but no
error messages):

The adapter "SQL" raised an error message. Details "New transaction cannot
enlist in the specified transaction coordinator. ".

Are there are any large volume or throughput issues with DTC?

Neal Walters
http://Biztalk-Training.com

[Marian Drumea]

Hi Neal,

I had a similar problem with one of my clients. I guess you can see
only four warning messages is because of the error threshold set on
adapter's properties. The default is 5. I guess you find that none of
the actual orchestration instances completes successfully. Let me know
if otherwise. What is the status of the service instances in HAT?

The best thing you can do now is to use a great diagnostic tool
(DTCTester Tool) you can find here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;293799

The instructions are clear and the output should put you on the right
track. For instance, DTC needs certain ports open in order to operate
properly. If the ports are OK, another reason can be the fact that the
SQL Server is on a distinct machine that cannot "see" the calling
machine by name (distinct domains maybe). If this, you could add the
mapping between the machine name and IP to lmhosts if I remember
correctly. Regardless, run the tool and see what you get.

Good luck!

Marian

[Younes Amar]

Hi Neal,

If my assumption is right, the problem descibed below is more a general
configuration issue than a BizTalk problem.

If the probelm occurs under Windows 2003 SP1 you might have to adjust the
MSDTC settings under COM+ to allow the communication to the
remote DTC.

How to adjust the MSDTC settings:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/deploying/htm/ebiz_depl_assemblies_tfrh.asp?frame=true

MSDTC Changes in Windows 2003 SP1:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cossdk/html/2627a956-60b3-4d26-bc04-e0676ec97786.asp

Regards,

Younes
"Marian Drumea" <mdr...@gmail.com> wrote in message
news:1131745295.7...@g43g2000cwa.googlegroups.com...