Post reply

The error occurs when trying to create dynamically the OLEDB source component.

  • November 15, 2009 at 6:53 pm

    #156401

    We have some programmatically generated SSIS 2005 packages and these are the ones that are not running after installing SQL 2008 last week. The error specifically occurs when trying to create the OLEDB source component. It says: The component is missing, not registered, not upgradeable, or missing required interfaces. But packages created through the SSIS 2005 designer are working fine.

    someone could help me.

    Thanks,

    Shawn

  • November 15, 2009 at 7:54 pm

    #1079500

    From memory, each of the SSIS objects has a unique ID. This may have changed when you installed SQL2008. I suspect the SSIS designer looks up the ID based on the name of each object and maybe your code doesn't.

  • November 17, 2009 at 4:41 am

    #1080153

    Hi..

    According to me the XML generates behind the package in 2008 is different from 2005.

    So, the package u had made in 2005 can be used in 2008, but once it is opened in 2008, the XML behind is automatically changed. So, again if u try to open tht package in 2005, it 'll not work..

    To see the detail.. open tht Package in notepad and compare it with other package (built in 2005).

    Hope it 'll help u..

    Samarth

  • November 17, 2009 at 4:43 am

    #1080154

    Maybe it would help people here if you could post the code fragment which generates the error.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • November 18, 2009 at 7:43 am

    #1080911

    Shawn-859490 (11/15/2009)

    We have some programmatically generated SSIS 2005 packages and these are the ones that are not running after installing SQL 2008 last week. The error specifically occurs when trying to create the OLEDB source component. It says: The component is missing, not registered, not upgradeable, or missing required interfaces. But packages created through the SSIS 2005 designer are working fine.

    someone could help me.

    Thanks,

    Shawn

    Hi Shawn,

    You have to create another application for generation of SSIS 2008 packages. The application you have in place is based on the SSIS 2005 API and the used objects and components have totally different GUID (class identifiers) in 2008.

    ---
    SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Viewing 5 posts - 1 through 4 (of 4 total)

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