Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 Transact-SQL (2008)
 64bit error

Author  Topic 

arkiboys
Master Smack Fu Yak Hacker

1433 Posts

Posted - 2011-12-14 : 11:14:43
Hi,
My ssis package reads data from an excel spreadsheet i.e. .xls
And places the data into a sql server table.
The ssis package works fine when I run it from the designer.
Now from the query analyser, I am using dtexec to execute this package and the error is:

Description: 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.

NOTE, I use the same method i.e. dtexec for other ssis packages which use .csv but not sure why I get an error when I use .xls in a ssis package.

And the server I am running it on is a 64bit machine.

Any thoughts please?

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2011-12-14 : 11:23:34
in your command using DTExec replace DTExec with below

"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTExec.exe"

and then see

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/

Go to Top of Page

arkiboys
Master Smack Fu Yak Hacker

1433 Posts

Posted - 2011-12-14 : 11:35:00
This is what I have now:
--set @param = 'DTExec /f ' + @sql
set @param = 'C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTExec.exe /f ' + @sql


the error is:
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
NULL

Any thoughts please?
Thanks
Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2011-12-14 : 11:36:34
as shown in my suggestion wrap the full path within ""

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/

Go to Top of Page

arkiboys
Master Smack Fu Yak Hacker

1433 Posts

Posted - 2011-12-14 : 11:54:39
same error with this.
set @param = '"C:\Program Files (x86)\[Microsoft SQL Server]\100\DTS\Binn\DTExec.exe" /f ' + @sql
Go to Top of Page

arkiboys
Master Smack Fu Yak Hacker

1433 Posts

Posted - 2011-12-14 : 11:59:59
quote:
Originally posted by visakh16

as shown in my suggestion wrap the full path within ""

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/




Not sure what is wrong here. can you see please?
--set @param = 'DTExec /f ' + @sql
set @param = '"C:\Program Files (x86)' + '\Microsoft SQL Server' + '\100\DTS\Binn\DTExec.exe" /f ' + @sql
Go to Top of Page

Lamprey
Master Smack Fu Yak Hacker

4614 Posts

Posted - 2011-12-14 : 12:08:36
When you run a package from within visual studio, I beleive it always runs as 32-bit. If you do not already have the 32bit version of DTExec, you need to install it and use that exe instead.
Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2011-12-14 : 12:29:14
quote:
Originally posted by arkiboys

quote:
Originally posted by visakh16

as shown in my suggestion wrap the full path within ""

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/




Not sure what is wrong here. can you see please?
--set @param = 'DTExec /f ' + @sql
set @param = '"C:\Program Files (x86)' + '\Microsoft SQL Server' + '\100\DTS\Binn\DTExec.exe" /f ' + @sql



one question
what have you've set as value for Run64bitRuntime property in designer when you run package?
it can be found inside project properties debugging tab

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/

Go to Top of Page

arkiboys
Master Smack Fu Yak Hacker

1433 Posts

Posted - 2011-12-14 : 12:38:03
It is false.
And the problem was to do with the string formating.
All done now.
Thanks for your time.
Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2011-12-14 : 12:42:01
quote:
Originally posted by arkiboys

It is false.
And the problem was to do with the string formating.
All done now.
Thanks for your time.


Ok so my guess was right
it was using 64 bit version of DTExec by default and didnt support excel connection manager
by specifying whole path you made it override default and use 32 bit version of DTEXec instead which supports Excel connection

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/

Go to Top of Page

arkiboys
Master Smack Fu Yak Hacker

1433 Posts

Posted - 2011-12-15 : 09:35:29
Thanks again.
Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2011-12-15 : 10:06:40
wc

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/

Go to Top of Page
   

- Advertisement -