scheduling the job to process a dts package

I am new to sqlserver.

Could anybody please help me by giving me a syntax for the command in job schedular to run dts package

i enter the job name in the first screen of the wizard.

I entered the step name. type Transact SQL

database msdb

What should i enter in command text box

My dts package name is fullcube.

Thanks in advance

The easiest way to schedule a DTS package in SQL 2000 is to navigate to the package in Enterprise Manager, right click on the package and choose the "Schedule Package..." option.

This will create a SQL Agent job to execute the package, by default I think it encrypts the command line.

The other way to execute a DTS package is to use the DTexec command line utility. To get a list of the parameters for this utility, type in "DTEXEC /?" to a command line window. If you wanted to you could manually do what the "Schedule Package..." screen does and create a SQL job that has a CmdExec step that calls DTExec.

Scheduling Tasks

In Data Transformation Service, Local Packages,
I need to pull data from a SAGE Line 50 v9 database into SQL . I have
created a simple DTS Package to pull one of the tables and prove the concept
.
It is set
up so it drops the existing table, creates it again and then copies
the data across. It runs well when I run it as a package, however it
fails when I run it as a scheduled job.
It seems to drop the table, it then creates the table (this somehow tells me
that I
don't have a permissions problem because the table structure has to be
read from the SAGE database), but finally fails to copy the data.
Error
Step Error Description:The driver returned invalid (or failed to return)
SQL_DRIVER_ODBC_VER: 2.00 (Microsoft OLE DB Provider for ODBC Drivers
(80004005): Cannot find all files in data path)When you run a package interactively, it runs under YOUR permissions. When
you schedule a package it runs under the permissions for the login that SQL
Agent uses... Make sure the SQL Agent login has the appropriate permissions
everywhere
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"GEmsley" <GEmsley@.discussions.microsoft.com> wrote in message
news:56B83EDA-653F-4E3F-83FA-179A645F4824@.microsoft.com...
> In Data Transformation Service, Local Packages,
> I need to pull data from a SAGE Line 50 v9 database into SQL . I have
> created a simple DTS Package to pull one of the tables and prove the
concept.
> It is set
> up so it drops the existing table, creates it again and then copies
> the data across. It runs well when I run it as a package, however it
> fails when I run it as a scheduled job.
> It seems to drop the table, it then creates the table (this somehow tells
me
> that I
> don't have a permissions problem because the table structure has to be
> read from the SAGE database), but finally fails to copy the data.
> Error
> Step Error Description:The driver returned invalid (or failed to return)
> SQL_DRIVER_ODBC_VER: 2.00 (Microsoft OLE DB Provider for ODBC Drivers
> (80004005): Cannot find all files in data path)|||Thanks Wayne Spot on
"Wayne Snyder" wrote:

> When you run a package interactively, it runs under YOUR permissions. When
> you schedule a package it runs under the permissions for the login that SQ
L
> Agent uses... Make sure the SQL Agent login has the appropriate permission
s
> everywhere
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "GEmsley" <GEmsley@.discussions.microsoft.com> wrote in message
> news:56B83EDA-653F-4E3F-83FA-179A645F4824@.microsoft.com...
> concept.
> me
>
>sql

Scheduling Tasks

