I am executing an SSIS package from VB.NET code.  Works great in design mode.  When I publish it (using Click-Once), it works great on development computer but fails on a customer computer:

Microsoft.SqlServer.Dts.Runtime.DtsPipelineException: Retrieving the COM class factory for component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} failed due to the following error: 80040154. —> System.Runtime.InteropServices.COMException (0×80040154): Retrieving the COM class factory for component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} failed due to the following error: 80040154.

   at Microsoft.SqlServer.Dts.Runtime.Package..ctor()

   — End of inner exception stack trace —

   at Microsoft.SqlServer.Dts.Runtime.Package..ctor()

My project references Microsoft.SQLServer.ManagedDTS.

The error occurs on the following line:

Dim objPackage As New Microsoft.SqlServer.Dts.Runtime.Package

Looking at various forum threads, it would appear that it’s because either (1) DLL(s) are not registered on the customer machine, or (2) DLL(s) are missing from the customer machine.  The first explanation doesn’t seem right — even though Microsoft.SQLServer.ManagedDTS is a COM dll, doesn’t .NET provide a wrapper when it references it?  I downloaded Process Explorer from Sysinternals.com to compare loaded DLLs on my dev box to those on the customer’s box and while several dlls are loaded when the line is successfully loaded, all of them exist on the customer box.

Any help would be greatly appreciated.

Report Abuse

09 May 2008, 12:23 AM UTC

jwelch

ModeratorMVP

Posts 3,540

Answer

Re: Error 80040154 using Microsoft.SqlServer.Dts.Runtime.Package

Was this post helpful ?

ManagedDTS is a .NET assembly, not a COM .dll.  The pipeline, however, is a COM dll.

Is the Integration Services service installed on the customer computer?

Bookmark:Digg Del.icio.us Reddit