Saturday, December 17, 2011

DTExec issues running ssis packages in 64 bit

Couple of days before, I was working on an SSIS package doing importing of some data from Excel spreadsheet to a table in SQL database. I built the package and tested it locally successfully. The intention was to create a sql procedure to call this package to make the excel data import done programmatically through a webpage. This would enable users to upload the data from excel through a screen to sql table and view some reports based on that.
Anyways after completing package, I created a procedure to call package using DTExec as explained in point 5 of below link

I added the script to call DTExec using xp_cmdshell and on testing i got below error message

SSIS Error Code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: The Excel Connection Manager is not supported in the 64-bit version of SSIS, as no OLE DB provider is available.

The reason was straightforward, the excel connection manager used inside package was not supported in 64 bit.
I was a bit surprised because I was able to run this package locally without any error.After doing some analysis, I found out the reason. In SSIS under project -> properties inside Debugging tab there's a property called Run64bitRuntime and it was set to false. That's why package was running fine locally.

My next attempt was to see how to enable package running in 32 bit mode while using DTExec.
I found out that in 64 bit machine there are two versions of DTExec existing one for 32 bit and other for 64 bit. By default, when I'm calling the DTExec the 64 bit version was getting called. So solution was to call 32 bit version explicitly. For this purpose, I modified the script as follows
ie from

EXEC xp_cmdshell 'DTExec /f....'


EXEC xp_cmdshell '"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTExec.exe" /f....'

and this made ure 32 bit version of DTExec was called and  solved the issue
Thought of posting this as somebody facing the same problem will get benefitted...

No comments:

Post a Comment