In Data Transformation Service, Local Packages,
I need to pull data from a SAGE Line 50 v9 database into SQL . I have
created a simple DTS Package to pull one of the tables and prove the concept.
It is set
up so it drops the existing table, creates it again and then copies
the data across. It runs well when I run it as a package, however it
fails when I run it as a scheduled job.
It seems to drop the table, it then creates the table (this somehow tells me
that I
don't have a permissions problem because the table structure has to be
read from the SAGE database), but finally fails to copy the data.
Error
Step Error Description:The driver returned invalid (or failed to return)
SQL_DRIVER_ODBC_VER: 2.00 (Microsoft OLE DB Provider for ODBC Drivers
(80004005): Cannot find all files in data path)When you run a package interactively, it runs under YOUR permissions. When
you schedule a package it runs under the permissions for the login that SQL
Agent uses... Make sure the SQL Agent login has the appropriate permissions
everywhere
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"GEmsley" <GEmsley@.discussions.microsoft.com> wrote in message
news:56B83EDA-653F-4E3F-83FA-179A645F4824@.microsoft.com...
> In Data Transformation Service, Local Packages,
> I need to pull data from a SAGE Line 50 v9 database into SQL . I have
> created a simple DTS Package to pull one of the tables and prove the
concept.
> It is set
> up so it drops the existing table, creates it again and then copies
> the data across. It runs well when I run it as a package, however it
> fails when I run it as a scheduled job.
> It seems to drop the table, it then creates the table (this somehow tells
me
> that I
> don't have a permissions problem because the table structure has to be
> read from the SAGE database), but finally fails to copy the data.
> Error
> Step Error Description:The driver returned invalid (or failed to return)
> SQL_DRIVER_ODBC_VER: 2.00 (Microsoft OLE DB Provider for ODBC Drivers
> (80004005): Cannot find all files in data path)|||Thanks Wayne Spot on
"Wayne Snyder" wrote:
> When you run a package interactively, it runs under YOUR permissions. When
> you schedule a package it runs under the permissions for the login that SQL
> Agent uses... Make sure the SQL Agent login has the appropriate permissions
> everywhere
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "GEmsley" <GEmsley@.discussions.microsoft.com> wrote in message
> news:56B83EDA-653F-4E3F-83FA-179A645F4824@.microsoft.com...
> > In Data Transformation Service, Local Packages,
> > I need to pull data from a SAGE Line 50 v9 database into SQL . I have
> > created a simple DTS Package to pull one of the tables and prove the
> concept.
> > It is set
> > up so it drops the existing table, creates it again and then copies
> > the data across. It runs well when I run it as a package, however it
> > fails when I run it as a scheduled job.
> > It seems to drop the table, it then creates the table (this somehow tells
> me
> > that I
> > don't have a permissions problem because the table structure has to be
> > read from the SAGE database), but finally fails to copy the data.
> >
> > Error
> > Step Error Description:The driver returned invalid (or failed to return)
> > SQL_DRIVER_ODBC_VER: 2.00 (Microsoft OLE DB Provider for ODBC Drivers
> > (80004005): Cannot find all files in data path)
>
>

Scheduling Tasks

In Data Transformation Service, Local Packages,
I need to pull data from a SAGE Line 50 v9 database into SQL . I have
created a simple DTS Package to pull one of the tables and prove the concept.
It is set
up so it drops the existing table, creates it again and then copies
the data across. It runs well when I run it as a package, however it
fails when I run it as a scheduled job.
It seems to drop the table, it then creates the table (this somehow tells me
that I
don't have a permissions problem because the table structure has to be
read from the SAGE database), but finally fails to copy the data.
Error
Step Error Description:The driver returned invalid (or failed to return)
SQL_DRIVER_ODBC_VER: 2.00 (Microsoft OLE DB Provider for ODBC Drivers
(80004005): Cannot find all files in data path)
When you run a package interactively, it runs under YOUR permissions. When
you schedule a package it runs under the permissions for the login that SQL
Agent uses... Make sure the SQL Agent login has the appropriate permissions
everywhere
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"GEmsley" <GEmsley@.discussions.microsoft.com> wrote in message
news:56B83EDA-653F-4E3F-83FA-179A645F4824@.microsoft.com...
> In Data Transformation Service, Local Packages,
> I need to pull data from a SAGE Line 50 v9 database into SQL . I have
> created a simple DTS Package to pull one of the tables and prove the
concept.
> It is set
> up so it drops the existing table, creates it again and then copies
> the data across. It runs well when I run it as a package, however it
> fails when I run it as a scheduled job.
> It seems to drop the table, it then creates the table (this somehow tells
me
> that I
> don't have a permissions problem because the table structure has to be
> read from the SAGE database), but finally fails to copy the data.
> Error
> Step Error Description:The driver returned invalid (or failed to return)
> SQL_DRIVER_ODBC_VER: 2.00 (Microsoft OLE DB Provider for ODBC Drivers
> (80004005): Cannot find all files in data path)
|||Thanks Wayne Spot on
"Wayne Snyder" wrote:

> When you run a package interactively, it runs under YOUR permissions. When
> you schedule a package it runs under the permissions for the login that SQL
> Agent uses... Make sure the SQL Agent login has the appropriate permissions
> everywhere
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "GEmsley" <GEmsley@.discussions.microsoft.com> wrote in message
> news:56B83EDA-653F-4E3F-83FA-179A645F4824@.microsoft.com...
> concept.
> me
>
>

