Hi, folks:
I created a simple SSIS package. On the Control Flow, I created a Bulk INsert Task with Destination connection to a the local SQL server, a csv file from a local folder, specify comma delimiter. Then I excute the task and I got this long error message.
[Bulk Insert Task] Error: An error occurred with the following error message: "Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)".The OLE DB provider "BULK" for linked server "(null)" reported an error. The provider did not give any information about the error.The bulk load failed. The column is too long in the data file for row 1, column 1. Verify that the field terminator and row terminator are specified correctly.".

Well..., congratulations. You found a bug in SSIS. I will file it and hopefully we'll improve it in SQL Server 2008. Thanks for the feedback. For now, as a workaround you can use Execute SQL task to do your bulk insert for native and widenative file types. Sorry for inconvinience.

Thanks for your feedback,

Evgeny Koblov,

SQL Server Integration Services

I think I know the answer, if I bulk insert into a table of varchar(50) for all cilumns, then I am OK. But if I load the data into a table with, date, number etc. then it bombs. How do I specify the input format??

Setting timeout to 0 worked for me...

http://www.sqljunkies.com/WebLog/macaw/archive/2005/07/29/16264.aspx

# re: Cannot fetch a row from OLE DB provider BULK for linked server (null) @ Wednesday, October 12, 2005 1:42 PM

when the data flow starts the sql server destination starts waiting for output rows. the default is 30 secs. if you have any slow transformation tasks inbetween the source and destination you could intermittently or always get this. you can up the timeout or set it to 0 so it never timesout.

Kristofor Selden

i set the timeout to 0 , it sill doesnt work for me!!

by time out u mean the connect timeout for the connection manager ,rite ??

The best thing worked for me was just close the complete package project and reopen it and run it again.

Having the same issue. BCP works fine with the same format file, SSIS is too stupid to do the same thing. The most simple task with SSIS always turns out to be so complicated that I hope I never have to do anything truly difficult with it.

PLEASE please bring back DTS. It worked.

Hi there,

On my data Bulk Insert Task works fine when file contains data of different types. Can you give a sample of the file you use for Bulk Insert and describe how your Bulk Insert Task is configured? After that I will be able to investigate that.

Thanks,

Eugene Koblov,

SQL Services Integration Team

I receive the following error message when I try to use the Bulk Insert Task to load data:

Error: 0xC002F304 at Bulk Insert Task, Bulk Insert Task: An error occurred with the following error message: "Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)".The OLE DB provider "BULK" for linked server "(null)" reported an error. The provider did not give any information about the error.The bulk load failed. The column is too long in the data file for row 1, column 4. Verify that the field terminator and row terminator are specified correctly.Bulk load data conversion error (overflow) for row 1, column 1 (rowno).".

Task failed: Bulk Insert Task

In SSMS I am able to issue the following command and the data loads into a table with no error messages:

BULK INSERTTableName
FROM 'C:\Data\Db\TableName.bcp'
WITH (DATAFILETYPE='widenative');

What configuration is required for the Bulk Insert Task in SSIS to make the data load? BTW - the TableName.bcp file is bulk copy file as bcp widenative data type. The properties of the Bulk Insert Task are the following:

DataFileType: DTSBulkInsert_DataFileType_WideNative

RowTerminator: {CR}{LF}

Let me know if you require any other information, thanks for all your help.

Paul

Well..., congratulations. You found a bug in SSIS. I will file it and hopefully we'll improve it in SQL Server 2008. Thanks for the feedback. For now, as a workaround you can use Execute SQL task to do your bulk insert for native and widenative file types. Sorry for inconvinience.

Thanks for your feedback,

Evgeny Koblov,

SQL Server Integration Services

Well..., congratulations. You found a bug in SSIS. I will file it and hopefully we'll improve it in SQL Server 2008. Thanks for the feedback. For now, as a workaround you can use Execute SQL task to do your bulk insert for native and widenative file types. Sorry for inconvinience.

Thanks for your feedback, Evgeny Koblov, SQL Server Integration Services

So does this mean Microsoft will only fix this bug in SQL Server 2008 and leave it unresolved for those who are stuck with SQL Server 2005 for the forseable future? In the real world, not all IT operations can make major DBMS version changesevery few years as if we're putting in the latest version of Visio. Vendors drag their feet on certification, budgets are tight, etc...

Keep the great new technology rolling in, but putting a stop to service packs too quickly (to conserve development resources, force customers tonew versions, or whatever) is going to lead to significant customerbacklash sooner or later.