none
Package deployment problem

    Question

  • I made a simple project on my system (Windows 7, 64 bit, SSIS 2008, BIDS). I tried to deploy it to a non-local machine (Windows server 2003 64 bit, SP2, SSIS 2005 and 2008, BIDS) to learn how to do deployment. I copied my project Deployment folder to the server. When I clicked the project's .SSISDeploymentManifest file, I got the error below - 

    TITLE: Package Installation Wizard
    ------------------------------

    Unexpected error occurred.

    ------------------------------
    ADDITIONAL INFORMATION:

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

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

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

    Why do I get this error and how do I fix it ? I thought that .SSISDeploymentManifest files are like normal software installation files. You simply save them in some computer and install them by executing them. Enter your preferences and settings during the installation. Simple, right ? But it did not work that way for me. 

    I saw this post, but it did not help -

    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/6a22331f-a2e9-4cff-a616-6ffa296c6db0/failed-to-deploy-ssis-manifest-file?forum=sqlintegrationservices


    • Edited by Greg3tl Sunday, October 06, 2013 9:55 PM
    Sunday, October 06, 2013 8:38 PM

All replies

  • Just run the platform matching setup.exe from the installation media of your SQL Server and choose to repair the installation.

    The shared components are seen in here:


    Arthur My Blog

    Monday, October 07, 2013 1:45 PM
    Moderator
  • A person at this link: COM Factory Component error

    Managed to solve this issue by installing SQL 2005 SP4. Please make sure your 2005 installation, and all other installations are at the latest patch levels (wherever practical).

    Go to sql studio and verify versions:

    SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
    
    [or do the following]
    
    Select @@version

    Verify against: List of SQL Server Builds (or here is a quick excerpt/summary image):

    Also, as Greg3tl mentioned, you additionally may need to repair your SQL server instances.

    Please remember to Mark as Answer, if this helps resolve your issue. Thanks!


    tnjman


    • Edited by TNJMAN Monday, October 07, 2013 2:03 PM instances
    Monday, October 07, 2013 2:00 PM
  • @ArthurZ - I cannot see that image. Please repost it. 

    Thanks.

    Monday, October 07, 2013 4:18 PM
  • My bad, here it is:


    Arthur My Blog

    Monday, October 07, 2013 5:25 PM
    Moderator
  • I am not sure if I could get someone to do that for me. The server is not mine, so I will have to wait. I have a feeling that it could be because SQL Server and SSIS 2005 and 2008 are installed side by side. Perhaps, I will have to disable "something" in 2005 to make my external SSIS 2008 packages work.

    Monday, October 07, 2013 11:53 PM
  • Yes, the side by side issue may be a big part of it.

    tnjman

    It also could be as simple as preferring the 2008 "path" before the 2005 path on that particular server.
    • Edited by TNJMAN Tuesday, October 08, 2013 12:02 AM update
    Monday, October 07, 2013 11:57 PM
  • Yes, the side by side issue may be a big part of it.

    tnjman

    Anyway I can fix that, without any reinstallation and such ? I tried the reverse approach and I don't get any error now. That is, make the package on the server and deploy it on my system. So, I guess its a good indicator that a side by side installation might be responsible.
    • Edited by Greg3tl Tuesday, October 08, 2013 12:03 AM
    Tuesday, October 08, 2013 12:02 AM
  • As i indicated, maybe get someone to change the path order on the server. I am guessing that it might be worth trying. Switch the order of 2005 and 2008 items in the path, but be cautious of anything else that might be impacted by changing that path.

    tnjman

    Note also you likely will have to restart the SQL and SSIS services after thepath change.
    • Edited by TNJMAN Tuesday, October 08, 2013 12:20 AM notes
    Tuesday, October 08, 2013 12:18 AM