Scheduling SSRS reports using an external scheduling package

We use a scheduling package to coordinate the scheduling of our batch
processes on most of our systems. Is there a way to trigger the
running of an SSRS report this way? And, what the specifics of what
is takes with some examples of how and what needs to be interfaced?
Thanks,On Sep 17, 12:49 pm, thill...@.steelcase.com wrote:
> We use a scheduling package to coordinate the scheduling of our batch
> processes on most of our systems. Is there a way to trigger the
> running of an SSRS report this way? And, what the specifics of what
> is takes with some examples of how and what needs to be interfaced?
> Thanks,
You can look into the rs.exe utility. Also, you might want to consider
calling a URL similar to this one to obtain the physical report file
and then attach it to an email. You can do this in ASP.NET (attaching
the file to an email, streaming the report file directly from an
HTTPRequest of the URL below), etc. It's up to you're preference and
expertise.
http://ServerX/reportserver?/Directory/ReportName&rs:Command=Render&Param1=Param1Value&rs:Format=PDF
Format:
http://<ServerName>/reportserver?/<Directory>/<ReportName>&rs:Command=Render&<ParameterName>=<ParameterValue>&rs:Format=<PDF/CSV/XML/Excel/MHTML>
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

scheduling ssis package

Hi there!!

I have created a ssis package and now i want to schedule it on SQL Server Agent.

How do we create new job for SSIS package?

Rahul Kumar

hi

gotta answer at:

http://msdn2.microsoft.com/en-us/library/ms139805.aspx

thanks and regards

Rahul Kumar

sql

Scheduling SSIS Package

Hi

I am trying to scheduling package using "Executing Sql Server Agent Task" before that I create new job,But there is error in STEP "Command Line Parameter are Invalid"

Anybody help me for configure jobs for Scheduling

I am new to SQL Server

Thanks in Advance

Now I want to save package in MSDB database but its gives en error as follows

"Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. "

Can anybody helpout for this error

Note : Whats modification in SQL Server Setting so did not get this error

Actually here i am trying to save a package in MSDB database for run package through Sql Server job

thnaks in advance for your help

|||

Hi,

I am new to SSIS but have worked on other ETL tools. I was trying to schedule and run a SSIS package using SQL Server Agent. I created the job but when i tried to make a step of the Job, it asks for a type of step in a drop down. I cant see the step type required for running the SSIS packages as mentioned in the help files.

Please help me on this.

Regards,

Samaksh

|||

Doesn't matter. Execute your packages from the cmdexec subsystem using dtexec. You will get more useful error messages as explained here: http://wiki.sqlis.com/default.aspx/SQLISWiki/ScheduledPackages.html

-Jamie

|||Don't you see the type "SQL Server Integration Services Package" as one option in the dropdown? If you choose that, you can select where your package is.|||

Yes, the help file says to look at the "SQL Server Integration Services Package" as the option in the drop down, but i am unable to see it as an option. I tried various ways to check if the i can get to it, but each time "SQL Server Integration Services Package" is not there as an option.

Can this be the issue with the licence of the product or something similar. Because this is bizarre that the option is not coming in the list.

Regards,

Samaksh

Scheduling SSIS Package

Hi

I am trying to scheduling package using "Executing Sql Server Agent Task" before that I create new job,But there is error in STEP "Command Line Parameter are Invalid"

Anybody help me for configure jobs for Scheduling

I am new to SQL Server

Thanks in Advance

Now I want to save package in MSDB database but its gives en error as follows

"Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. "

Can anybody helpout for this error

Note : Whats modification in SQL Server Setting so did not get this error

Actually here i am trying to save a package in MSDB database for run package through Sql Server job

thnaks in advance for your help

|||

Hi,

I am new to SSIS but have worked on other ETL tools. I was trying to schedule and run a SSIS package using SQL Server Agent. I created the job but when i tried to make a step of the Job, it asks for a type of step in a drop down. I cant see the step type required for running the SSIS packages as mentioned in the help files.

Please help me on this.

Regards,

Samaksh

|||

Doesn't matter. Execute your packages from the cmdexec subsystem using dtexec. You will get more useful error messages as explained here: http://wiki.sqlis.com/default.aspx/SQLISWiki/ScheduledPackages.html

-Jamie

|||Don't you see the type "SQL Server Integration Services Package" as one option in the dropdown? If you choose that, you can select where your package is.|||

