Bulk Insert with another outstanding result set should be run with XACT_ABORT on

All,

I have an SSIS package which calls several other SSIS packages. The "mother" package has TrasactionOption set to "Supported". There is a sequence container and an imbedded Execute Package Task for each of my embedded packages. Each of the sequence containers has TransactionOption = Required. DTC is running.

When I run my mother package I get the following error within the first package executed "Bulk Insert with another outstanding result set should be run with XACT_ABORT on." I've looked high and low for others with this problem, but haven't found any resolution. Can anyone tell me how to resolve this error? I have tried using BEGIN TRANSACTION instead of using Required and I turn on XACT_ABORT, but it doesn't seem to help either. Any help on this would be greatly appreciated.

Thanks

Update on this - I was able to get around this problem by switching to using native SQL Server transactions. However, it still puzzles me that I can't use DTC instead. Please, any help on this problem would be greatly appreciated. Just to add a little more information - there is a SQL Server 2005 instance (destination) and a SQL Server 2000 instance (source) involved. Microsoft? Any answer on this?|||I'm getting the same problem.

An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Bulk Insert with another outstanding result set should be run with XACT_ABORT on."

What does it mean, 'another outstanding resultset'?

I have a bulk insert updating table A (multicast also creates data to update table A history)

This is the first task in a series of 4 with the other 3 occuring directly after the first one, all doing a similar thing. i.e. Bulk insert to table B and table B historysql

Bulk Insert with another outstanding result set should be run with XACT_ABORT on

All,

I have an SSIS package which calls several other SSIS packages. The "mother" package has TrasactionOption set to "Supported". There is a sequence container and an imbedded Execute Package Task for each of my embedded packages. Each of the sequence containers has TransactionOption = Required. DTC is running.

When I run my mother package I get the following error within the first package executed "Bulk Insert with another outstanding result set should be run with XACT_ABORT on." I've looked high and low for others with this problem, but haven't found any resolution. Can anyone tell me how to resolve this error? I have tried using BEGIN TRANSACTION instead of using Required and I turn on XACT_ABORT, but it doesn't seem to help either. Any help on this would be greatly appreciated.

Thanks

Update on this - I was able to get around this problem by switching to using native SQL Server transactions. However, it still puzzles me that I can't use DTC instead. Please, any help on this problem would be greatly appreciated. Just to add a little more information - there is a SQL Server 2005 instance (destination) and a SQL Server 2000 instance (source) involved. Microsoft? Any answer on this?

Bulk Edit DTS Packages

I have a Whole Bunch of DTS packages that copy data from Database1 to Database2.
I want to quickly make duplicates of all these packages, except that they will copy data from Database1 to Database3. Everything else stays the same.
Is there an easy way to do this?Refer to this SQL DTS (http://www.sqldts.com/default.aspx?6,105,204,0,0) link.

Or you can use COPY DATABASE wizard to accomplish the task.

Building/Running a Package.

Hi,

I have a solution, and I have a few projects in this solution. Each project has a few packages in them. The problem/question I have is this: when I am working on one of the packages, I have only this package open. When I try to run/test this package, every single package in every project gets opened, recompiled/rebuilt before my current package gets to run. It's very frastrating and time consuming. Is there a way to somehow disable this weird behavior ? Is there a way to just build the package I am currently working on ?

Please, help.

Thanks,

Victor.

This behavior occurs if you configured the project to build deployment utility - unfortunately, opening package was required for this. You may switch the deployment utility off temporary to avoid this.|||

Thank you, Michael. I'll try that.

Otherwise, I'll have to create a solution for each package separately.