I am using 2005's DTS Beta 2 and am running into the error below when I
execute my package:

Error : AcquireConnection call to the connection manager
<dbserver>.<db> failed with error code 0xC0202009.

The odd thing is that I do NOT get the error if I run my package in
Transaction "Supported". I only get this error in Transaction
"Required". I do want to include my package execution in a transaction
though.

Does anyone have any idea? Might it be a DTS problem?

Thanks,
Kay
kit_mx1 (AT) hotmail (DOT) com

This is not really the correct group for this and you should ideally
come up on the Beta NGs but

Does it take a long time?
Are you getting deadlocks?
What connection managers are you using?



"Kay" <kit_mx1 (AT) hotmail (DOT) com> wrote

In message <1116633749.540161.248080 (AT) g47g2000cwa (DOT) googlegroups.com>, Kay
<kit_mx1 (AT) hotmail (DOT) com> writes
Check MS DTC is working correctly between source and destination, and
the machine running package.

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

*** Sent via Developersdex http://www.developersdex.com ***

Thanks.

Does it take a long time?
No, it fails immediately.

Are you getting deadlocks?
No. I don't get an error message stating that it is deadlocked.

What connection managers are you using?
I am using a Microsoft OLE DB Provider for Oracle to Microsoft OLE DB
Provider for SQL(just moving data from a Oracle table to an SQL Server
table).

It just does not seem to support transactions within the package. Am I
doing something wrong?

Thanks,
Kay




*** Sent via Developersdex http://www.developersdex.com ***

Thank you.

Msdtc.exe is running on source, destination, and the machine that is
running the package. Is there anything that I should check to make sure
the dtc is running properly?

Thanks.



*** Sent via Developersdex http://www.developersdex.com ***

Thanks.

How do I check that MS DTC is working correctly between source and
destination, and
the machine running package?

I am only checking that the service is running on all thes machines.

Thanks.

*** Sent via Developersdex http://www.developersdex.com ***

In message <uZq5ZZYYFHA.2588 (AT) TK2MSFTNGP14 (DOT) phx.gbl>, Kay Lee
<kit_mx1 (AT) hotmail (DOT) com> writes
There are a couple of tools available, DTSPing is one and there is at
least one more, but I forget the name. Search the MS KB, for DTC errors,
such as "cannot enlist in the distributed transaction". A post to the
beta group may also help as hopefully one of the team can expand on the
error code. They are not currently documented. Also ensure you fully
check the output window for the complete error message, They often come
in several parts.



--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Hi Kay,

"Kay Lee" wrote:
there are some troubles with MS DTC with Windows XP SP2 and Windows Server
2003 because they changed the default behaviour of MS DTC. Do you have one
of these systems involved?

Open Windows Administration\Componentservices (mmc) and look the
properties under Componentservices\computer\my computer (right click). In
the section MS DTC check the security settings and check wether network
access for MS DTC is configured.
Also, depending on your actual configuration/implementation you might rely
on XA transactions which require additional configuration in the above
section. Also see the folowing article:
http://support.microsoft.com/default...b;EN-US;817066

Which transaction system do you use on the oracle side, which DB version do
you use?

Helge