Yes, the help file says to look at the "SQL Server Integration Services Package" as the option in the drop down, but i am unable to see it as an option. I tried various ways to check if the i can get to it, but each time "SQL Server Integration Services Package" is not there as an option.

Can this be the issue with the licence of the product or something similar. Because this is bizarre that the option is not coming in the list.

Regards,

Samaksh

Scheduling SSIS Package

Hi ,

How do I schedule SSIS package.

Open Books Online. In the index type "packages", then look for scheduling under the Integration Services entry for packages in the index. The default topic "Scheduling Package Execution in SQL Server Agent" gives a good overview. The linked topic "How to: Run a Package Using a SQL Server Agent Job" gives a step by step description.

Scheduling SQL Agent job

Hello Everyone,

I wanted to schedule my SQL Agent Job with SSIS package loading data into Oracle Destination can it be possible, if not. What do i do to schedule my SSIS package?

Thank you

Yes, it is possible. See the following threads / technet articles on setting up a job / credentials / proxy etc.

http://support.microsoft.com/kb/912911

http://support.microsoft.com/?kbid=918760

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1322146&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1955723&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703968&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2068280&SiteID=1

Scheduling SQL 2005 SSIS packages

I have created and run SSIS packages from my workstation that are successful. When I Build and then Deploy the same package to the server and schedule it, it fails. I am using SQL authentication connecting from a SQL 2000 database to a SQL 2005 database via OLE DB connections.

The following is the exported result of the package...

Date,Source,Severity,Step ID,Server,Job Name,Step Name,Notifications,Message,Duration,Sql Severity,Sql Message ID,Operator Emailed,Operator Net sent,Operator Paged,Retries Attempted

05/09/2007 15:46:05,AMS_EnterpriseWarehouse,Error,0,AMSBINT1,AMS_EnterpriseWarehouse,(Job outcome),,The job failed. The Job was invoked by User JDEREP. The last step to run was step 1 (step1).,00:00:01,0,0,,,,0

05/09/2007 15:46:05,AMS_EnterpriseWarehouse,Error,1,AMSBINT1,AMS_EnterpriseWarehouse,step1,,Executed as user: AMSOIL\vector. Error: 2007-05-09 15:46:06.38 Code: 0xC0047017 Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: component "F0005" (1) failed validation and returned error code 0xC020801C. End Error Error: 2007-05-09 15:46:06.38 Code: 0xC004700C Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: One or more component failed validation. End Error Error: 2007-05-09 15:46:06.38 Code: 0xC0024107 Source: JDE Production to AMS BI 7332 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:46:05 PM Finished: 3:46:06 PM Elapsed: 0.75 seconds. The package execution failed. The step failed.,00:00:01,0,0,,,,0
05/09/2007 15:30:00,AMS_EnterpriseWarehouse,Error,0,AMSBINT1,AMS_EnterpriseWarehouse,(Job outcome),,The job failed. The Job was invoked by Schedule 29 (AMS_EnterpriseWarehouse). The last step to run was step 1 (step1).,00:00:01,0,0,,,,0
05/09/2007 15:30:00,AMS_EnterpriseWarehouse,Error,1,AMSBINT1,AMS_EnterpriseWarehouse,step1,,Executed as user: AMSOIL\vector. Error: 2007-05-09 15:30:01.15 Code: 0xC0047017 Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: component "F0005" (1) failed validation and returned error code 0xC020801C. End Error Error: 2007-05-09 15:30:01.15 Code: 0xC004700C Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: One or more component failed validation. End Error Error: 2007-05-09 15:30:01.15 Code: 0xC0024107 Source: JDE Production to AMS BI 7332 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:30:00 PM Finished: 3:30:01 PM Elapsed: 0.734 seconds. The package execution failed. The step failed.,00:00:01,0,0,,,,0
05/09/2007 15:20:00,AMS_EnterpriseWarehouse,Error,0,AMSBINT1,AMS_EnterpriseWarehouse,(Job outcome),,The job failed. The Job was invoked by Schedule 29 (AMS_EnterpriseWarehouse). The last step to run was step 1 (step1).,00:00:01,0,0,,,,0
05/09/2007 15:20:00,AMS_EnterpriseWarehouse,Error,1,AMSBINT1,AMS_EnterpriseWarehouse,step1,,Executed as user: AMSOIL\vector. Error: 2007-05-09 15:20:01.55 Code: 0xC0047017 Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: component "F0005" (1) failed validation and returned error code 0xC020801C. End Error Error: 2007-05-09 15:20:01.55 Code: 0xC004700C Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: One or more component failed validation. End Error Error: 2007-05-09 15:20:01.55 Code: 0xC0024107 Source: JDE Production to AMS BI 7332 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:20:00 PM Finished: 3:20:01 PM Elapsed: 0.703 seconds. The package execution failed. The step failed.,00:00:01,0,0,,,,0
05/09/2007 15:18:00,AMS_EnterpriseWarehouse,Error,0,AMSBINT1,AMS_EnterpriseWarehouse,(Job outcome),,The job failed. The Job was invoked by Schedule 29 (AMS_EnterpriseWarehouse). The last step to run was step 1 (step1).,00:00:01,0,0,,,,0
05/09/2007 15:18:00,AMS_EnterpriseWarehouse,Error,1,AMSBINT1,AMS_EnterpriseWarehouse,step1,,Executed as user: AMSOIL\vector. Error: 2007-05-09 15:18:01.53 Code: 0xC0047017 Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: component "F0005" (1) failed validation and returned error code 0xC020801C. End Error Error: 2007-05-09 15:18:01.53 Code: 0xC004700C Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: One or more component failed validation. End Error Error: 2007-05-09 15:18:01.53 Code: 0xC0024107 Source: JDE Production to AMS BI 7332 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:18:00 PM Finished: 3:18:01 PM Elapsed: 0.766 seconds. The package execution failed. The step failed.,00:00:01,0,0,,,,0

