ssis 64 bit from 32 bit

I am new working with ssis
i am trying to deploy package which is running on 32 bit sql 2005 in 64 bit sql 2005
i get errors like xml not found etc

What are the steps i need to follow to succesfully deploy package which is running on 32 bit successfully even it runs succesfully as a job

What steps i need to follow to over come 64 bit ssis error

Who is Participating?
Megan BrooksSQL Server ConsultantCommented:
There are various ways you can do this. I will decribe what I do or have done in the past, and then if your environment requires something else we can look at that.
For deployment, I simply run the package deployment wizard (manifest file) from a workstation (i86 or x64, doesn't matter) that has the necessary server privileges. I store the package in SQL Server and I store any configuration files (currently I have none--Visual Studio 2008 itself does a good job of managing connection strings) in a directory that the package's runtime identity has read access to.
In the past, for security reasons, I sometimes had to copy the deployment package to the server first and then execute it from there. While I don't normally do this, I did test it just now to verify that it works, and it did. This does appear to run as an i86 (32 bit) process.
To deploy using the wizard, you must have created the deployment package by setting CreateDeploymentUtility to True in the SSIS project properties. By default, the deployment files are located in Bin\Deployment under the SSIS project directory.
You can also simply copy the package file to the desired destination and copy the configuration files to wherever they need to do. I find it more convenient to use the utility. To copy the package directly to SQL Server you would need to connect to the SSIS server using Management Studio. None of this is platform-dependent that I am aware of, although I am sure there are possible scenarios that I don't know about.
To run the package you need to run dtexec. I do this using a SQL Server Agent job. The job step type is SQL Server Integration Services Package, and Run As is set to the name of a SQL Agent Proxy that is configured to run SSIS. The proxy credentials are those of the account under which I want the package to run.
Using this approach I have not encountered any x64 platform issues other than, as I mentioned, the lack of Excel Data Source support.
Megan BrooksSQL Server ConsultantCommented:
Many SSIS packages will run on either platform without modification, as long as they do not use components that are not supported on x64, such as the Excel data source. If you are using package configuration files and deploying to a new server, it's possible that the Windows identity under which the package is running does not have access to the configuration files.
Are you using the package deployment wizard and does the error occur when you run that? Or does the error occur when you try to execute the package after deploying it? Are you running it as a SQL Agent job or some other way?
dba2dbaAuthor Commented:
i am not able to even deploy success fully
i am able to deploy and execute very small packages but not able to work with big packages whoich get and move data from other servers

Can you let me know what is the way to invoke 32bit exe in 64 bit and use it to deploy and run the package
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.