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
Showing posts with label packages. Show all posts
Showing posts with label packages. Show all posts
Friday, March 30, 2012
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)
>
>
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
>
>
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 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.
Wednesday, March 28, 2012
Scheduling DTS packages in SQLServer 2005 via the Run Time utility
All,
I installed SQLServer 2005 on a new box and installed the DTS Runtime
utility as well so that the DTS packages run in the 2005 environment.
I imported all the DTS packages but I dont know how to schedule each of
them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a DTS
package would create and schedule a job. I'm not sure how to do it here other
than creating the job manually.
Thanks,
rgnCreate an Agent job with a CmdExec jobstep. In this jobstep, you execute DTSRUN.EXE with appropriate
command-line options (see 2000 Books Online for documentation of the command-line options for
DTSRUN.EXE).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> All,
> I installed SQLServer 2005 on a new box and installed the DTS Runtime
> utility as well so that the DTS packages run in the 2005 environment.
> I imported all the DTS packages but I dont know how to schedule each of
> them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a DTS
> package would create and schedule a job. I'm not sure how to do it here other
> than creating the job manually.
> Thanks,
> rgn
>|||rgn,
Apparently, since DTS is being deprecated the scheduling function did not
move over with the legacy support.
However, creating your own job is pretty easy, especially if you examine the
job definitions created for you on your SQL Server 2000 server. In fact, you
may be able to simply script out the jobs from SQL Server 2000 and run those
scripts on your 2005 SQL Server.
Some adjustements may be necessary. For example, if the same logins used
for the jobs on 2000 do not exist on your new 2005 server, you will need to
adjust the scripts to point to the logins you wish to use.
RLF
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> All,
> I installed SQLServer 2005 on a new box and installed the DTS Runtime
> utility as well so that the DTS packages run in the 2005 environment.
> I imported all the DTS packages but I dont know how to schedule each of
> them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a
> DTS
> package would create and schedule a job. I'm not sure how to do it here
> other
> than creating the job manually.
> Thanks,
> rgn
>|||Tibor/Russell,
I should have been clearer in my earlier post. I can create a job for each
one of the DTS packages with DTSRUN. However, I dont know how to generate the
encrypted details of the package name, login name, Password ... etc.
It is against our SOX policy to include password in open text.
THis example is for a different DTS on a different server altogether.[DTSRun
/~Z0xBBA31CD08C42214454A70882A4D929948FA0915B8AA465A7BEF16CCA4AC7639EB256D85DB6780227228D2D92A3FF92D1AAC3354C13AF4CCF5704F24B8EA95C5C95E33BE0EAF73A5ED7C9F1D9AA391B364F64B7473F9E27823B3EF142CE09CF1F1BF7E08A031026BC2F7E03E544C824E13C2584B3C7197F19A12371 ]
Thanks,
rgn
"Russell Fields" wrote:
> rgn,
> Apparently, since DTS is being deprecated the scheduling function did not
> move over with the legacy support.
> However, creating your own job is pretty easy, especially if you examine the
> job definitions created for you on your SQL Server 2000 server. In fact, you
> may be able to simply script out the jobs from SQL Server 2000 and run those
> scripts on your 2005 SQL Server.
> Some adjustements may be necessary. For example, if the same logins used
> for the jobs on 2000 do not exist on your new 2005 server, you will need to
> adjust the scripts to point to the logins you wish to use.
> RLF
>
> "rgn" <rgn@.discussions.microsoft.com> wrote in message
> news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> > All,
> >
> > I installed SQLServer 2005 on a new box and installed the DTS Runtime
> > utility as well so that the DTS packages run in the 2005 environment.
> >
> > I imported all the DTS packages but I dont know how to schedule each of
> > them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a
> > DTS
> > package would create and schedule a job. I'm not sure how to do it here
> > other
> > than creating the job manually.
> >
> > Thanks,
> > rgn
> >
> >
>
>|||rgn,
I poked around a bit and found that the encrypted details are not as secure
as you might wish. So... user beware. Here is how you can generate one:
dtsrun /S ServerName /E /N PackagePathAndName /!Y
You will see that it gives a different encryption each time, but try it out
and see if the results work for you.
Since you are in SQL Server 2005, I encourage you to study up on SQL Agent
Proxies, which use Credentials for Logins to switch execution context before
running the Operating System step of DTSRUN. If that works for you, you can
run your DTS Packages without any user names or passwords in the command
line. Much more secure.
RLF
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:C777E793-E904-4D38-A361-E642C056AF7A@.microsoft.com...
> Tibor/Russell,
> I should have been clearer in my earlier post. I can create a job for each
> one of the DTS packages with DTSRUN. However, I dont know how to generate
> the
> encrypted details of the package name, login name, Password ... etc.
> It is against our SOX policy to include password in open text.
> THis example is for a different DTS on a different server
> altogether.[DTSRun
> /~Z0xBBA31CD08C42214454A70882A4D929948FA0915B8AA465A7BEF16CCA4AC7639EB256D85DB6780227228D2D92A3FF92D1AAC3354C13AF4CCF5704F24B8EA95C5C95E33BE0EAF73A5ED7C9F1D9AA391B364F64B7473F9E27823B3EF142CE09CF1F1BF7E08A031026BC2F7E03E544C824E13C2584B3C7197F19A12371
> ]
> Thanks,
> rgn
> "Russell Fields" wrote:
>> rgn,
>> Apparently, since DTS is being deprecated the scheduling function did not
>> move over with the legacy support.
>> However, creating your own job is pretty easy, especially if you examine
>> the
>> job definitions created for you on your SQL Server 2000 server. In fact,
>> you
>> may be able to simply script out the jobs from SQL Server 2000 and run
>> those
>> scripts on your 2005 SQL Server.
>> Some adjustements may be necessary. For example, if the same logins used
>> for the jobs on 2000 do not exist on your new 2005 server, you will need
>> to
>> adjust the scripts to point to the logins you wish to use.
>> RLF
>>
>> "rgn" <rgn@.discussions.microsoft.com> wrote in message
>> news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
>> > All,
>> >
>> > I installed SQLServer 2005 on a new box and installed the DTS Runtime
>> > utility as well so that the DTS packages run in the 2005 environment.
>> >
>> > I imported all the DTS packages but I dont know how to schedule each of
>> > them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on
>> > a
>> > DTS
>> > package would create and schedule a job. I'm not sure how to do it here
>> > other
>> > than creating the job manually.
>> >
>> > Thanks,
>> > rgn
>> >
>> >
>>sql
I installed SQLServer 2005 on a new box and installed the DTS Runtime
utility as well so that the DTS packages run in the 2005 environment.
I imported all the DTS packages but I dont know how to schedule each of
them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a DTS
package would create and schedule a job. I'm not sure how to do it here other
than creating the job manually.
Thanks,
rgnCreate an Agent job with a CmdExec jobstep. In this jobstep, you execute DTSRUN.EXE with appropriate
command-line options (see 2000 Books Online for documentation of the command-line options for
DTSRUN.EXE).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> All,
> I installed SQLServer 2005 on a new box and installed the DTS Runtime
> utility as well so that the DTS packages run in the 2005 environment.
> I imported all the DTS packages but I dont know how to schedule each of
> them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a DTS
> package would create and schedule a job. I'm not sure how to do it here other
> than creating the job manually.
> Thanks,
> rgn
>|||rgn,
Apparently, since DTS is being deprecated the scheduling function did not
move over with the legacy support.
However, creating your own job is pretty easy, especially if you examine the
job definitions created for you on your SQL Server 2000 server. In fact, you
may be able to simply script out the jobs from SQL Server 2000 and run those
scripts on your 2005 SQL Server.
Some adjustements may be necessary. For example, if the same logins used
for the jobs on 2000 do not exist on your new 2005 server, you will need to
adjust the scripts to point to the logins you wish to use.
RLF
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> All,
> I installed SQLServer 2005 on a new box and installed the DTS Runtime
> utility as well so that the DTS packages run in the 2005 environment.
> I imported all the DTS packages but I dont know how to schedule each of
> them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a
> DTS
> package would create and schedule a job. I'm not sure how to do it here
> other
> than creating the job manually.
> Thanks,
> rgn
>|||Tibor/Russell,
I should have been clearer in my earlier post. I can create a job for each
one of the DTS packages with DTSRUN. However, I dont know how to generate the
encrypted details of the package name, login name, Password ... etc.
It is against our SOX policy to include password in open text.
THis example is for a different DTS on a different server altogether.[DTSRun
/~Z0xBBA31CD08C42214454A70882A4D929948FA0915B8AA465A7BEF16CCA4AC7639EB256D85DB6780227228D2D92A3FF92D1AAC3354C13AF4CCF5704F24B8EA95C5C95E33BE0EAF73A5ED7C9F1D9AA391B364F64B7473F9E27823B3EF142CE09CF1F1BF7E08A031026BC2F7E03E544C824E13C2584B3C7197F19A12371 ]
Thanks,
rgn
"Russell Fields" wrote:
> rgn,
> Apparently, since DTS is being deprecated the scheduling function did not
> move over with the legacy support.
> However, creating your own job is pretty easy, especially if you examine the
> job definitions created for you on your SQL Server 2000 server. In fact, you
> may be able to simply script out the jobs from SQL Server 2000 and run those
> scripts on your 2005 SQL Server.
> Some adjustements may be necessary. For example, if the same logins used
> for the jobs on 2000 do not exist on your new 2005 server, you will need to
> adjust the scripts to point to the logins you wish to use.
> RLF
>
> "rgn" <rgn@.discussions.microsoft.com> wrote in message
> news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> > All,
> >
> > I installed SQLServer 2005 on a new box and installed the DTS Runtime
> > utility as well so that the DTS packages run in the 2005 environment.
> >
> > I imported all the DTS packages but I dont know how to schedule each of
> > them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a
> > DTS
> > package would create and schedule a job. I'm not sure how to do it here
> > other
> > than creating the job manually.
> >
> > Thanks,
> > rgn
> >
> >
>
>|||rgn,
I poked around a bit and found that the encrypted details are not as secure
as you might wish. So... user beware. Here is how you can generate one:
dtsrun /S ServerName /E /N PackagePathAndName /!Y
You will see that it gives a different encryption each time, but try it out
and see if the results work for you.
Since you are in SQL Server 2005, I encourage you to study up on SQL Agent
Proxies, which use Credentials for Logins to switch execution context before
running the Operating System step of DTSRUN. If that works for you, you can
run your DTS Packages without any user names or passwords in the command
line. Much more secure.
RLF
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:C777E793-E904-4D38-A361-E642C056AF7A@.microsoft.com...
> Tibor/Russell,
> I should have been clearer in my earlier post. I can create a job for each
> one of the DTS packages with DTSRUN. However, I dont know how to generate
> the
> encrypted details of the package name, login name, Password ... etc.
> It is against our SOX policy to include password in open text.
> THis example is for a different DTS on a different server
> altogether.[DTSRun
> /~Z0xBBA31CD08C42214454A70882A4D929948FA0915B8AA465A7BEF16CCA4AC7639EB256D85DB6780227228D2D92A3FF92D1AAC3354C13AF4CCF5704F24B8EA95C5C95E33BE0EAF73A5ED7C9F1D9AA391B364F64B7473F9E27823B3EF142CE09CF1F1BF7E08A031026BC2F7E03E544C824E13C2584B3C7197F19A12371
> ]
> Thanks,
> rgn
> "Russell Fields" wrote:
>> rgn,
>> Apparently, since DTS is being deprecated the scheduling function did not
>> move over with the legacy support.
>> However, creating your own job is pretty easy, especially if you examine
>> the
>> job definitions created for you on your SQL Server 2000 server. In fact,
>> you
>> may be able to simply script out the jobs from SQL Server 2000 and run
>> those
>> scripts on your 2005 SQL Server.
>> Some adjustements may be necessary. For example, if the same logins used
>> for the jobs on 2000 do not exist on your new 2005 server, you will need
>> to
>> adjust the scripts to point to the logins you wish to use.
>> RLF
>>
>> "rgn" <rgn@.discussions.microsoft.com> wrote in message
>> news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
>> > All,
>> >
>> > I installed SQLServer 2005 on a new box and installed the DTS Runtime
>> > utility as well so that the DTS packages run in the 2005 environment.
>> >
>> > I imported all the DTS packages but I dont know how to schedule each of
>> > them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on
>> > a
>> > DTS
>> > package would create and schedule a job. I'm not sure how to do it here
>> > other
>> > than creating the job manually.
>> >
>> > Thanks,
>> > rgn
>> >
>> >
>>sql
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
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
Monday, March 26, 2012
Scheduling Data Transformation Services?
Hi,
Our vendor created a series of dts local packages and I'd like to have them
run each night. When I right-click one of the packages and select Schedule
Package it comes up with a default schedule. So it looks like it is already
schedule, which is fine but how do I know if the package was run? Is this
activity tracked in a log somewhere? When I look under Package Log I see
it's empty. Any suggestions?
Thanks in advance,
LinnIn enterprize manager, go to
Management / SQL Server Agent / Jobs
From there you can view job history and edit the job itself.. as well as the
schedule.
"Linn Kubler" <lkubler@.chartwellwisc2.com> wrote in message
news:uBL6RelMGHA.3432@.tk2msftngp13.phx.gbl...
> Hi,
> Our vendor created a series of dts local packages and I'd like to have
> them run each night. When I right-click one of the packages and select
> Schedule Package it comes up with a default schedule. So it looks like it
> is already schedule, which is fine but how do I know if the package was
> run? Is this activity tracked in a log somewhere? When I look under
> Package Log I see it's empty. Any suggestions?
> Thanks in advance,
> Linn
>|||First..I assume you are using ss2k.
If you open up the DTS package, and click Package, Proprties..and the
Logging tab, you will see in the bottom how to create an error file.
You could also set up a task to email yourself when the task completes
successfully(of course for this to work your server must be configured
to use Exchange.)
MJKulangara
http://sqladventures.blogspot.com
Our vendor created a series of dts local packages and I'd like to have them
run each night. When I right-click one of the packages and select Schedule
Package it comes up with a default schedule. So it looks like it is already
schedule, which is fine but how do I know if the package was run? Is this
activity tracked in a log somewhere? When I look under Package Log I see
it's empty. Any suggestions?
Thanks in advance,
LinnIn enterprize manager, go to
Management / SQL Server Agent / Jobs
From there you can view job history and edit the job itself.. as well as the
schedule.
"Linn Kubler" <lkubler@.chartwellwisc2.com> wrote in message
news:uBL6RelMGHA.3432@.tk2msftngp13.phx.gbl...
> Hi,
> Our vendor created a series of dts local packages and I'd like to have
> them run each night. When I right-click one of the packages and select
> Schedule Package it comes up with a default schedule. So it looks like it
> is already schedule, which is fine but how do I know if the package was
> run? Is this activity tracked in a log somewhere? When I look under
> Package Log I see it's empty. Any suggestions?
> Thanks in advance,
> Linn
>|||First..I assume you are using ss2k.
If you open up the DTS package, and click Package, Proprties..and the
Logging tab, you will see in the bottom how to create an error file.
You could also set up a task to email yourself when the task completes
successfully(of course for this to work your server must be configured
to use Exchange.)
MJKulangara
http://sqladventures.blogspot.com
Friday, March 23, 2012
Scheduling
Hi
when scheduling SQL server DTS packages, i know we can set up a chain of
steps saying(let's say) execute step2 on success of step1. But can we specify
multiple chaining...meaning to say that execute step3 on success of both
step1 and step2.
Any help would be appreciated.
Thanks
Neeraj
The default behavior of a SQL Agent job step is to quit the job when an
error occurs. Consequently, step 3 will execute only if both steps 1 and 2
succeed.
Hope this helps.
Dan Guzman
SQL Server MVP
"ReportFAQGuy" <ReportFAQGuy@.discussions.microsoft.com> wrote in message
news:335C71C0-D023-4C11-B99A-907CAC6DE965@.microsoft.com...
> Hi
> when scheduling SQL server DTS packages, i know we can set up a chain of
> steps saying(let's say) execute step2 on success of step1. But can we
> specify
> multiple chaining...meaning to say that execute step3 on success of both
> step1 and step2.
> Any help would be appreciated.
> Thanks
> Neeraj
when scheduling SQL server DTS packages, i know we can set up a chain of
steps saying(let's say) execute step2 on success of step1. But can we specify
multiple chaining...meaning to say that execute step3 on success of both
step1 and step2.
Any help would be appreciated.
Thanks
Neeraj
The default behavior of a SQL Agent job step is to quit the job when an
error occurs. Consequently, step 3 will execute only if both steps 1 and 2
succeed.
Hope this helps.
Dan Guzman
SQL Server MVP
"ReportFAQGuy" <ReportFAQGuy@.discussions.microsoft.com> wrote in message
news:335C71C0-D023-4C11-B99A-907CAC6DE965@.microsoft.com...
> Hi
> when scheduling SQL server DTS packages, i know we can set up a chain of
> steps saying(let's say) execute step2 on success of step1. But can we
> specify
> multiple chaining...meaning to say that execute step3 on success of both
> step1 and step2.
> Any help would be appreciated.
> Thanks
> Neeraj
Scheduling
Hi
when scheduling SQL server DTS packages, i know we can set up a chain of
steps saying(let's say) execute step2 on success of step1. But can we specify
multiple chaining...meaning to say that execute step3 on success of both
step1 and step2.
Any help would be appreciated.
Thanks
NeerajThe default behavior of a SQL Agent job step is to quit the job when an
error occurs. Consequently, step 3 will execute only if both steps 1 and 2
succeed.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"ReportFAQGuy" <ReportFAQGuy@.discussions.microsoft.com> wrote in message
news:335C71C0-D023-4C11-B99A-907CAC6DE965@.microsoft.com...
> Hi
> when scheduling SQL server DTS packages, i know we can set up a chain of
> steps saying(let's say) execute step2 on success of step1. But can we
> specify
> multiple chaining...meaning to say that execute step3 on success of both
> step1 and step2.
> Any help would be appreciated.
> Thanks
> Neerajsql
when scheduling SQL server DTS packages, i know we can set up a chain of
steps saying(let's say) execute step2 on success of step1. But can we specify
multiple chaining...meaning to say that execute step3 on success of both
step1 and step2.
Any help would be appreciated.
Thanks
NeerajThe default behavior of a SQL Agent job step is to quit the job when an
error occurs. Consequently, step 3 will execute only if both steps 1 and 2
succeed.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"ReportFAQGuy" <ReportFAQGuy@.discussions.microsoft.com> wrote in message
news:335C71C0-D023-4C11-B99A-907CAC6DE965@.microsoft.com...
> Hi
> when scheduling SQL server DTS packages, i know we can set up a chain of
> steps saying(let's say) execute step2 on success of step1. But can we
> specify
> multiple chaining...meaning to say that execute step3 on success of both
> step1 and step2.
> Any help would be appreciated.
> Thanks
> Neerajsql
Wednesday, March 21, 2012
Scheduled SSIS
Hello all,
I was very familiar in creating quite complex DTS packages in SQL2000. Now with 2007 that is all gone. I looked at the command line utility and it's UI counter part but these are just for executing. I keep getting references to the SSIS designer but I can't find where it is.
Can someone point me in the right direction?
Thanks,
Jesse
So, dtsrun.exe has now become dtexec.exe and it's counterpart on the UI is dtexecui.exe. The UI you see in the UI there is the same type of ui you'll see in the SQL Server Agent job. You'll just simply need to select SQL Server Integration Services for the step type and you'll get the same screens.
Brian
|||The designer components is installed when you select Client/Workstation components during SQL Setup. Run SQL Server Business Intelligence Development Studio, create new Integration Services project, now you have a package to design.|||Yes I did that but when I open SQL Server Business Intelligence Development Studio it just looks like a standard visual basic studio that there is nothing under new projects that says intergration services project.
Do I just have a bad install maybe?
|||BIDS is a standard Visual Studio, but in the New Project dialog it should contain Business Intelligence Projects folder, with Integration Services Project in it.|||I found it!
I feal incredably greatfull to everyone that helped and incredably stupid for not spoting earlier.
Thank you all.
Scheduled SSIS
Hello all,
I was very familiar in creating quite complex DTS packages in SQL2000. Now with 2007 that is all gone. I looked at the command line utility and it's UI counter part but these are just for executing. I keep getting references to the SSIS designer but I can't find where it is.
Can someone point me in the right direction?
Thanks,
Jesse
So, dtsrun.exe has now become dtexec.exe and it's counterpart on the UI is dtexecui.exe. The UI you see in the UI there is the same type of ui you'll see in the SQL Server Agent job. You'll just simply need to select SQL Server Integration Services for the step type and you'll get the same screens.
Brian
|||The designer components is installed when you select Client/Workstation components during SQL Setup. Run SQL Server Business Intelligence Development Studio, create new Integration Services project, now you have a package to design.|||Yes I did that but when I open SQL Server Business Intelligence Development Studio it just looks like a standard visual basic studio that there is nothing under new projects that says intergration services project.
Do I just have a bad install maybe?
|||BIDS is a standard Visual Studio, but in the New Project dialog it should contain Business Intelligence Projects folder, with Integration Services Project in it.|||I found it!
I feal incredably greatfull to everyone that helped and incredably stupid for not spoting earlier.
Thank you all.
sqlScheduled package failed but still shows as running job
i had scheduled to run a package it failed but a part of the package still shows up on the integration system running packages. i tried to stop it or delete it nothing works. when i try toi run the package even in visual studio that part of the package fails.
how do i remove the running package?
Thanks
jas
Have you clicked Refresh in Management Studio? The list of running packages does not auto-refresh.|||Thanks for the reply.
I tried refreshing nothing worked....but anyway i tried shuting down the sql server and bring it again it worked.
The wierd thing was, when it was hanging it was not even able to execute it in my designer.
Thanks again
jas
Tuesday, March 20, 2012
Scheduled Jobs Failing
I have some Local Packages to import data from Access into SQL which run
fine on but wont run as a scheduled jobs with any steps. TSQL steps run fine
but
DTSRUN /S<server> /E /N<localpackagename>
fails even though it runs on its own.
I noticed that on SQL Server Agent Properties and the Job System tab there
is a checkbox at the bottom relating to CmdExec. On setting this on my
laptop then unsetting it the job does not run on that either now.
Can someone get me out of this hole
Thanks
Andy Willis
Have a look at this:
http://www.support.microsoft.com/?id=269074 How to Run a DTS Package as a
Scheduled Job
Andrew J. Kelly SQL MVP
"Andy Willis" <andrewrwillis@.blueyonder.co.uk> wrote in message
news:e8qeFIT4EHA.208@.TK2MSFTNGP12.phx.gbl...
>I have some Local Packages to import data from Access into SQL which run
> fine on but wont run as a scheduled jobs with any steps. TSQL steps run
> fine
> but
> DTSRUN /S<server> /E /N<localpackagename>
> fails even though it runs on its own.
> I noticed that on SQL Server Agent Properties and the Job System tab there
> is a checkbox at the bottom relating to CmdExec. On setting this on my
> laptop then unsetting it the job does not run on that either now.
> Can someone get me out of this hole
> Thanks
> Andy Willis
>
fine on but wont run as a scheduled jobs with any steps. TSQL steps run fine
but
DTSRUN /S<server> /E /N<localpackagename>
fails even though it runs on its own.
I noticed that on SQL Server Agent Properties and the Job System tab there
is a checkbox at the bottom relating to CmdExec. On setting this on my
laptop then unsetting it the job does not run on that either now.
Can someone get me out of this hole
Thanks
Andy Willis
Have a look at this:
http://www.support.microsoft.com/?id=269074 How to Run a DTS Package as a
Scheduled Job
Andrew J. Kelly SQL MVP
"Andy Willis" <andrewrwillis@.blueyonder.co.uk> wrote in message
news:e8qeFIT4EHA.208@.TK2MSFTNGP12.phx.gbl...
>I have some Local Packages to import data from Access into SQL which run
> fine on but wont run as a scheduled jobs with any steps. TSQL steps run
> fine
> but
> DTSRUN /S<server> /E /N<localpackagename>
> fails even though it runs on its own.
> I noticed that on SQL Server Agent Properties and the Job System tab there
> is a checkbox at the bottom relating to CmdExec. On setting this on my
> laptop then unsetting it the job does not run on that either now.
> Can someone get me out of this hole
> Thanks
> Andy Willis
>
Monday, March 12, 2012
Scheduled job "show step details" more info?
We have some very large DTS packages that are run nightly.
We they fail it is often difficult to diagnose because the error
details in Job History is truncated. Is this information written to a
log anywhere, or is there a setting to increase the amount of
information that is stored?
Or... am I stuck with logging each step.
Thanks for the help,
DGAny ideas? I havent been able to find any info on this. I know others
must be having the same problems.|||Any ideas? I havent been able to find any info on this. I know others
must be having the same problems.|||Any ideas? I havent been able to find any info on this. I know others
must be having the same problems.|||Hi
I believe the job step details are taken from the message column of the
sysjobhistory table which is limited to 1024 characters.
John
"Dave" wrote:
> Any ideas? I havent been able to find any info on this. I know others
> must be having the same problems.
>
We they fail it is often difficult to diagnose because the error
details in Job History is truncated. Is this information written to a
log anywhere, or is there a setting to increase the amount of
information that is stored?
Or... am I stuck with logging each step.
Thanks for the help,
DGAny ideas? I havent been able to find any info on this. I know others
must be having the same problems.|||Any ideas? I havent been able to find any info on this. I know others
must be having the same problems.|||Any ideas? I havent been able to find any info on this. I know others
must be having the same problems.|||Hi
I believe the job step details are taken from the message column of the
sysjobhistory table which is limited to 1024 characters.
John
"Dave" wrote:
> Any ideas? I havent been able to find any info on this. I know others
> must be having the same problems.
>
Scheduled DTS packages
Hi All,
I'm running into a problem executing a dts package. The package completes
fine, however once it gets scheduled it fails. The package references a
script on another server, so I'm assuming the job scheduler is not passing
along my credentials, however I schedule to job to runas me. I've seen the
problem with it would schedule a job that referenced \\machine\c$, but
references shares don't seem to work too.
what am i doing wrong?
Have a look at
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/default...;en-us;Q269074
This has a section on the various security contexts involved. If you are a
sysadmin then the SQLAgent service account needs to be given access to the
remote server.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"michael" <michael@.discussions.microsoft.com> wrote in message
news:E298049D-0691-4262-8A28-C340806E52A1@.microsoft.com...
> Hi All,
> I'm running into a problem executing a dts package. The package
> completes
> fine, however once it gets scheduled it fails. The package references a
> script on another server, so I'm assuming the job scheduler is not passing
> along my credentials, however I schedule to job to runas me. I've seen
> the
> problem with it would schedule a job that referenced \\machine\c$, but
> references shares don't seem to work too.
> what am i doing wrong?
I'm running into a problem executing a dts package. The package completes
fine, however once it gets scheduled it fails. The package references a
script on another server, so I'm assuming the job scheduler is not passing
along my credentials, however I schedule to job to runas me. I've seen the
problem with it would schedule a job that referenced \\machine\c$, but
references shares don't seem to work too.
what am i doing wrong?
Have a look at
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/default...;en-us;Q269074
This has a section on the various security contexts involved. If you are a
sysadmin then the SQLAgent service account needs to be given access to the
remote server.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"michael" <michael@.discussions.microsoft.com> wrote in message
news:E298049D-0691-4262-8A28-C340806E52A1@.microsoft.com...
> Hi All,
> I'm running into a problem executing a dts package. The package
> completes
> fine, however once it gets scheduled it fails. The package references a
> script on another server, so I'm assuming the job scheduler is not passing
> along my credentials, however I schedule to job to runas me. I've seen
> the
> problem with it would schedule a job that referenced \\machine\c$, but
> references shares don't seem to work too.
> what am i doing wrong?
Scheduled DTS packages
Hi All,
I'm running into a problem executing a dts package. The package completes
fine, however once it gets scheduled it fails. The package references a
script on another server, so I'm assuming the job scheduler is not passing
along my credentials, however I schedule to job to runas me. I've seen the
problem with it would schedule a job that referenced \\machine\c$, but
references shares don't seem to work too.
what am i doing wrong?Have a look at
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/defaul...b;en-us;Q269074
This has a section on the various security contexts involved. If you are a
sysadmin then the SQLAgent service account needs to be given access to the
remote server.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"michael" <michael@.discussions.microsoft.com> wrote in message
news:E298049D-0691-4262-8A28-C340806E52A1@.microsoft.com...
> Hi All,
> I'm running into a problem executing a dts package. The package
> completes
> fine, however once it gets scheduled it fails. The package references a
> script on another server, so I'm assuming the job scheduler is not passing
> along my credentials, however I schedule to job to runas me. I've seen
> the
> problem with it would schedule a job that referenced \\machine\c$, but
> references shares don't seem to work too.
> what am i doing wrong?
I'm running into a problem executing a dts package. The package completes
fine, however once it gets scheduled it fails. The package references a
script on another server, so I'm assuming the job scheduler is not passing
along my credentials, however I schedule to job to runas me. I've seen the
problem with it would schedule a job that referenced \\machine\c$, but
references shares don't seem to work too.
what am i doing wrong?Have a look at
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/defaul...b;en-us;Q269074
This has a section on the various security contexts involved. If you are a
sysadmin then the SQLAgent service account needs to be given access to the
remote server.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"michael" <michael@.discussions.microsoft.com> wrote in message
news:E298049D-0691-4262-8A28-C340806E52A1@.microsoft.com...
> Hi All,
> I'm running into a problem executing a dts package. The package
> completes
> fine, however once it gets scheduled it fails. The package references a
> script on another server, so I'm assuming the job scheduler is not passing
> along my credentials, however I schedule to job to runas me. I've seen
> the
> problem with it would schedule a job that referenced \\machine\c$, but
> references shares don't seem to work too.
> what am i doing wrong?
Friday, March 9, 2012
Schedule the integration packages from the web application
Hi all,
I have developed some SSIS packages and scheduling them by using the SQL Server Agent.
But now I want to change all the scheduling from my web application.
is there anyone could help me this?
Do you mean that you want to alter the schedule? If so, this is not an appropriate question for the SSIS forum. The schedule is defined in SQL Server Agent, NOT SSIS.
I do not know if there is an API available for Agent. Try the SMO forum: https://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=88&SiteID=1
-Jamie
Wednesday, March 7, 2012
Schedule package menu grayed out in EM
I tried to schedule a local package under Enterprise Manager\DTS\Local
package by right click local packages. However the Schedule package menu
grayed out. I used the domain login, which is SQL Server system
administrator role. This account is also in the administrators group of SQL
Server machine, and has log in as service and batch privilege. Moreover SQL
agent service is under this account.
Since SQL Server machine box itself does not install Enterprise Manager, I
add SQL Server registration from client machine, which login with above
domain account. Looks like I have all the privileges. I cannot figure out
why Schedule package menu is still grayed out. Please help. Thanks,
Charts
Hi Charts,
Thanks for your post.
From your descriptiosn, I understood Schedule Package menu is grayed out in
your SEM. If I have misunderstood your concern, please feel free to point
it out.
Based on my knowledge, please make sure SQL Agent is correctly started.
Would you please paste the SQL Server logs here? I understand the
information may be sensitive to you, my direct email address is
v-mingqc@.online.microsoft.com (make sure to remove 'online.' before you
click SEND as it's only for SPAM), you may send the file to me directly and
I will keep secure.
If you register this SQL Server in another machine, does "Schedule
Package..." menu also disabled?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Mike,
I made sure SQL agent started and running. There are so many logs in event
viewer for SQLAgent$InstanceName, most of them are not relevant. SQL Server
machine itself does not have SEM, so I used other machines to register for
SQL Server. I have two other questions. 1) Am I able to install SEM in the
server machine without affecting the SQL Server activities? 2) How do I use
dtsrun utility to schedule a package? Can you give me an example for syntax
using pseudo SQL name? Thanks a lot for your help.
Charts
"Michael Cheng [MSFT]" wrote:
> Hi Charts,
> Thanks for your post.
> From your descriptiosn, I understood Schedule Package menu is grayed out in
> your SEM. If I have misunderstood your concern, please feel free to point
> it out.
> Based on my knowledge, please make sure SQL Agent is correctly started.
> Would you please paste the SQL Server logs here? I understand the
> information may be sensitive to you, my direct email address is
> v-mingqc@.online.microsoft.com (make sure to remove 'online.' before you
> click SEND as it's only for SPAM), you may send the file to me directly and
> I will keep secure.
> If you register this SQL Server in another machine, does "Schedule
> Package..." menu also disabled?
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Charts,
Thanks for your prompt update.
For your questions[vbcol=seagreen]
Yes, SQL Server Enterprise Manager is the component of SQL Server Client
Tools, registering SQL Server instance with SEM won't affect SQL Server
activities.
Please register the SQL Server in a new machine and see whether it will
reproduce this issue on that new machine.
[vbcol=seagreen]
an[vbcol=seagreen]
Here is a simple example: C:\> dtsrun /s <server name> /e /N <DTS package
name>
If you want to schedule it, create a job and let it execute the command in
a regular time.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thanks Mike,
It’s very helpful. For question 1) it’s not the issue registering SQL
Server instance. I don’t have SQL enterprise manager installed in the server
machine, and I wanted to install this tool without affecting server. I guess
I need to put SQL Server 2000 installation CD in and start install process.
Can you give me some instruction for safe installation since this is existing
server?
Charts
"Michael Cheng [MSFT]" wrote:
> Hi Charts,
> Thanks for your prompt update.
> For your questions
> Yes, SQL Server Enterprise Manager is the component of SQL Server Client
> Tools, registering SQL Server instance with SEM won't affect SQL Server
> activities.
> Please register the SQL Server in a new machine and see whether it will
> reproduce this issue on that new machine.
> an
> Here is a simple example: C:\> dtsrun /s <server name> /e /N <DTS package
> name>
> If you want to schedule it, create a job and let it execute the command in
> a regular time.
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/tec...rview/40010469
> Others: https://partner.microsoft.com/US/tec...pportoverview/
> If you are outside the United States, please visit our International
> Support page: http://support.microsoft.com/common/international.aspx
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Charts,
Thanks for your update.
Based on my knowledge, if you install SQL Server in the machine, SQL Server
Client Tools will also be installed, so I am not very sure your scenario.
Would you please help me explain it clearly? More detailed descriptions, I
believe, will make us closer to the resolution.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Never mind Mike,
I found EM component in the server component installation. Thanks for your
help.
Charts
"Michael Cheng [MSFT]" wrote:
> Hi Charts,
> Thanks for your update.
> Based on my knowledge, if you install SQL Server in the machine, SQL Server
> Client Tools will also be installed, so I am not very sure your scenario.
> Would you please help me explain it clearly? More detailed descriptions, I
> believe, will make us closer to the resolution.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Charts,
That's OK and let's go back to see why Schedule package menu grayed out.
If you register this SQL Server in another machine, does "Schedule
Package..." menu also disabled?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
package by right click local packages. However the Schedule package menu
grayed out. I used the domain login, which is SQL Server system
administrator role. This account is also in the administrators group of SQL
Server machine, and has log in as service and batch privilege. Moreover SQL
agent service is under this account.
Since SQL Server machine box itself does not install Enterprise Manager, I
add SQL Server registration from client machine, which login with above
domain account. Looks like I have all the privileges. I cannot figure out
why Schedule package menu is still grayed out. Please help. Thanks,
Charts
Hi Charts,
Thanks for your post.
From your descriptiosn, I understood Schedule Package menu is grayed out in
your SEM. If I have misunderstood your concern, please feel free to point
it out.
Based on my knowledge, please make sure SQL Agent is correctly started.
Would you please paste the SQL Server logs here? I understand the
information may be sensitive to you, my direct email address is
v-mingqc@.online.microsoft.com (make sure to remove 'online.' before you
click SEND as it's only for SPAM), you may send the file to me directly and
I will keep secure.
If you register this SQL Server in another machine, does "Schedule
Package..." menu also disabled?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Mike,
I made sure SQL agent started and running. There are so many logs in event
viewer for SQLAgent$InstanceName, most of them are not relevant. SQL Server
machine itself does not have SEM, so I used other machines to register for
SQL Server. I have two other questions. 1) Am I able to install SEM in the
server machine without affecting the SQL Server activities? 2) How do I use
dtsrun utility to schedule a package? Can you give me an example for syntax
using pseudo SQL name? Thanks a lot for your help.
Charts
"Michael Cheng [MSFT]" wrote:
> Hi Charts,
> Thanks for your post.
> From your descriptiosn, I understood Schedule Package menu is grayed out in
> your SEM. If I have misunderstood your concern, please feel free to point
> it out.
> Based on my knowledge, please make sure SQL Agent is correctly started.
> Would you please paste the SQL Server logs here? I understand the
> information may be sensitive to you, my direct email address is
> v-mingqc@.online.microsoft.com (make sure to remove 'online.' before you
> click SEND as it's only for SPAM), you may send the file to me directly and
> I will keep secure.
> If you register this SQL Server in another machine, does "Schedule
> Package..." menu also disabled?
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Charts,
Thanks for your prompt update.
For your questions[vbcol=seagreen]
Yes, SQL Server Enterprise Manager is the component of SQL Server Client
Tools, registering SQL Server instance with SEM won't affect SQL Server
activities.
Please register the SQL Server in a new machine and see whether it will
reproduce this issue on that new machine.
[vbcol=seagreen]
an[vbcol=seagreen]
Here is a simple example: C:\> dtsrun /s <server name> /e /N <DTS package
name>
If you want to schedule it, create a job and let it execute the command in
a regular time.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thanks Mike,
It’s very helpful. For question 1) it’s not the issue registering SQL
Server instance. I don’t have SQL enterprise manager installed in the server
machine, and I wanted to install this tool without affecting server. I guess
I need to put SQL Server 2000 installation CD in and start install process.
Can you give me some instruction for safe installation since this is existing
server?
Charts
"Michael Cheng [MSFT]" wrote:
> Hi Charts,
> Thanks for your prompt update.
> For your questions
> Yes, SQL Server Enterprise Manager is the component of SQL Server Client
> Tools, registering SQL Server instance with SEM won't affect SQL Server
> activities.
> Please register the SQL Server in a new machine and see whether it will
> reproduce this issue on that new machine.
> an
> Here is a simple example: C:\> dtsrun /s <server name> /e /N <DTS package
> name>
> If you want to schedule it, create a job and let it execute the command in
> a regular time.
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/tec...rview/40010469
> Others: https://partner.microsoft.com/US/tec...pportoverview/
> If you are outside the United States, please visit our International
> Support page: http://support.microsoft.com/common/international.aspx
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Charts,
Thanks for your update.
Based on my knowledge, if you install SQL Server in the machine, SQL Server
Client Tools will also be installed, so I am not very sure your scenario.
Would you please help me explain it clearly? More detailed descriptions, I
believe, will make us closer to the resolution.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Never mind Mike,
I found EM component in the server component installation. Thanks for your
help.
Charts
"Michael Cheng [MSFT]" wrote:
> Hi Charts,
> Thanks for your update.
> Based on my knowledge, if you install SQL Server in the machine, SQL Server
> Client Tools will also be installed, so I am not very sure your scenario.
> Would you please help me explain it clearly? More detailed descriptions, I
> believe, will make us closer to the resolution.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Charts,
That's OK and let's go back to see why Schedule package menu grayed out.
If you register this SQL Server in another machine, does "Schedule
Package..." menu also disabled?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
schedule new verion of DTS Package
I have several DTS Packages that are scheduled to run every night. If I
change the Packages, which version will be run the following night? If its
the old one, how to I update the schedule to recognize the new version?
SQL2K SP3
TIA, ChrisR
If you do not specify the version # then it is always the latest
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"ChrisR" <bla@.noemail.com> wrote in message
news:Oypg1xKBFHA.2792@.TK2MSFTNGP15.phx.gbl...
>I have several DTS Packages that are scheduled to run every night. If I
> change the Packages, which version will be run the following night? If its
> the old one, how to I update the schedule to recognize the new version?
> --
> SQL2K SP3
> TIA, ChrisR
>
|||Thanks Allen. Im still a bit in the dark though?
Is the version cotained in this type of deal?
DTSRun /~Z0x9F8F7D0B93BlaBlaBla
Is it updated when a new version is added?
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:eZh24$KBFHA.2788@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> If you do not specify the version # then it is always the latest
> --
>
> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> www.SQLDTS.com - The site for all your DTS needs.
> www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
> www.konesans.com - Consultancy from the people who know
>
> "ChrisR" <bla@.noemail.com> wrote in message
> news:Oypg1xKBFHA.2792@.TK2MSFTNGP15.phx.gbl...
its
>
|||yuck.
This will wrap version up for you and you cannoot change it unless you
regenerate the string (DTSRUNUI). Personally I prefer to use the DTSRUN and
the non-encrypted versions.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"ChrisR" <bla@.noemail.com> wrote in message
news:%23QnYYxLBFHA.2112@.TK2MSFTNGP14.phx.gbl...
> Thanks Allen. Im still a bit in the dark though?
> Is the version cotained in this type of deal?
> DTSRun /~Z0x9F8F7D0B93BlaBlaBla
> Is it updated when a new version is added?
>
> "Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
> news:eZh24$KBFHA.2788@.TK2MSFTNGP15.phx.gbl...
> its
>
|||Sorry to be such a pain Allan, but now Im really lost. Do you know if the
version gets updated when stored this way?
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:ukprc3LBFHA.1564@.TK2MSFTNGP09.phx.gbl...
> yuck.
> This will wrap version up for you and you cannoot change it unless you
> regenerate the string (DTSRUNUI). Personally I prefer to use the DTSRUN
and[vbcol=seagreen]
> the non-encrypted versions.
>
> --
>
> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> www.SQLDTS.com - The site for all your DTS needs.
> www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
> www.konesans.com - Consultancy from the people who know
>
> "ChrisR" <bla@.noemail.com> wrote in message
> news:%23QnYYxLBFHA.2112@.TK2MSFTNGP14.phx.gbl...
I[vbcol=seagreen]
If[vbcol=seagreen]
version?
>
|||No it does not.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"ChrisR" <bla@.noemail.com> wrote in message
news:ewbUGKMBFHA.1292@.TK2MSFTNGP10.phx.gbl...
> Sorry to be such a pain Allan, but now Im really lost. Do you know if the
> version gets updated when stored this way?
>
> "Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
> news:ukprc3LBFHA.1564@.TK2MSFTNGP09.phx.gbl...
> and
> I
> If
> version?
>
change the Packages, which version will be run the following night? If its
the old one, how to I update the schedule to recognize the new version?
SQL2K SP3
TIA, ChrisR
If you do not specify the version # then it is always the latest
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"ChrisR" <bla@.noemail.com> wrote in message
news:Oypg1xKBFHA.2792@.TK2MSFTNGP15.phx.gbl...
>I have several DTS Packages that are scheduled to run every night. If I
> change the Packages, which version will be run the following night? If its
> the old one, how to I update the schedule to recognize the new version?
> --
> SQL2K SP3
> TIA, ChrisR
>
|||Thanks Allen. Im still a bit in the dark though?
Is the version cotained in this type of deal?
DTSRun /~Z0x9F8F7D0B93BlaBlaBla
Is it updated when a new version is added?
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:eZh24$KBFHA.2788@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> If you do not specify the version # then it is always the latest
> --
>
> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> www.SQLDTS.com - The site for all your DTS needs.
> www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
> www.konesans.com - Consultancy from the people who know
>
> "ChrisR" <bla@.noemail.com> wrote in message
> news:Oypg1xKBFHA.2792@.TK2MSFTNGP15.phx.gbl...
its
>
|||yuck.
This will wrap version up for you and you cannoot change it unless you
regenerate the string (DTSRUNUI). Personally I prefer to use the DTSRUN and
the non-encrypted versions.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"ChrisR" <bla@.noemail.com> wrote in message
news:%23QnYYxLBFHA.2112@.TK2MSFTNGP14.phx.gbl...
> Thanks Allen. Im still a bit in the dark though?
> Is the version cotained in this type of deal?
> DTSRun /~Z0x9F8F7D0B93BlaBlaBla
> Is it updated when a new version is added?
>
> "Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
> news:eZh24$KBFHA.2788@.TK2MSFTNGP15.phx.gbl...
> its
>
|||Sorry to be such a pain Allan, but now Im really lost. Do you know if the
version gets updated when stored this way?
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:ukprc3LBFHA.1564@.TK2MSFTNGP09.phx.gbl...
> yuck.
> This will wrap version up for you and you cannoot change it unless you
> regenerate the string (DTSRUNUI). Personally I prefer to use the DTSRUN
and[vbcol=seagreen]
> the non-encrypted versions.
>
> --
>
> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> www.SQLDTS.com - The site for all your DTS needs.
> www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
> www.konesans.com - Consultancy from the people who know
>
> "ChrisR" <bla@.noemail.com> wrote in message
> news:%23QnYYxLBFHA.2112@.TK2MSFTNGP14.phx.gbl...
I[vbcol=seagreen]
If[vbcol=seagreen]
version?
>
|||No it does not.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"ChrisR" <bla@.noemail.com> wrote in message
news:ewbUGKMBFHA.1292@.TK2MSFTNGP10.phx.gbl...
> Sorry to be such a pain Allan, but now Im really lost. Do you know if the
> version gets updated when stored this way?
>
> "Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
> news:ukprc3LBFHA.1564@.TK2MSFTNGP09.phx.gbl...
> and
> I
> If
> version?
>
Subscribe to:
Posts (Atom)