Any help would be greatly appreciated...

Jim

Additionally, when I run this from the command line, I get the following

DTSER_FAILURE (1)

Jim

How are you setting the database connections in your package?|||

The package was created in Visual Studio 2005, the database connections were created within the package under Data Sources by using the Data Source Wizard. Then in the editor for the Execute SQL Task and the Data Flow task, the connection is selected.

The Execute SQL Task is a SQL statement to trucate the destination table.

Then on the Data Flow I select a source table and a destination table for the ETL - actually just copying the data from one table in one db to another table in a different db.

|||Take a look at the topic "Setting the Protection Level of Packages" in Books Online. Depending on the ProtectionLevel setting, the package may not be saving the password for the database, or it may require it to be run under your user account to decrypt the password.|||

Hello,

To run packages as sql agent jobs, I have deployed the package in the ssis server in sql server MSDB with the option 'Rely on server storage for encryption'

I have also added packages that use a package configuration file, the packages refer to the config file via an environment variable. the environment variable is set on the server. The package is also deployed in the ssis server in sql server MSDB with the option rely on server storage for encryption. I have not yet tested it a job that runs this 2nd type of packages , realy uses this package configuration file, or if it is using whatever happend to be in the connection string of the package when I deployed it.

|||does it work?|||

Yes,

the packages definitely use the config file.

Scheduling SQL 2005 SSIS packages

I have created and run SSIS packages from my workstation that are successful. When I Build and then Deploy the same package to the server and schedule it, it fails. I am using SQL authentication connecting from a SQL 2000 database to a SQL 2005 database via OLE DB connections.

The following is the exported result of the package...

Date,Source,Severity,Step ID,Server,Job Name,Step Name,Notifications,Message,Duration,Sql Severity,Sql Message ID,Operator Emailed,Operator Net sent,Operator Paged,Retries Attempted

05/09/2007 15:46:05,AMS_EnterpriseWarehouse,Error,0,AMSBINT1,AMS_EnterpriseWarehouse,(Job outcome),,The job failed. The Job was invoked by User JDEREP. The last step to run was step 1 (step1).,00:00:01,0,0,,,,0

