Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154

  • I'm getting this message when executing the SSISDeploymentManifest file on SQL Server 2005 (32 bit) running on Windows Server 2003 SP1 Standard Edition (64 bit).  The package was created on another SQL Server 2005 machine, where it executes OK.

    I can run the dtsx file OK, only the manifest file has this problem.

    Has anyone come across this one before?

    Thanks

    ===================================

    Unexpected error occurred. (Package Installation Wizard)

    ===================================

    Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154. (Microsoft.SqlServer.ManagedDTS)

    ------------------------------

    Program Location:

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

       at Microsoft.SqlServer.Dts.Deployment.PackageInstallationWizardForm..ctor()

       at Microsoft.SqlServer.Dts.Deployment.PackageInstaller.Main(String[] args)

    ===================================

  • I had the exact same issue with a server I am working with.  When I installed the 64 bit the issue went away.  I could not find the actual problem

  • Also what I did find is that most stuff works normally.  The only thing jacked up is the manifest and occasional errors.  If you upload the DTS from a 32 bit machine onto the 64 bit it works fine. I was worried about that but I have had these jobs running for 3 weeks and they do not fail.  So that is the work around.

  • Thanks for that, I'll try the 64-bit version.  If that resolves it I'm happy!

  • Did you uninstall the 32 bit version first?

  • Please clarify. Are you saying there's both SQL2005 32 and 64 bit versions?

    I have this same problem and cannot get it to go away.

    My SQL2005 Standard does not qualify it as either 32 or 64 bit.

    thanks

  • Hi, I had the same problem. Managed to fix it with the installation of SQL 2005 Sp4.

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

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