dbTalk Databases Forums  

SSIS Package Error

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss SSIS Package Error in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Terry
 
Posts: n/a

Default SSIS Package Error - 07-31-2006 , 06:56 AM






How can I determine what is causing the following package to fail?

Error: Error 0xC0012050 while loading package file "C:\Documents and
Settings\wardte\Local Settings\Temp\2\InnerPackage.dtsx". Package failed
validation from the ExecutePackage task. The package cannot run. .

Reply With Quote
  #2  
Old   
Terry
 
Posts: n/a

Default RE: SSIS Package Error - 07-31-2006 , 06:59 AM






Here's the rest of the information:

Information: 0x40043006 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Pre-Execute phase is beginning.
Information: 0x4004300C at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Execute phase is beginning.
Information: 0x402090DF at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F}, OLE DB
Destination [2]: The final commit for the data insertion has started.
Information: 0x402090E0 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F}, OLE DB
Destination [2]: The final commit for the data insertion has ended.
Information: 0x40043008 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Post Execute phase is beginning.
Information: 0x40043009 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Cleanup phase is beginning.
Information: 0x4004300B at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: "component "OLE DB Destination" (2)" wrote 0 rows.
Information: 0x4004300A at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Validation phase is beginning.
Information: 0x40043006 at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Pre-Execute phase is beginning.
Information: 0x4004300C at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Execute phase is beginning.
Information: 0x402090DF at {05004535-2B97-4B58-906A-11E69AA53323}, OLE DB
Destination [2]: The final commit for the data insertion has started.
Information: 0x402090E0 at {05004535-2B97-4B58-906A-11E69AA53323}, OLE DB
Destination [2]: The final commit for the data insertion has ended.
Information: 0x40043008 at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Post Execute phase is beginning.
Information: 0x40043009 at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Cleanup phase is beginning.
Information: 0x4004300B at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: "component "OLE DB Destination" (2)" wrote 0 rows.
Information: 0x4004300A at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC},
DTS.Pipeline: Validation phase is beginning.
Error: 0xC0047008 at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
The package contains two objects with the duplicate name of "output column
"ErrorCode" (69)" and "output column "ErrorCode" (14)".
Error: 0xC0047008 at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
The package contains two objects with the duplicate name of "output column
"ErrorColumn" (74)" and "output column "ErrorColumn" (15)".
Error: 0xC004706B at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
"component "OLE DB Source" (1)" failed validation and returned validation
status "VS_ISCORRUPT".
Error: 0xC004700C at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
One or more component failed validation.
Error: 0xC0024107 at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}: There were
errors during task validation.
Error: 0xC00220DE at Execute Inner Package: Error 0xC0012050 while loading
package file "C:\Documents and Settings\wardte\Local
Settings\Temp\2\InnerPackage.dtsx". Package failed validation from the
ExecutePackage task. The package cannot run.
..
Task failed: Execute Inner Package
Task failed: CompensatingSql
SSIS package "Reporting_Database.dtsx" finished: Failure.




"Terry" wrote:

Quote:
How can I determine what is causing the following package to fail?

Error: Error 0xC0012050 while loading package file "C:\Documents and
Settings\wardte\Local Settings\Temp\2\InnerPackage.dtsx". Package failed
validation from the ExecutePackage task. The package cannot run. .

Reply With Quote
  #3  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: SSIS Package Error - 08-01-2006 , 07:50 AM



My investigation would start around here in your output

