VS_ISBROKEN Error After Table Delete
Maybe you have package configuration which caused this problemhttp://www.rad.pasfu.com
July 28th, 2012 3:25am

I have an SSIS package that is using a new table in the DataFlow. The former table has been deleted. The package runs good on it's own; however, when I run it from the MasterPackage, I get the error below. I have tried DelayValidation=True, ValidateExternalMetadata = False, BypassPrepare = false but none of them make a difference. The error message references the deleted table but I do not know where the reference to the table is being held. Information: 0x4004300A at IMPORT NEW, SSIS.Pipeline: Validation phase is beginning. Error: 0xC0202009 at IMPORT NEW, BBTA [58]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E37. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80040E37 Description: "Invalid object name 'STAGE.EQUIPMENT'.". Error: 0xC0202040 at IMPORT NEW, BBTA [58]: Failed to open a fastload rowset for "[he object exists in the database. Error: 0xC004706B at IMPORT NEW, SSIS.Pipeline: "component "EAIODS" (58)" failed validation and returned validation status "VS_ISBROKEN". Error: 0xC004700C at IMPORT NEW, SSIS.Pipeline: One or more component failed validation. Error: 0xC0024107 at IMPORT NEW: There were errors during task validation. Please Vote &/or "Mark As Answer" if this post is helpful to you. Thanks and happy coding :D
Free Windows Admin Tool Kit Click here and download it now
July 28th, 2012 5:45pm

I do not see any reference to that table in the package configuration. I cannot locate where that table is being referenced. It has to do with the MasterPackage since the child succeeds by itself. I've even tried removing the "ExecuteTask" item for the child package and re-creating it with no success. Is something being cached somewhere? Could it be something in the database? The packages pass the initial validation. If I re-create the table in SQL Server, even though I'm not intentionally using it, then the MasterPackage runs. I could also try re-creating the MasterPackage but these approaches are only work-arounds. Please Vote &/or "Mark As Answer" if this post is helpful to you. Thanks and happy coding :D
July 29th, 2012 3:34pm

did you checked Parent Package variable configuration?http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
July 29th, 2012 5:15pm

Hi polymorphic, My guess was also the package configuration which overwrite the database connection string. But as you are saying its not an issue then let's try the following things: 1. http://www.sqlservercentral.com/Forums/Topic875337-148-1.aspx#bm875444 2. Open your SSIS package's code (XML) and search for that table and try to identify where it is referred. Thanks, Khilit http://www.bigator.com
July 29th, 2012 11:37pm

Hi polymorphic, My guess was also the package configuration which overwrite the database connection string. But as you are saying its not an issue then let's try the following things: 1. http://www.sqlservercentral.com/Forums/Topic875337-148-1.aspx#bm875444 2. Open your SSIS package's code (XML) and search for that table and try to identify where it is referred. Thanks, Khilit http://www.bigator.com
Free Windows Admin Tool Kit Click here and download it now
July 29th, 2012 11:48pm

The solution to this problem was that there was an environmental variable set incorrectly on a server. Please Vote &/or "Mark As Answer" if this post is helpful to you. Thanks and happy coding :D
August 6th, 2012 12:44pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics