64-bit Visual Studio 2005 SSIS Task Execution

Question

64-bit Visual Studio 2005 SSIS Task Execution

Andrew Lamberth

Mr or Mrs. 500

Points: 514
More actions
November 26, 2007 at 10:13 am

#180702

I have been trying to run an SSIS package task from 64-bit Visual Studio 2005 and it keeps failing. I created the package with Import Data (loading an Oracle table into SQL Server) from SSMS, this ran successfully. If I try to run this package from within Visual Studio it fails but give no indication as to why. I have loaded the appropriate Oracle OLEDB driver for 64-bit and can connect to the database successfully from with VS.
The package works if I connect to the Integration Services server from SSMS and use Run Package.
The same package works in Visual Studio 2005 32-bit, so I suspect I have a problem with the 64-bit version of Visual Studio.
Has anyone encountered similar issues with loading Oracle data using SSIS in a 64-bit environment?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

wildh SSCarpal Tunnel Points: 4370 More actions · Answer 1

Being able to run a package successfully while it using the service accounts and not being able to run it manually from Visual Studio makes me wonder if it is a security/ permission issue.

Out of interest, are your servers x86 or Itaniums? We are extracting from Oracle to SQL server 2005 on Itaniums and have had several issues with the set up.

Andrew Lamberth Mr or Mrs. 500 Points: 514 More actions · Answer 2

Thanks for the reply.

It is an X64 server

The package doesn't fail completely and performs the following steps:

1. Create table in SQL Server 2005 database (this works)

2. Run query to retrieve the data from the Oracle database (I think this is failing - but no error messages)

3. Load data into table in SQL Server (not sure if it gets this far or not)

Not having any useful errors messages at the point of failure is a problem too.

andy

wildh SSCarpal Tunnel Points: 4370 More actions · Answer 3

Have a word with the Oracle DBA it could be that teh SQL Server Agent has been set up with the correct rights but your user hasnt, so when you run it manually the account you are using may not be allowd to access the database.

Andrew Lamberth Mr or Mrs. 500 Points: 514 More actions · Answer 4

Re-installing SQL Server 2005 64-bit and applying SP2 solved the problem.

Thanks for feedback

Gift Peddie SSC Guru Points: 73570 More actions · Answer 5

There are known issues with this process but another thing to know there is no 64bits VS2005 not even 2008 both can create and process 64bits dll but they remain 32bits applications.

Kind regards,
Gift Peddie