Bug?

When I have two connection managers in the DFT and OLEDB source and destination component.

Associating the different conneciton managers to source and destination seem to go through fine with the code below, but the package generated does not have the connection manager associated with the destination.

I get this error on the destionation on opening up the package in the designer.

<Error> A connection Manager has not been assigned to the runtime connection (24) </Error>

SourceOrDestinationComponent.RuntimeConnectionCollection[0].ConnectionManager = DtsConvert.ToConnectionManager90(pkg.Connections[ConnMgrName]);

However when I assign the ID using the code below it seem to work fine. The documentation doesn't mention needing this step, so is this a bug or a documentation issue?

SourceOrDestinationComponent.RuntimeConnectionCollection[0].ConnectionManagerID = pkg.Connections[ConnMgrName].ID;

Also is the BOL documentation being updated for how to program/configure various tasks in SSIS? Without which it is extremely time consuming with a trial and error method if at all impossible to use them (programmatically)

-tim

Tim,

That step is definately needed and the documentation should say so. If it doesn't say it then use the Send feedback link to tell them. You may be surprised at how effective this is.

If you need anything extra in BOL then ask them for it. It is constantly being updated.

-Jamie

|||

Thanks Jamie, I know the folks working on BOL content appreciate the comments.

This seems like a great opportunity to point out the recent/July refresh of BOL

>>>>>>>>>>>>>>>>>>>>>>>>>>>

Download an updated version of the documentation and tutorials for Microsoft SQL Server 2005. See the "Additional Information" section for an update on SQL Server Express Books Online.

http://www.microsoft.com/downloads/details.aspx?FamilyId=BE6A2C5D-00DF-4220-B133-29C1E0B6585F&displaylang=en

There is a separate download for the sample packages, programs, and databases, at http://www.microsoft.com/downloads/details.aspx?familyid=E719ECF7-9F46-4312-AF89-6AD8702E4E6E&displaylang=en.

|||

Thank you both. The new documentation still does not include the required step.

Craig, BOL seem to have provided clearified some of the existing samples , but it still does not contain samples to how to programmatically most components eg: SCD. Can we expect more samples to be updated to BOL going forward?

Till that time what is the recommended way for people to figure out how to use these apart from trial and error

|||

We are continually updating BOL and I will pass along a note on this one and as Jamie noted, using the feedback mechanism for BOL is really the best way. I can certainly suggest/ask for doc changes but requests from customers always carry more weight. One complication is that every connection mgr may behave differently. Connections and data providers are tricky as each has its own behavior.

sql

Bug cannot export/import any dts package on sql 2000 from 2005 manag. studio

I am connectd to a 2000 database and select import and try to

generate a dts to pull in a flat file... the destination is also a 2000 database.. I used to do this using enterprise manager..

Nothing works you get the error:

The operation could not be completed.

The existsonsqlserver mthod has encountered an ole db error code 0x80004005 (client unable to esablish connection) the sql statement issued has failed.

I can connect fine an open query windows and look at all the tables etc...

You can file bugs here:

http://lab.msdn.microsoft.com/productfeedback/default.aspx

Thanks

Bug cannot export/import any dts package on sql 2000 from 2005 manag. studio

I am connectd to a 2000 database and select import and try to

generate a dts to pull in a flat file... the destination is also a 2000 database.. I used to do this using enterprise manager..

Nothing works you get the error:

The operation could not be completed.

The existsonsqlserver mthod has encountered an ole db error code 0x80004005 (client unable to esablish connection) the sql statement issued has failed.

I can connect fine an open query windows and look at all the tables etc...

You can file bugs here:

http://lab.msdn.microsoft.com/productfeedback/default.aspx

Thanks

Bringing data into a flat file

I am trying to bring in the result fo a query to a flat file. The source and destination connections are oK, the mapping is also correct. However I get the following error during execution:

[Flat File Destination [507]] Error: No column was specified to allow the component to advance through the file.

followed by this:

[DTS.Pipeline] Error: component "Flat File Destination" (507) failed the pre-execute phase and returned error code 0xC02020F0.

What is the fix?

Hmmm... never seen that error before. Can you share your package? I'd be interested in seeing it. Perhaps email me via http://blogs.conchango.com/jamiethomson/contact.aspx

I'm not promising that I'll be able to fix it

-Jamie

|||

Jayaram Krishnaswamy wrote:

I am trying to bring in the result fo a query to a flat file. The source and destination connections are oK, the mapping is also correct. However I get the following error during execution:

[Flat File Destination [507]] Error: No column was specified to allow the component to advance through the file.

followed by this:

[DTS.Pipeline] Error: component "Flat File Destination" (507) failed the pre-execute phase and returned error code 0xC02020F0.

What is the fix?

Jay,

Thanks for sending your package.

You don't have anything mapped to [Column 0] in the destination. I am guessing that this is the problem.

-Jamie

|||

Thanks. Perhaps I have to just test various possibilities.

|||

Jayaram Krishnaswamy wrote:

Thanks. Perhaps I have to just test various possibilities.

No. You simply have to put something into that first column.