FIX: "No object exists with a lineage ID" error message when you run an SSIS 2012 package

Article ID: 2714937 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You run a Microsoft SQL Server Integration Services (SSIS) package in SQL Server 2012 Integration Services. The package contains a customized component or a third-party component.
  • The customized or the third-party component contains a property that is an array of lineage IDs.

    Note The ContainsID property and the IsArray property are set to True for the component.
In this scenario, you receive an error message that resembles the following:
[SSIS.Pipeline] Error: No object exists with a lineage ID of number.
[Table Difference] Error: Unable to retrieve fields information, please configure the component.
[SSIS.Pipeline] Error: "ComponentName" failed validation and returned validation status "VS_ISBROKEN."
Note If you use the third-party COZYROC Table Difference Component, you encounter this issue.
Back to the top | Give Feedback

Cause

This issue occurs because the combination of the array of the lineage IDs is returned incorrectly. This causes the failure when the array is parsed.
Back to the top | Give Feedback

Resolution


Cumulative update information

Cumulative update package 1 for SQL Server 2012 Service Pack 1

The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2765331
(http://support.microsoft.com/kb/2765331/ )
Cumulative update package 1 for SQL Server 2012 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2772858
(http://support.microsoft.com/kb/2772858/ )
The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Cumulative update package 3 for SQL Server 2012

The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2723749
(http://support.microsoft.com/kb/2723749/ )
Cumulative update 3 for SQL Server 2012
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828
(http://support.microsoft.com/kb/2692828/ )
The SQL Server 2012 builds that were released after SQL Server 2012 was released
Back to the top | Give Feedback

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

Properties

Article ID: 2714937 - Last Review: November 20, 2012 - Revision: 3.0
Applies to
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Express
  • Microsoft SQL Server 2012 Standard
  • Microsoft SQL Server 2012 Web
  • SQL Server 2012 Enterprise Core
  • Microsoft SQL Server 2012 Business Intelligence
Keywords: 
kbtshoot kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2714937
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top