I am receiving the following error when I try to run my Package.SSISDeploymentManifest file: TITLE: Package Installation Wizard ------------------------------ Unexpected error occurred. ------------------------------ ADDITIONAL INFORMATION: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B) (DTSInstall) ------------------------------ When this occurs the normal wizard for deployment never appears, just the error message. The SSIS package uses a Web Service task to pull data from a web service, then an XML task to read and parse the data. Then I do some basic transformations, mostly merges and inserts. I know there are some compatibility issues with 64bit Windows and SSIS (especially with Oracle) but this talks to a SQL Server database and an ASP.NET web service. There are also no Script Components/Tasks in the package. I know that this error has something to do with the switch from 32bit BIDS (my searching has shown there isn't a 64bit version of this) and the 64bit server. Is there a specific way to deploy packages on a 64bit server or some configuration setting that I'm missing? Any help would be greatly appreciated!

I have resolved this error in the past in 1 of 2 ways: 1. I had to save the SSIS package off as a file, then login to the SQL server through remote desktop and import the package from the file. In SSMS: -Connect to Integration services; -Expand "Stored Packages" -Right click "File System" Select "Import package" and Choose the file you saved with the .dtsx file extension. This does not resolve your issue, but does get your package deployed and working. 2. If you package has custom components included, you may have to load them in the .net GAC, which can be done from the command prompt. You have to open the command prompt as administrator by right clicking it and choose run as administrator on server 2008. Browse to the folder that contains gacutil.exe through the command line interface and follow the instructions below. Please include the full path to the dll you are trying to load. To install the task assembly into the global assembly cache (GAC), use the command line tool gacutil.exe, or drag the assemblies to the %system%\assembly directory. For convenience, you can also include the call to gacutil.exe in a Post-build Event. The following command installs a component named MyTask.dll into the GAC by using gacutil.exe. gacutil /iF MyTask.dll You must close and reopen SSIS Designer after you install a new version of your custom object. If you have installed earlier versions of your custom object in the global assembly cache, you must remove them before installing the new version. To uninstall an assembly, run gacutil.exe and specify the assembly name with the /u option. For more information about the global assembly cache, see Global Assembly Cache Tool (Gactutil.exe) in the .NET Framework Tools.

Thank you so much for your reply. Unfortunately, I'm not sure it will fix my problem. I should have specified earlier, but I'm attempting to do a File System Deployment as the machine that I'm putting it on only has Integration Services, not a full installation of SQL Server 2008. I do not have access to perform an installation on the SQL Server machine. Any ideas on how to get around this for a File System Deployment? Also, I don't have any references to any custom DLLs in my project. Thanks again, I really appreciate any information!

A file system deployment is equivalent to "COPY". :) Just do that instead. Talk to me now on

I have tried copying and running the dtsx using dtexec.exe but when I do that I get an error saying that the dtsx is corrupted. Also, I use the configuration manager and have a separate configuration file for production settings, which is the main reason I was using the deployment utility.

When you copy and run with DTExec, where/how are you running DTExec? Are you RDP'd into the server machine? If you are and it's reporting corruption, I'd try a reinstall of SSIS bits... Talk to me now on

Yes, it is a remote server. I'll give it a shot if I can, unfortunately I had to get someone else to do the install for me to begin with. Thanks for all of the quick responses!

Also, I'm running DTExec from the command line.

I'd make sure they installed the right version of SSIS - as in 2005/2008 ;) Talk to me now on

I remember solving this problem another way now. I had to compile the SSIS package on a 64-bit OS before deploying it to the 64-bit server. I actually compiled this on a 64-bit virtual machine of server 2003, and the package then ran fine on the server.

Are you using any "Script Component" in you package? If yes, then you have to recompile your package in 64 bit machine and compiled code for 32 bit is different from that of 64 bit machine. HTH! Rakesh

Yes, I experienced the same DTSX corruption error as below also. Failed to open package file "C:\Program Files\Microsoft SQL Server\100\DTS\Packages\TIC\xxx.dtsx" due to error 0x80070005 "Access is denied.". This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. I ended up making a batch file, and run it using Windows Task Scheduler from the Computer Management on 2008 Server. The content of the batch file, as proposed by the Command Line page of the Execute Package Utility. "C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTExec.exe" /DTS "\File System\TIC\xxx" /SERVER ServerName /CONFIGFILE "D:\SSIS\TIC\xxx.dtsConfig" /CHECKPOINTING OFF /REPORTING EWCDI This works. Please "Propose As Answer", if accepted, for others to know.