05/09/2007 15:46:05,AMS_EnterpriseWarehouse,Error,1,AMSBINT1,AMS_EnterpriseWarehouse,step1,,Executed as user: AMSOIL\vector. Error: 2007-05-09 15:46:06.38 Code: 0xC0047017 Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: component "F0005" (1) failed validation and returned error code 0xC020801C. End Error Error: 2007-05-09 15:46:06.38 Code: 0xC004700C Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: One or more component failed validation. End Error Error: 2007-05-09 15:46:06.38 Code: 0xC0024107 Source: JDE Production to AMS BI 7332 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:46:05 PM Finished: 3:46:06 PM Elapsed: 0.75 seconds. The package execution failed. The step failed.,00:00:01,0,0,,,,0
05/09/2007 15:30:00,AMS_EnterpriseWarehouse,Error,0,AMSBINT1,AMS_EnterpriseWarehouse,(Job outcome),,The job failed. The Job was invoked by Schedule 29 (AMS_EnterpriseWarehouse). The last step to run was step 1 (step1).,00:00:01,0,0,,,,0
05/09/2007 15:30:00,AMS_EnterpriseWarehouse,Error,1,AMSBINT1,AMS_EnterpriseWarehouse,step1,,Executed as user: AMSOIL\vector. Error: 2007-05-09 15:30:01.15 Code: 0xC0047017 Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: component "F0005" (1) failed validation and returned error code 0xC020801C. End Error Error: 2007-05-09 15:30:01.15 Code: 0xC004700C Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: One or more component failed validation. End Error Error: 2007-05-09 15:30:01.15 Code: 0xC0024107 Source: JDE Production to AMS BI 7332 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:30:00 PM Finished: 3:30:01 PM Elapsed: 0.734 seconds. The package execution failed. The step failed.,00:00:01,0,0,,,,0
05/09/2007 15:20:00,AMS_EnterpriseWarehouse,Error,0,AMSBINT1,AMS_EnterpriseWarehouse,(Job outcome),,The job failed. The Job was invoked by Schedule 29 (AMS_EnterpriseWarehouse). The last step to run was step 1 (step1).,00:00:01,0,0,,,,0
05/09/2007 15:20:00,AMS_EnterpriseWarehouse,Error,1,AMSBINT1,AMS_EnterpriseWarehouse,step1,,Executed as user: AMSOIL\vector. Error: 2007-05-09 15:20:01.55 Code: 0xC0047017 Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: component "F0005" (1) failed validation and returned error code 0xC020801C. End Error Error: 2007-05-09 15:20:01.55 Code: 0xC004700C Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: One or more component failed validation. End Error Error: 2007-05-09 15:20:01.55 Code: 0xC0024107 Source: JDE Production to AMS BI 7332 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:20:00 PM Finished: 3:20:01 PM Elapsed: 0.703 seconds. The package execution failed. The step failed.,00:00:01,0,0,,,,0
05/09/2007 15:18:00,AMS_EnterpriseWarehouse,Error,0,AMSBINT1,AMS_EnterpriseWarehouse,(Job outcome),,The job failed. The Job was invoked by Schedule 29 (AMS_EnterpriseWarehouse). The last step to run was step 1 (step1).,00:00:01,0,0,,,,0
05/09/2007 15:18:00,AMS_EnterpriseWarehouse,Error,1,AMSBINT1,AMS_EnterpriseWarehouse,step1,,Executed as user: AMSOIL\vector. Error: 2007-05-09 15:18:01.53 Code: 0xC0047017 Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: component "F0005" (1) failed validation and returned error code 0xC020801C. End Error Error: 2007-05-09 15:18:01.53 Code: 0xC004700C Source: JDE Production to AMS BI 7332 DTS.Pipeline Description: One or more component failed validation. End Error Error: 2007-05-09 15:18:01.53 Code: 0xC0024107 Source: JDE Production to AMS BI 7332 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:18:00 PM Finished: 3:18:01 PM Elapsed: 0.766 seconds. The package execution failed. The step failed.,00:00:01,0,0,,,,0

Any help would be greatly appreciated...

Jim

Additionally, when I run this from the command line, I get the following

DTSER_FAILURE (1)

Jim

How are you setting the database connections in your package?|||

The package was created in Visual Studio 2005, the database connections were created within the package under Data Sources by using the Data Source Wizard. Then in the editor for the Execute SQL Task and the Data Flow task, the connection is selected.

The Execute SQL Task is a SQL statement to trucate the destination table.

Then on the Data Flow I select a source table and a destination table for the ETL - actually just copying the data from one table in one db to another table in a different db.

|||Take a look at the topic "Setting the Protection Level of Packages" in Books Online. Depending on the ProtectionLevel setting, the package may not be saving the password for the database, or it may require it to be run under your user account to decrypt the password.|||

Hello,

To run packages as sql agent jobs, I have deployed the package in the ssis server in sql server MSDB with the option 'Rely on server storage for encryption'

