SSIS package won't run in production server

Hi,

I have a package that I developed on my local machine and runs well. I run
it through the command line on my production server the following way:

D:\test\CMS_MoveContentToLive>dtexec /f
D:\test\CMS_MoveContentToLive\CMSMoveIte
mToLive.dtsx -de

The -de option is because i changed the default security protection level of
the package as BOL says that for the default protection level
(EncryptAllWithUserKey): "Only the user who created or exported the package
can open the package in SSIS Designer or run the package by using the dtexec
command prompt utility."

The problem is that the package does not run successfully and vomits a lot
of error message that I do not understand, such as:

<errorMessage>
Error: 2006-02-15 18:13:43.55
Code: 0xC004706E
Source: Data Flow Task DTS.Pipeline
Description: The module containing "component "Multicast" (637)" cannot
be lo
cated, even though it is registered.
End Error
Error: 2006-02-15 18:13:43.55
Code: 0xC004706E
Source: Data Flow Task DTS.Pipeline
Description: The module containing "component "OLE DB Destination" (756)"
can
not be located, even though it is registered.
End Error
....
Error: 2006-02-15 18:13:43.62
Code: 0xC0048021
Source: Data Flow Task Multicast [637]
Description: The component is missing, not registered, not upgradeable,
or mi
ssing required interfaces. The contact information for this component is
"Multic
ast;Microsoft Corporation;Microsoft SqlServer v9; (C) 2005 Microsoft
Corporation
; All Rights Reserved; http://www.microsoft.com/sql/support;0";.
End Error
Error: 2006-02-15 18:13:43.62
Code: 0xC0047017
Source: Data Flow Task DTS.Pipeline
Description: component "Multicast" (637) failed validation and returned
error
code 0xC0048021.
End Error
</errorMessage>

Notice that at the end it says that the validation failed.

I looked on the internet but I did not found any information regarding this
issue.

I also created a dummy SSIS package that does not have any data flaw but
just have a single SQL task doing a single insert in a table. When i
execute it on the production server, it runs successfully!

Then what is wrong with my "complex" package that all the data flow
components seems to: "can not be located, even though it is registered." ???
To be exact, I have an error for all the data flow components except the
script component.

Thanks for any help.

Best regards,

Francois Malgreve


.

Relevant Pages

  • Re: Performance and Parallelism in SSIS
    ... then your one package would have 10 individual Data Flows in it. ... The requirement is to parallely execute the 10 procs within a SSIS ... Create just one SSIS Package with one Data Flow. ...
    (microsoft.public.sqlserver.dts)
  • Re: SSIS and SSRS integration
    ... after 30 secs the package completes; ... What I forgot to mention in my previous post, is that my data flow ... I use the Conditional Split to "filter" records. ... the report designer is no longer crashing when trying to retrieve ...
    (microsoft.public.sqlserver.dts)
  • Flat File connection manager could not be edited - Package corrupted
    ... I am trying to re-write and old SQL 2000 DTS package for SSIS using VS ... I add a Data Flow Task to the Data Flow tab ... Surprisingly the Connection Manager is still there, ...
    (microsoft.public.sqlserver.dts)
  • Re: SqlServer 2005: Want to set up SSIS job to import flat file data into 18 tables on a nightly bas
    ... > as each pipeline will instantiate its own version of it ... > Yes 16 data flow tasks in 1 package is valid as is one data flow task and ... >>> to call the other packages and use workflow between them. ...
    (microsoft.public.sqlserver.dts)
  • Handle task error
    ... the package to act as if it had suceeded. ... I'm working on a somewhat long ETL where most of my data ... getting from user controlled exel spredsheets. ... data flow never existed? ...
    (microsoft.public.sqlserver.dts)
Loading