Error: 0xC0047008 at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
The package contains two objects with the duplicate name of "output column
"ErrorCode" (69)" and "output column "ErrorCode" (14)".
Error: 0xC0047008 at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
The package contains two objects with the duplicate name of "output column
"ErrorColumn" (74)" and "output column "ErrorColumn" (15)".
Error: 0xC004706B at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
"component "OLE DB Source" (1)" failed validation and returned validation
status "VS_ISCORRUPT".
Error: 0xC004700C at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
One or more component failed validation.
Error: 0xC0024107 at {5C909D87


From BOL VS_ISCORRUPT means

The component is irreparably damaged and must be completely reset. The
designer calls the component's ProvideComponentProperties method in
response.

--


Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com



"Terry" <Terry (AT) discussions (DOT) microsoft.com> wrote

Quote:
Here's the rest of the information:

Information: 0x40043006 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Pre-Execute phase is beginning.
Information: 0x4004300C at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Execute phase is beginning.
Information: 0x402090DF at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F}, OLE DB
Destination [2]: The final commit for the data insertion has started.
Information: 0x402090E0 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F}, OLE DB
Destination [2]: The final commit for the data insertion has ended.
Information: 0x40043008 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Post Execute phase is beginning.
Information: 0x40043009 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Cleanup phase is beginning.
Information: 0x4004300B at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: "component "OLE DB Destination" (2)" wrote 0 rows.
Information: 0x4004300A at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Validation phase is beginning.
Information: 0x40043006 at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Pre-Execute phase is beginning.
Information: 0x4004300C at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Execute phase is beginning.
Information: 0x402090DF at {05004535-2B97-4B58-906A-11E69AA53323}, OLE DB
Destination [2]: The final commit for the data insertion has started.
Information: 0x402090E0 at {05004535-2B97-4B58-906A-11E69AA53323}, OLE DB
Destination [2]: The final commit for the data insertion has ended.
Information: 0x40043008 at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Post Execute phase is beginning.
Information: 0x40043009 at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Cleanup phase is beginning.
Information: 0x4004300B at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: "component "OLE DB Destination" (2)" wrote 0 rows.
Information: 0x4004300A at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC},
DTS.Pipeline: Validation phase is beginning.
Error: 0xC0047008 at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
The package contains two objects with the duplicate name of "output column
"ErrorCode" (69)" and "output column "ErrorCode" (14)".
Error: 0xC0047008 at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
The package contains two objects with the duplicate name of "output column
"ErrorColumn" (74)" and "output column "ErrorColumn" (15)".
Error: 0xC004706B at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
"component "OLE DB Source" (1)" failed validation and returned validation
status "VS_ISCORRUPT".
Error: 0xC004700C at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
One or more component failed validation.
Error: 0xC0024107 at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}: There were
errors during task validation.
Error: 0xC00220DE at Execute Inner Package: Error 0xC0012050 while loading
package file "C:\Documents and Settings\wardte\Local
Settings\Temp\2\InnerPackage.dtsx". Package failed validation from the
ExecutePackage task. The package cannot run.
.
Task failed: Execute Inner Package
Task failed: CompensatingSql
SSIS package "Reporting_Database.dtsx" finished: Failure.




"Terry" wrote:

How can I determine what is causing the following package to fail?

Error: Error 0xC0012050 while loading package file "C:\Documents and
Settings\wardte\Local Settings\Temp\2\InnerPackage.dtsx". Package failed
validation from the ExecutePackage task. The package cannot run. .



Reply With Quote
  #4  
Old   
nukemhill
 
Posts: n/a

Default Re: SSIS Package Error - 08-18-2006 , 08:58 AM



Allan. I'm getting a very similar error message when I build and run a
backup package through the wizard:

'Error : errorCode=-1073451000 description=The package contains two objects
with the duplicate name of "output column "ErrorCode" (54)" and "output
column "ErrorCode" (14)". helpFile=dtsmsg.rll ....'

Your explanation below is a little cryptic. Can you elaborate more? Are
you saying the backup package is corrupt? I'm building it from scratch every
time, and I get the same error message. Are you saying the *db* is corrupt?
That would be beyond painful. This *is* a db that was originally built in
2000 and the ported over. If I remember correctly, this was simply a matter
of backing up the db from 2000 and then restoring in 2005. I don't exactly
remember, though.

Any help you can offer would be greatly appreciated.

"Allan Mitchell" wrote:

Quote:
My investigation would start around here in your output

