Hi, I've created an SSIS package to be loaded using my ASP .NET app. Thispackage is kept within the application and loaded via Microsoft.SqlServer.Dts.Runtime.LoadPackage method. My target machine does not have MS SQL Server 2005 installed. So what do I need at minimum to get this up and running? What components do I've to install or copy over? I tried to copy just the class libraries across. I copiedMicrosoft.SQLServer.ManagedDTS.dlland Microsoft.SQLServer.DTSRuntimeWrap.dll into my bin directorybut I got this error: [COMException (0x80040154): Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154.] Microsoft.SqlServer.Dts.Runtime.Application..ctor() +25[DtsPipelineException: Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154.] Microsoft.SqlServer.Dts.Runtime.Application..ctor() +87 I can't find any information online so any insight or advice will be very much appreciated!

You need to install Integration Services from the SQL Server 2005 CD. No more, no less. -jamie

I got the same error. To avoid installing SSIS in the target machine i started a web service in the former machine, where the package is invoked, and then i make a web reference in my project. Its working fine and fast.

Fine but I wonder what will happen if you need to launch a ssis package from VB/C# application.

hello eric/JTeoh , did you find a solution? I am doing the same and am getting the same interop error that JTeoh is sayihng he got. The one file you guys were missing is DTS.dll which is what the {GUID} is on my box - but sorry, even copying that doesnt work. Maybe just registering that one to windows will do it - but then it starts getting slower than simply installing SSIS (which of course we dont want to really do - we want it to be as simple as it was in 2000 - hmmm. backwards steps????) EDIT: (quote from the microsoft website) You cannot run packages outside BI Development Studio on a client computer that does not have Integration Services installed, and the terms of your SQL Server 2005 licensing may not let you install Integration Services on additional computers. SQL Server 2005 Integration Services (SSIS) is now a server component and is not redistributable to client computers in the same manner that the components required for SQL Server 2000 Data Transformation Services (DTS) were redistributable. To run packages from a client computer that does not have Integration Services installed, you must start them in a manner that ensures that the packages run on the server. Craig http://www.salonsoftwaresystem.com

Why don't you want to install SSIS? In order to run a SSIS package you need to have SSIS installed, I don't really understand what your issue is with that. Sorry, I'm obviously not understanding! -Jamie

Hi Jamie, Thanks for helping. We are talking deployment here on a normal non-dev customers machine: I have a .net winform It has a sql express back end It is all downloadble from the web and the customer installs it easily with effective click-once(MSI/bootstrapper) Its on a normal non-development - "customers" machine It does not have SQL Server full strength on it- just express free version. The terms of licensing(i have detailed about in the edit: section in my above post) does not allow you to redistribute in the way you are saying. So for dev its ok as paid for - but for redistributing like you can with .net framework it is not legal practise. Plus its 55 meg download and install - so that another issue. The way around it is to do as the others have said here and connect-in to the server so that it is all running on the internal "free" sql server - that way its ok. My view is its a real step back - I've had to re-write all my "customer-side" data import programs(excel-to-DTS-SQL-Server) Not happy! Thanks for your time, Craig (any of this might be wrong but is based on my current knowledge)

Craig, Sounds like you might be screwed. Unless you can run all packages centrally. -Jamie

I've the same problem with an asp.net page moved from Win 2003 32 bit to Windows Server 2008 R2 64 bit with SSIS 2012 installed. If I'm not wrong your suggestion is to install SQL Server 2005 near SQL Server 2012. Is there a way to modify my projecy to use assembly for 2012? In my web.config I've the following line: <add assembly="Microsoft.SqlServer.ManagedDTS, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91" /> Do I need to reference a new version? Thank you for your help.