Re: SSIS package won't run in production server
- From: "Francois Malgreve" <francois.malgreve@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 15 Feb 2006 19:39:51 +0700
I also would like to mention that on my production server, only the SSIS
service is installed, not SQL Server itself.
When you run the setup of SQL 2005, it is indeed possible to install only
the SSIS component which is what I need in my case as SSIS packages are run
from a middle tier server and connect to various DBs.
I think this is important as I just discovered that the package can run
successfully when I run it on a server which has a full version of SQL
Server 2005. By that I mean having SQL Database Server + SSIS installed.
I am starting to think that there might be an other component that I would
have to install. Or some dlls missing (bug in the install process?).
In DTS 2000, it was possible to redistribute DTS dlls on machines that did
not have SQL 2000 installed. That was typical when it was needed to run DTS
from an win app or a web app. But I ever read somewhere that there was no
redistributable dlls for SSIS...
Best regards,
Francois Malgreve.
"Francois Malgreve" <francois.malgreve@xxxxxxxxxxxxxxxxxxx> wrote in message
news:uuCn5RiMGHA.740@xxxxxxxxxxxxxxxxxxxxxxx
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
.
- References:
- SSIS package won't run in production server
- From: Francois Malgreve
- SSIS package won't run in production server
- Prev by Date: RE: transfer sql server objects task cannot run on this edition
- Next by Date: Re: SQL 2005, DTS, problems, problems, problems, etc..
- Previous by thread: SSIS package won't run in production server
- Index(es):
Relevant Pages
|