Error: 0xC0047008 at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
The package contains two objects with the duplicate name of "output column
"ErrorCode" (69)" and "output column "ErrorCode" (14)".
Error: 0xC0047008 at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
The package contains two objects with the duplicate name of "output column
"ErrorColumn" (74)" and "output column "ErrorColumn" (15)".
Error: 0xC004706B at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
"component "OLE DB Source" (1)" failed validation and returned validation
status "VS_ISCORRUPT".
Error: 0xC004700C at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
One or more component failed validation.
Error: 0xC0024107 at {5C909D87


From BOL VS_ISCORRUPT means

The component is irreparably damaged and must be completely reset. The
designer calls the component's ProvideComponentProperties method in
response.

--


Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com



"Terry" <Terry (AT) discussions (DOT) microsoft.com> wrote in message
news:25235232-484B-47D2-B734-1771C6014203 (AT) microsoft (DOT) com...
Here's the rest of the information:

Information: 0x40043006 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Pre-Execute phase is beginning.
Information: 0x4004300C at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Execute phase is beginning.
Information: 0x402090DF at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F}, OLE DB
Destination [2]: The final commit for the data insertion has started.
Information: 0x402090E0 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F}, OLE DB
Destination [2]: The final commit for the data insertion has ended.
Information: 0x40043008 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Post Execute phase is beginning.
Information: 0x40043009 at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: Cleanup phase is beginning.
Information: 0x4004300B at {A3C9B3E4-6629-433F-9456-37C2B8C7CF9F},
DTS.Pipeline: "component "OLE DB Destination" (2)" wrote 0 rows.
Information: 0x4004300A at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Validation phase is beginning.
Information: 0x40043006 at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Pre-Execute phase is beginning.
Information: 0x4004300C at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Execute phase is beginning.
Information: 0x402090DF at {05004535-2B97-4B58-906A-11E69AA53323}, OLE DB
Destination [2]: The final commit for the data insertion has started.
Information: 0x402090E0 at {05004535-2B97-4B58-906A-11E69AA53323}, OLE DB
Destination [2]: The final commit for the data insertion has ended.
Information: 0x40043008 at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Post Execute phase is beginning.
Information: 0x40043009 at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: Cleanup phase is beginning.
Information: 0x4004300B at {05004535-2B97-4B58-906A-11E69AA53323},
DTS.Pipeline: "component "OLE DB Destination" (2)" wrote 0 rows.
Information: 0x4004300A at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC},
DTS.Pipeline: Validation phase is beginning.
Error: 0xC0047008 at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
The package contains two objects with the duplicate name of "output column
"ErrorCode" (69)" and "output column "ErrorCode" (14)".
Error: 0xC0047008 at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
The package contains two objects with the duplicate name of "output column
"ErrorColumn" (74)" and "output column "ErrorColumn" (15)".
Error: 0xC004706B at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
"component "OLE DB Source" (1)" failed validation and returned validation
status "VS_ISCORRUPT".
Error: 0xC004700C at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}, DTS.Pipeline:
One or more component failed validation.
Error: 0xC0024107 at {5C909D87-0DA3-47F1-83B5-2FC49ABD6DAC}: There were
errors during task validation.
Error: 0xC00220DE at Execute Inner Package: Error 0xC0012050 while loading
package file "C:\Documents and Settings\wardte\Local
Settings\Temp\2\InnerPackage.dtsx". Package failed validation from the
ExecutePackage task. The package cannot run.
.
Task failed: Execute Inner Package
Task failed: CompensatingSql
SSIS package "Reporting_Database.dtsx" finished: Failure.




"Terry" wrote:

How can I determine what is causing the following package to fail?

Error: Error 0xC0012050 while loading package file "C:\Documents and
Settings\wardte\Local Settings\Temp\2\InnerPackage.dtsx". Package failed
validation from the ExecutePackage task. The package cannot run. .




Reply With Quote
  #5  
Old   
Janthijs van Dam
 
Posts: n/a

Default RE: SSIS Package Error - 07-24-2009 , 08:51 AM



Hi,
I got the same error during development. This is the way I 'solved' it.

I had a master startup package with build number 23. An child package had become build number 43 as I set it as startup package to test some code. Afters setting the master package back as startup package the error occured as soon the child-package with buildnumber 43 started execution the error occured.

Setting the buildnumber within the properties of the child-package to 23 and build the project solved the problem.


From http://www.developmentnow.com/g/103_...kage-Error.htm

Posted via DevelopmentNow.com Groups
http://www.developmentnow.com/g/

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.