I have also added packages that use a package configuration file, the packages refer to the config file via an environment variable. the environment variable is set on the server. The package is also deployed in the ssis server in sql server MSDB with the option rely on server storage for encryption. I have not yet tested it a job that runs this 2nd type of packages , realy uses this package configuration file, or if it is using whatever happend to be in the connection string of the package when I deployed it.

|||does it work?|||

Yes,

the packages definitely use the config file.

scheduling package - Urgent

Hi all gurus
If I create a package and schedule it for jobs and then if i delete the
package and create a new package with same name. Then my job for old package
will run on new package which has name of old deleted package?
In my case my old job runs new package.
will it make any problem?
Thanks
AMHuh?
"AM" <anonymous@.codecomments.com> wrote in message
news:Or0wyERRFHA.3544@.TK2MSFTNGP12.phx.gbl...
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old
> package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>|||AM,
If you create a DTS package, then schedule it, then delete the package, and
create a new one with the EXACT same name, your scheduled job will still wor
k.
Hope that answers your question.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602_.html
"AM" wrote:

> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old packa
ge
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>sql

scheduling package - Urgent

Hi all gurus
If I create a package and schedule it for jobs and then if i delete the
package and create a new package with same name. Then my job for old package
will run on new package which has name of old deleted package?
In my case my old job runs new package.
will it make any problem?
Thanks
AMHuh?
"AM" <anonymous@.developersdex.com> wrote in message
news:Or0wyERRFHA.3544@.TK2MSFTNGP12.phx.gbl...
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old
> package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>|||AM,
If you create a DTS package, then schedule it, then delete the package, and
create a new one with the EXACT same name, your scheduled job will still work.
Hope that answers your question.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602­.html
"AM" wrote:
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>

scheduling package- Urgent

Hi all gurus
If I create a package and schedule it for jobs and then if i delete the
package and create a new package with same name. Then my job for old package
will run on new package which has name of old deleted package?
In my case my old job runs new package.
will it make any problem?
Thanks
AM
Huh?
"AM" <anonymous@.codecomments.com> wrote in message
news:Or0wyERRFHA.3544@.TK2MSFTNGP12.phx.gbl...
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old
> package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>
|||AM,
If you create a DTS package, then schedule it, then delete the package, and
create a new one with the EXACT same name, your scheduled job will still work.
Hope that answers your question.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602X.html
"AM" wrote:

> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>

Scheduling not working

I have an Active Task in a DTS which uses CDONTS to send an email. When I
execute the package manually it works. The schedule doesn't. It says in the
job list that it has been successful. The email does not, however, get sent.
The job, server agent and task scheduler are all enabled. I have even tried
setting up the job/dts package on the server in case there was some kind of
permissions issue. Any ideas? Regards, Chris.
The solution was specify a user name that belonged to sysadmin when creating
the package and schedule.
"Chris Kennedy" <chrisknospam@.cybase.co.uk> wrote in message
news:enmaP4%23REHA.3444@.TK2MSFTNGP12.phx.gbl...
> I have an Active Task in a DTS which uses CDONTS to send an email. When I
> execute the package manually it works. The schedule doesn't. It says in
the
> job list that it has been successful. The email does not, however, get
sent.
> The job, server agent and task scheduler are all enabled. I have even
tried
> setting up the job/dts package on the server in case there was some kind
of
> permissions issue. Any ideas? Regards, Chris.
>

Scheduling not working

I have an Active Task in a DTS which uses CDONTS to send an email. When I
execute the package manually it works. The schedule doesn't. It says in the
job list that it has been successful. The email does not, however, get sent.
The job, server agent and task scheduler are all enabled. I have even tried
setting up the job/dts package on the server in case there was some kind of
permissions issue. Any ideas? Regards, Chris.The solution was specify a user name that belonged to sysadmin when creating
the package and schedule.
"Chris Kennedy" <chrisknospam@.cybase.co.uk> wrote in message
news:enmaP4%23REHA.3444@.TK2MSFTNGP12.phx.gbl...
> I have an Active Task in a DTS which uses CDONTS to send an email. When I
> execute the package manually it works. The schedule doesn't. It says in
the
> job list that it has been successful. The email does not, however, get
sent.
> The job, server agent and task scheduler are all enabled. I have even
tried
> setting up the job/dts package on the server in case there was some kind
of
> permissions issue. Any ideas? Regards, Chris.
>

