Run a package with dtexec

  • Hi Experts,

    I created a package that it just inserts data into a SQL table from a flat file. Package runs well on MIDS and in my Computer (where I connect to the database using SQL Server Management Studio, I have an instance of the database. All my files are saving as a File System on a drive of the server)

    I want to run my package as a batch. I’m using this command prompt and works fine on my computer:

    dtexec /FILE "\\ServerName\e\SSIS\SSIS.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

    My problem is when I try to execute the same command in another computer or server. Even as a Job task failed.

    The package has the property of ProtectionLevel as "DontSaveSensitive" and it has a configuration file that include the password of server and user.

    "MyPassword"

    The error that I got on the command prompt running from another computer is:

    Description: The package is attempting to configure from the XML file "\\Server\e\SSIS\SSIS.Configuration.dtsConfig".

    Code: 0x4004300A Source: Data Flow Task DTS.Pipeline

    Description: Validation phase is beginning.

    Code: 0x4004300A

    Source: Data Flow Task DTS.Pipeline

    Description: Validation phase is beginning.

    Code: 0xC00470FE

    Source: Data Flow Task DTS.Pipeline

    Description: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Flat File Source" (129).

    note: I tried to eliminate the configuration file (xml) because I’m running the package on the command prompt but, still it doesn’t work.

    What I’m doing wrong? What I’m missing in the package? I have tried all the options that I read in the Forums. I have spent all week to try to make it work.

    Any advice??

    Regards,

  • i tried to copy this code in my first message but it didnt appear cause the tags.. This is my Configuration File.

    DTSConfiguration

    DTSConfigurationHeading

    DTSConfigurationFileInfo GeneratedBy="User" GeneratedFromPackageName="SSIS" GeneratedFromPackageID="{4137D44F-A958-4268-8180-F6D5172B7BCB}" GeneratedDate="7/24/2009 12:06:40 PM"

    DTSConfigurationHeading

    Configuration ConfiguredType="Property" Path="\Package.Connections[Server.Database.sa].Properties[Password]" ValueType="String”

    ConfiguredValue "MyPassword"ConfiguredValue

    Configuration

    DTSConfiguration

  • Any advice in how to run it either as a SQL Agent Job or using the DTexec Utiliy ??

    Thank you So much

  • Do you have another version of sql server installed on another computer or server? If you do, your dtexec by default will take the path of the first install. You also need to check user permission for db_ssisadmin, db_ssisltduser and db_ssisoperator in msdb system database on another computer or server. Make sure the user who run the package has these three permissions.

  • Thank you so much for your respond.

    This is the situation. My PC has installed SQL 2005 and Visual Studio 2008. The Server where I want to run the package has only SQL 2005. I tried running the utility with the path where I can take the right version. I dont find the solution. What other options do you recommend?

    About the permissions, I just want to know if you talk about the user that has to log in on the Domain?

  • Is your package created in sql server 2008 SSIS or 2005 SSIS? You cannot run 2008 SSIS packge using SSIS 2005.

  • Its created in Visual Studio 2005. But, Since I tried all the solutions posible. I guess I have conflict with the system files version on the computers.. How can I find this ? What's your advice?

    thank you

  • In my PC says:

    Microsoft SQL Server Integration Services Designer

    Version 9.00.4035.00

    in the Server when I need to run the utility says:

    Microsoft SQL Server Integration Services Designer

    Version 9.00.3042.00

  • I think you have to have SSIS server components installed on the server in order to run the package with deexec. Please check.

  • Im sorry for the question.. How I do check that ?

    thank you

  • I fixed the problem. I just re installed the Integration Services component and it worked.

    Thank you for the advices

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply