I'm having a similar problem to this but it is localised to my machine only. My colleague wrote a package to import an Excel spreadsheet in SQL Server. It works perfectly on his machine but when we transferred the package/solution in its entirety to my machine, the behaviour described in this forum appeared on mine. Does anyone have any ideas why this might be the case. We have the same software version and all drivers on both our computers are the same.