Scheduling not working

I have an Active Task in a DTS which uses CDONTS to send an email. When I
execute the package manually it works. The schedule doesn't. It says in the
job list that it has been successful. The email does not, however, get sent.
The job, server agent and task scheduler are all enabled. I have even tried
setting up the job/dts package on the server in case there was some kind of
permissions issue. Any ideas? Regards, Chris.The solution was specify a user name that belonged to sysadmin when creating
the package and schedule.
"Chris Kennedy" <chrisknospam@.cybase.co.uk> wrote in message
news:enmaP4%23REHA.3444@.TK2MSFTNGP12.phx.gbl...
> I have an Active Task in a DTS which uses CDONTS to send an email. When I
> execute the package manually it works. The schedule doesn't. It says in
the
> job list that it has been successful. The email does not, however, get
sent.
> The job, server agent and task scheduler are all enabled. I have even
tried
> setting up the job/dts package on the server in case there was some kind
of
> permissions issue. Any ideas? Regards, Chris.
>

Scheduling DTS Package using a stored procedure problem

The DTS package runs fine through Enterprise manager successfully.
However, when scheduled through a job that runs the dts through the
following code:

DECLARE @.findfile int
Exec @.findfile = master.dbo.xp_cmdShell 'dir
\\ServerName\folder\filename.xls', no_output
IF (@.findfile=0)
BEGIN
Exec master.dbo.xp_cmdshell 'dtsrun -E -Server\Instance
-N"DataImport"'
END

The servername specified in the above statement in a different server
than the server that the package resides on.

This is the error that I get when I try to run the same code using
query analyzer:

DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1
DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1
DTSRun OnStart: DTSStep_DTSDataPumpTask_1
DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147024893
(80070003)
Error string: The system cannot find the path specified.

Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts80.hlp
Help context: 1100

Error Detail Records:

Error: -2147024893 (80070003); Provider Error: 0 (0)
Error string: The system cannot find the path specified.

Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts80.hlp
Help context: 1100

Error: -2147024893 (80070003); Provider Error: 0 (0)
Error string: Cannot open a log file of specified name. The system
cannot find the path specified.

Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts80.hlp
Help context: 4700

DTSRun OnFinish: DTSStep_DTSDataPumpTask_1

Error: -2147220440 (80040428); Provider Error: 0 (0)
Error string: Package failed because Step
'DTSStep_DTSDataPumpTask_1' failed.
Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts80.hlp
Help context: 700

NULL

The job is owned by the SQLService account(Windows account) that has
System Admin rights and also is part of the Domain Admin User group.
The Domain Admin User group has full rights on the file that the DTS is
trying to access.

Any help in trying to figure out why the schedule job cannot find the
file path would be appreciated.

Thanks

KRI found the problem was the path in the log file : was using a mapped
drive vs a UNC path.

Scheduling DTS package that executes other DTS packages

Hey guys...

We have a particular process in place that uses many different DTS packages that have to be scheduled. We can successfully run a DTS package from EM. Furthermore, we can successfully schedule a DTS package and run it successfully from SQLServerAgent. And finally... I can create a DTS package that executes other DTS packages and execute it successfully from EM.

Our problem is when I attempt to schedule a DTS package that executes other packages I get an error that says:

Error string: Invalid class string Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts.hlp Help context: 713. Process Exit Code 1. The step failed.

I've seen all over the place issues regarding the inability to schedule a DTS package... but we are able to do this. This is just limited to those scheduled packages that have an "Execute Package Task" in them.

Thanks in advance...I dont know wich version of server you got..this ansver goes for 7.0 (might also work on 2000).

You can add an "Execute process task" in the package that should execute other packages (one for each package).
It should run DTSrun.exe, the parameters you need is /S ServerName /U Login /P Password /N PackageName

Works for me!|||I am having the same issue as we speak. It seems that I have the SQL 2000 client tools installed on my WS, but the server is running SQL 7 with SQL 7 client tools. There are some new tasks shipped with SQL 2000. The one I am having the issue with is dynamic properties task. When I open the package on SQL 7, I get an error message that says "Invalid Class String", this is caused becauase the server does not have the same tasks or clients tools installed.

Microsofts workaround is to install the SQL 2000 client tools on the server.

I am looking for a workaround without installing SQL 2000 tools in production.

Any Thoughts?

SHICKS