Using SSIS on SS2k5 running on MS Server 2008, using wizard. Very simply, just export results of a view to Excel. Took almost all the defaults. I get this consistent error message (on Pre-Execute): - Pre-execute (Error) Messages Error 0xc0202009: Data Flow Task 1: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E21. (SQL Server Import and Export Wizard) Error 0xc0202025: Data Flow Task 1: Cannot create an OLE DB accessor. Verify that the column metadata is valid. (SQL Server Import and Export Wizard) Error 0xc004701a: Data Flow Task 1: component "Destination - Staff Aug Hours by Discipline Project with Budgets" (52) failed the pre-execute phase and returned error code 0xC0202025. (SQL Server Import and Export Wizard) It does create the Excel file, but doesn't add any valid data. This is a server, and I do not have MS Office installed on it. Here's a look at the data mapping: Jim

Hello, check this post http://social.msdn.microsoft.com/forums/en-US/sqlintegrationservices/thread/16b46dd4-a252-4829-ae2a-fb456d3f18aa Just to test everything working fine, you can export to csv and see if issue is exporting to excel or there is anything else creating this issue. Mostly when you import/export data to excel you need to convert to correct format. Thanks Aamir http://sqlage.blogspot.com/

Good idea, Aamir. I'll do that. Check my edit to my original post as well. ThanksJim

Aamir, I was able to export to txt file. I went back and exported to .xls file. Worked. Frustrating. I've had this happen before, where MS products themselves don't work on Excel .xlsx files. I guess the fact that it's SS2k5 may be the issue. I'll look through the numerous links you led me to and see if I see anything else. Thanks for your help.Jim

The thing is the Data Export Import Wizard samples rows, then decides on the data type, the sampling is very shaloow by default (8 rows), the error you posted is exactly due to the Wizard picking the incorrect datatype, in most cases it does not pick ntext, so in simple words you had a very long text record somewhere toward the bottom of the Excel file. Oftentimes, to resolve a developer needs to adjust the datatypes intelligently. PS: It is easy to blame Microsoft, but please understand that Excel was developed primarily for other reasons than data import export, it is a desktop app that became extremely popular.Arthur My Blog

A quick test would be, select only one column, data type varchar from your table and then export to .xlsx . Maybe some other columns are creating problem. What if you create csv , then you don't need to worry about conversion , your server has proper driver for excel or not. You can open .csv file in Excel and it will be exactly your excel file. Thanks Aamirhttp://sqlage.blogspot.com/

Arthur, my mapping is shown above. Is there another destination mapping I should consider? The description field can get as long as 150 characters. What destination mapping would you use? And why did it work fine using defaults on an xls file? @Aamir, good idea, thanks. Jim

I think your assumptions about the 150 chars is wrong. There perhaps is a record with 1K blanks. Can you export only a subset of records, say 2-3?Arthur My Blog

I think your assumptions about the 150 chars is wrong. There perhaps is a record with 1K blanks. Can you export only a subset of records, say 2-3?Arthur My Blog