...read down several posts - I'd suggest focusing on the DTC configuration,
although there's more relevant information there as well.
"SallyT" <soxvar...@gmail.com> wrote in message
news:fadd3fae-9c20-40ed...@d20g2000yqh.googlegroups.com...
> I'm running around in circles trying to debug an issue using a
> transaction in SSIS and am hoping someone can shed better light than
> what I've been able to find. I believe I've read just about every blog
> on using transactions in SSIS, none of which relate to my particular
> problem - most just have cryptic responses and suggections.
>
> background:
> SSIS 2005 (build 9.00.4035.00)
> VS 2005 sp 1
> Package.TransactionOption = Supported
> within the package is a Data Flow Task, TransactionOption =
> Required
> DFT:
> OLEDB connection (SQL Native) - RetainSameConnection = true (I've
> tried setting this both true and false)
> Connection saved in an xml package configuration file.
> The SQL Server in question is not a linked server.
>
> DTC running on source/target server
> DTC running locally on development laptop
>
> ERROR(s) received:
> Error: 0xC001402C at DSTAR_ETL_Dim, Connection manager "OLEDB_xxx":
> The SSIS Runtime has failed to enlist the OLE DB connection in a
> distributed transaction with error 0x8004D024 "The transaction manager
> has disabled its support for remote/network transactions.".
>
> Error: 0xC0202009 at DSTAR_ETL_Dim, Connection manager "OLEDB_xxx":
> SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error
> code: 0x8004D024.
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4659 (20091203) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4659 (20091203) __________
The message was checked by ESET NOD32 Antivirus.