August 4, 2011 at 9:05 am
Hi ,
i am just trying to get the data from sql server to an excel using SSIS. Following are the errors i am being encountered with. Any help would be appreciated!
[Excel Destination [16]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E09.
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Excel Destination" (16) failed with error code 0xC0202009 while processing input "Excel Destination Input" (27). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
THanks,
Praveen
August 4, 2011 at 7:50 pm
What tasks do you have in your SSIS Package?
Do you have a Fuzzy Lookup Task?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 5, 2011 at 11:33 am
There should be more errors in your log that you can post, to let us narrow down the potential problems.
But, from my experience using the Excel Destination, I can almost guarantee you that the error is that the values being written into the Excel Destination, are not of the same data type as the values coming from SQL Server through your OLE DB Source.
The biggest source of error comes from the Unicode vs Non-Unicode values. If you have a column in your database which is a VARCHAR column, and you try writing that to an Excel Destination, it will give you an error saying it can't convert between Unicode and Non-Unicode values. For some reason, the Excel Destination always requires strings to be Unicode. So put a Data Conversion task in between, and just map your VARCHAR column to a Unicode (WSTR) field, then you should be set!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply