Scheduling Tasks

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

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

Scheduling Tasks

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

Scheduling Tasks

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

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

Scheduling 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

Scheduling an SSIS package that invokes a web service

Hey,

I have an SSIS package that invokes a web service and then updates a table. It runs fine as long as I am running it on the local machine. However, as soon as I save this package to the sql server, and try to schedule this as a job, it starts to fail. Now, the web service writes to an xml file and also uses an xsd and and an xsl file. When I save a dts package to the sql server, whats the proper way of referencing these files? I think this probably is what is making the package to fail, ut I am not sure.

Any help is greatly appreciated!!

Thanks!

You should use a configuration (right-click in the package and choose configurations) to set the ConnectionString property of the connection managers for the files. Or you could use expressions to set the connection strings (paths and filenames) based on variables. The variables can be set at runtime using the /SET option of DTEXEC.|||Also make sure you've configured SSIS logging, so you can find out why the package fails now or (once you fix the problem and go to production) if something goes wrong with scheduled package in production.|||That depends on where you want to keep them. I prefer to keep them in files on the disk. If your package is in SQL and you prefer to avoid the disk entirely, you can keep them in the database and just load them into variables via the Execute SQL task. The XML task and the XML Source component support receiving the XSD/XSLT from variables.
|||Thanks a lot for the suggestions. I will try them out and see how it works.|||

Hey,

Sorry for this delayed reply. Since I posted this question a lot of issues cropped up with my SQL server which eventually led to a total reinstallation of all apps on my pc. Anyway, I discovered that the problem I have been having was because of permission issues. I was able to fix that problem and just when I thought that I had everything going, I came across a new problem. After I save the SSIS package in sql server and create a job, the job starts failing. This is the error that I am getting:

-1073548540,0x,An error occurred with the following error message: "Microsoft.SqlServer.Dts.Tasks.WebServiceTask.WebserviceTaskException: The Web Service threw an error during method execution. The error is: Unable to connect to the remote server.

Any suggestions would be very helpful.

Thanks!

|||Could it be a authentication issue? Is there any security on the web service?|||

Guys!!Thanks a lot for all the suggestions. Really appreciate your help. Problem was a combination of many issues. One was related to 32bit/64bit differences, the other was authentication, and finally some syntax problems when invoking the web service. Seems it is working really well now.

Thanks again!

Scheduling a SSIS Package using SQL Agent (passing credentials)

Hi:

I created a fairly simple SSIS package to move data from a remote server which uses SQL Server Authentication to a local server that uses Windows Authentication. Everything works fine when executing the package within BI studio and if I execute the package by connecting to SSIS. If I schedule it as a SQL Server Agent Job, however, the non-integrated security fails unless I manually edit the connection to include the password. Obviously this is insecure because it is in plain text. What can I do?

Thanks.

You might need to change the encryption protection of your package (i.e. encrypt sensitive w/ user key, encrypt sensitive w/ password, etc) as well as setting up your proxy / credentials correctly.

Check out these MS article...

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

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

There are also many threads discussing these topics, including:

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

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

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

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

|||

Thanks for your response.

First of all, I did try the encrypt sensitive w / password (the default is w / user key) and I put a password in, saved the package to SQL Server and re-setup the job. It prompted me for passwords as I was setting the job up, but it didn't help at all with the remote connection. Do I need to put my connection information into the command line (user and password) AND encrypt with the password to keep others from seeing the username and password. So far I've just done one or the other.

I also tried the proxy credentials thing, but I am not so sure I understood exactly how it works. Specifically, it was prompting for an AD account, which doesn't help me in the non-integrated (SQL) login environment.

|||

RM,

You have multiple choices, but before choosing one you have to understand the pros and cons of each one. Using Package protection level equal to DonSaveSensitive plus using package configurations is a popular method that works well. You have more details in the method 4 described in one of the KB articles that EWisdahl pointed out( http://support.microsoft.com/?kbid=918760)

Search by package configurations and you will find plenty of options and examples

|||

Interestingly enough,

When I went back into the SQL Agent Job and clicked on command line (where I had added the credentials before) it defaulted back to the original command line. If this is the case, no problem, because the password I typed is hidden, right? Of course, now when I click on the data sources tab I get an error that states my connection string is invalid and it shows no data sources, either? Is the behavior somehow interrelated? The job seems to be running fine, though!?!

Scheduling a job under SA

I've shceduled a job under sa account (I've changed the password
though),this job access local folder of the box running SQL server.I have
added sa to the sysadmin role and it dose have access to the local folder
..How is it possible as *sa* is a sql server account and how it has the
enough permissions to access local file system?
Thanks a lot
If the job is owned by a sysadmin, it's operating under the
security context of the service account for SQL Agent.
-Sue
On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
wrote:

>I've shceduled a job under sa account (I've changed the password
>though),this job access local folder of the box running SQL server.I have
>added sa to the sysadmin role and it dose have access to the local folder
>.How is it possible as *sa* is a sql server account and how it has the
>enough permissions to access local file system?
>Thanks a lot
>
|||Thanks a lot
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:e36gf11g82of53tigjia7dqobotkfvp5pt@.4ax.com...
> If the job is owned by a sysadmin, it's operating under the
> security context of the service account for SQL Agent.
> -Sue
> On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
> wrote:
>

Scheduling a job under SA

I've shceduled a job under sa account (I've changed the password
though),this job access local folder of the box running SQL server.I have
added sa to the sysadmin role and it dose have access to the local folder
.How is it possible as *sa* is a sql server account and how it has the
enough permissions to access local file system?
Thanks a lotIf the job is owned by a sysadmin, it's operating under the
security context of the service account for SQL Agent.
-Sue
On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
wrote:

>I've shceduled a job under sa account (I've changed the password
>though),this job access local folder of the box running SQL server.I have
>added sa to the sysadmin role and it dose have access to the local folder
>.How is it possible as *sa* is a sql server account and how it has the
>enough permissions to access local file system?
>Thanks a lot
>|||Thanks a lot
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:e36gf11g82of53tigjia7dqobotkfvp5pt@.
4ax.com...
> If the job is owned by a sysadmin, it's operating under the
> security context of the service account for SQL Agent.
> -Sue
> On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
> wrote:
>
>

Scheduling a job under SA

I've shceduled a job under sa account (I've changed the password
though:)),this job access local folder of the box running SQL server.I have
added sa to the sysadmin role and it dose have access to the local folder
.How is it possible as *sa* is a sql server account and how it has the
enough permissions to access local file system?
Thanks a lotIf the job is owned by a sysadmin, it's operating under the
security context of the service account for SQL Agent.
-Sue
On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
wrote:
>I've shceduled a job under sa account (I've changed the password
>though:)),this job access local folder of the box running SQL server.I have
>added sa to the sysadmin role and it dose have access to the local folder
>.How is it possible as *sa* is a sql server account and how it has the
>enough permissions to access local file system?
>Thanks a lot
>|||Thanks a lot
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:e36gf11g82of53tigjia7dqobotkfvp5pt@.4ax.com...
> If the job is owned by a sysadmin, it's operating under the
> security context of the service account for SQL Agent.
> -Sue
> On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
> wrote:
>>I've shceduled a job under sa account (I've changed the password
>>though:)),this job access local folder of the box running SQL server.I
>>have
>>added sa to the sysadmin role and it dose have access to the local folder
>>.How is it possible as *sa* is a sql server account and how it has the
>>enough permissions to access local file system?
>>Thanks a lot
>sql

Scheduled package problem: Class not registered

Hi,

Attempting to schedule and execute a package. The server is a 64bit clustered sql 2005 server.

The package was developed on my local install of sql 2005 client tools. I can run the package within BIDS, I can export and run the package from MSDB, but I cannot get it to execute without failure when scheduled.

I suspect it is some weirdness caused by the difference between 32 bit and 64 bit type program, but do not know what to do to figure it out.

Job history output below:

Date 14/09/2007 1:07:30 PM
Log Job History (SISS)

Step ID 1
Server servername

Job Name SSIS test job
Step Name Import NE Outpat
Duration 00:00:02
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: HAHS\billsqlserver. ...9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:07:30 PM Progress: 2007-09-14 13:07:31.54 Source: Clinics Validating: 0% complete End Progress Progress: 2007-09-14 13:07:31.54 Source: Clinics Validating: 33% complete End Progress Progress: 2007-09-14 13:07:31.75 Source: Clinics Validating: 66% complete End Progress Error: 2007-09-14 13:07:31.89 Code: 0xC0202009 Source: ImportNewEnglandOutpatientData Connection manager "Clinics" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2007-09-14 13:07:31.89 Code: 0xC020801C Source: Clinics Clinics Access Database [15] Description: SSIS Error Code DTS_E_CANNOTACQ... The package execution fa... The step failed.

Thanks for all suggestions,

Does the package run when executed from SQL Management Studio on the server itself?|||

Hi,

Not sure.....

Been doing some further reading, and found:

"Noted that the Microsoft OLE DB Provider for Jet, used for Access and Excel databases, is not available in a 64-bit version."

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

The package has 4 MS access as datasources and imports the data into 2005.

Is this possible? is there another way around this?

|||

Well it sounds to me like you are on the right track.

Someone else will ahve to answer the 64bit question. I have no experience with using Access on a 64 bit install (thank god!)

|||

You cannot run this package in 64-bit mode as there is no 64-bit JET provider. Use the 32-bit dtexec when scheduling your jobs.

Thanks,

Bob

sql

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
>

Scheduled Job works when run manually but not when scheduled

Hi
I have a very simple local package, which performs the following:
1. Execute SQL Task
Delete from PURCHASE_LEDGER
Delete from SALES_LEDGER
2. Transform Data task
Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
There is a workflow between steps 1 and 2, so that step 2 only
executes if step 1 is successfull.
The connection to SAGE is ODBC (which I know works fine) and to SQL it
is OLE.
This package works perfectly if I right click on it and select
execute. However, if I schedule it, the first step works perfectly but
the second step fails. I know that the first step works because the
tables are empty. If I remove the first step and the workflow from the
package, the transform data task still does not work when scheduled,
but is fine when I run it manually. In the error log, it just says:
"SQL Server Scheduled Job 'Update SAGE
Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
was invoked by Schedule 6 (Update SAGE Tables). The last step to run
was step 1 (Update SAGE Tables)."
Any idea why this package should work manually but not when scheduled?
Thanks
Colin
Check the following knowledge base article for information
on troubleshooting this issue:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
-Sue
On 30 Mar 2007 03:11:12 -0700, "Bobby"
<bobby2@.blueyonder.co.uk> wrote:

>Hi
>I have a very simple local package, which performs the following:
>1. Execute SQL Task
> Delete from PURCHASE_LEDGER
> Delete from SALES_LEDGER
>2. Transform Data task
> Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
> Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
>There is a workflow between steps 1 and 2, so that step 2 only
>executes if step 1 is successfull.
>The connection to SAGE is ODBC (which I know works fine) and to SQL it
>is OLE.
>This package works perfectly if I right click on it and select
>execute. However, if I schedule it, the first step works perfectly but
>the second step fails. I know that the first step works because the
>tables are empty. If I remove the first step and the workflow from the
>package, the transform data task still does not work when scheduled,
>but is fine when I run it manually. In the error log, it just says:
>"SQL Server Scheduled Job 'Update SAGE
>Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
>Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
>was invoked by Schedule 6 (Update SAGE Tables). The last step to run
>was step 1 (Update SAGE Tables)."
>Any idea why this package should work manually but not when scheduled?
>Thanks
>Colin
|||On 30 Mar, 12:52, Sue Hoegemeier <S...@.nomail.please> wrote:
> Check the following knowledge base article for information
> on troubleshooting this issue:
> INF: How to Run a DTS Package as a Scheduled Jobhttp://support.microsoft.com/?id=269074
> -Sue
Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
It's set up on my p/c, which is why it works manually, but when it's
scheduled it runs from the server and can't find the link to SAGE.
Thanks
Colin
|||> Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
> It's set up on my p/c, which is why it works manually, but when it's
> scheduled it runs from the server and can't find the link to SAGE.
>
Hmmm... Not quite as simple as I thought. Anybody know how to install
the SAGE ODBC driver without installing the whole software package?
Colin
|||On 30 Mar, 13:58, "Bobby" <bob...@.blueyonder.co.uk> wrote:
> Hmmm... Not quite as simple as I thought. Anybody know how to install
> the SAGE ODBC driver without installing the whole software package?
> Colin
Ok, forget it - I've worked it out
Colin

Scheduled Job works when run manually but not when scheduled

Hi
I have a very simple local package, which performs the following:
1. Execute SQL Task
Delete from PURCHASE_LEDGER
Delete from SALES_LEDGER
2. Transform Data task
Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
There is a workflow between steps 1 and 2, so that step 2 only
executes if step 1 is successfull.
The connection to SAGE is ODBC (which I know works fine) and to SQL it
is OLE.
This package works perfectly if I right click on it and select
execute. However, if I schedule it, the first step works perfectly but
the second step fails. I know that the first step works because the
tables are empty. If I remove the first step and the workflow from the
package, the transform data task still does not work when scheduled,
but is fine when I run it manually. In the error log, it just says:
"SQL Server Scheduled Job 'Update SAGE
Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
was invoked by Schedule 6 (Update SAGE Tables). The last step to run
was step 1 (Update SAGE Tables)."
Any idea why this package should work manually but not when scheduled?
Thanks
ColinHi Colin,
Are the accounts you use to 1) execut the package manually and 2) the
account that runs it via a schedule, the same account?
Without digging too deeply to me it sounds like the account that is used for
the scheduled job, isnt the same as the one where you execute it manually.
Barry
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1175249472.172771.158350@.y80g2000hsf.googlegroups.com...
> Hi
> I have a very simple local package, which performs the following:
> 1. Execute SQL Task
> Delete from PURCHASE_LEDGER
> Delete from SALES_LEDGER
> 2. Transform Data task
> Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
> Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
> There is a workflow between steps 1 and 2, so that step 2 only
> executes if step 1 is successfull.
> The connection to SAGE is ODBC (which I know works fine) and to SQL it
> is OLE.
> This package works perfectly if I right click on it and select
> execute. However, if I schedule it, the first step works perfectly but
> the second step fails. I know that the first step works because the
> tables are empty. If I remove the first step and the workflow from the
> package, the transform data task still does not work when scheduled,
> but is fine when I run it manually. In the error log, it just says:
> "SQL Server Scheduled Job 'Update SAGE
> Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
> Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
> was invoked by Schedule 6 (Update SAGE Tables). The last step to run
> was step 1 (Update SAGE Tables)."
> Any idea why this package should work manually but not when scheduled?
> Thanks
> Colin
>|||Check the following knowledge base article for information
on troubleshooting this issue:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
-Sue
On 30 Mar 2007 03:11:12 -0700, "Bobby"
<bobby2@.blueyonder.co.uk> wrote:
>Hi
>I have a very simple local package, which performs the following:
>1. Execute SQL Task
> Delete from PURCHASE_LEDGER
> Delete from SALES_LEDGER
>2. Transform Data task
> Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
> Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
>There is a workflow between steps 1 and 2, so that step 2 only
>executes if step 1 is successfull.
>The connection to SAGE is ODBC (which I know works fine) and to SQL it
>is OLE.
>This package works perfectly if I right click on it and select
>execute. However, if I schedule it, the first step works perfectly but
>the second step fails. I know that the first step works because the
>tables are empty. If I remove the first step and the workflow from the
>package, the transform data task still does not work when scheduled,
>but is fine when I run it manually. In the error log, it just says:
>"SQL Server Scheduled Job 'Update SAGE
>Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
>Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
>was invoked by Schedule 6 (Update SAGE Tables). The last step to run
>was step 1 (Update SAGE Tables)."
>Any idea why this package should work manually but not when scheduled?
>Thanks
>Colin|||On 30 Mar, 12:52, Sue Hoegemeier <S...@.nomail.please> wrote:
> Check the following knowledge base article for information
> on troubleshooting this issue:
> INF: How to Run a DTS Package as a Scheduled Jobhttp://support.microsoft.com/?id=269074
> -Sue
Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
It's set up on my p/c, which is why it works manually, but when it's
scheduled it runs from the server and can't find the link to SAGE.
Thanks
Colin|||> Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
> It's set up on my p/c, which is why it works manually, but when it's
> scheduled it runs from the server and can't find the link to SAGE.
>
Hmmm... Not quite as simple as I thought. Anybody know how to install
the SAGE ODBC driver without installing the whole software package?
Colin|||On 30 Mar, 13:58, "Bobby" <bob...@.blueyonder.co.uk> wrote:
> > Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
> > It's set up on my p/c, which is why it works manually, but when it's
> > scheduled it runs from the server and can't find the link to SAGE.
> Hmmm... Not quite as simple as I thought. Anybody know how to install
> the SAGE ODBC driver without installing the whole software package?
> Colin
Ok, forget it - I've worked it out
Colin

Scheduled Job works when run manually but not when scheduled

Hi
I have a very simple local package, which performs the following:
1. Execute SQL Task
Delete from PURCHASE_LEDGER
Delete from SALES_LEDGER
2. Transform Data task
Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
There is a workflow between steps 1 and 2, so that step 2 only
executes if step 1 is successfull.
The connection to SAGE is ODBC (which I know works fine) and to SQL it
is OLE.
This package works perfectly if I right click on it and select
execute. However, if I schedule it, the first step works perfectly but
the second step fails. I know that the first step works because the
tables are empty. If I remove the first step and the workflow from the
package, the transform data task still does not work when scheduled,
but is fine when I run it manually. In the error log, it just says:
"SQL Server Scheduled Job 'Update SAGE
Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
was invoked by Schedule 6 (Update SAGE Tables). The last step to run
was step 1 (Update SAGE Tables)."
Any idea why this package should work manually but not when scheduled?
Thanks
ColinHi Colin,
Are the accounts you use to 1) execut the package manually and 2) the
account that runs it via a schedule, the same account?
Without digging too deeply to me it sounds like the account that is used for
the scheduled job, isnt the same as the one where you execute it manually.
Barry
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1175249472.172771.158350@.y80g2000hsf.googlegroups.com...
> Hi
> I have a very simple local package, which performs the following:
> 1. Execute SQL Task
> Delete from PURCHASE_LEDGER
> Delete from SALES_LEDGER
> 2. Transform Data task
> Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
> Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
> There is a workflow between steps 1 and 2, so that step 2 only
> executes if step 1 is successfull.
> The connection to SAGE is ODBC (which I know works fine) and to SQL it
> is OLE.
> This package works perfectly if I right click on it and select
> execute. However, if I schedule it, the first step works perfectly but
> the second step fails. I know that the first step works because the
> tables are empty. If I remove the first step and the workflow from the
> package, the transform data task still does not work when scheduled,
> but is fine when I run it manually. In the error log, it just says:
> "SQL Server Scheduled Job 'Update SAGE
> Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
> Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
> was invoked by Schedule 6 (Update SAGE Tables). The last step to run
> was step 1 (Update SAGE Tables)."
> Any idea why this package should work manually but not when scheduled?
> Thanks
> Colin
>|||Check the following knowledge base article for information
on troubleshooting this issue:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
-Sue
On 30 Mar 2007 03:11:12 -0700, "Bobby"
<bobby2@.blueyonder.co.uk> wrote:

>Hi
>I have a very simple local package, which performs the following:
>1. Execute SQL Task
> Delete from PURCHASE_LEDGER
> Delete from SALES_LEDGER
>2. Transform Data task
> Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
> Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
>There is a workflow between steps 1 and 2, so that step 2 only
>executes if step 1 is successfull.
>The connection to SAGE is ODBC (which I know works fine) and to SQL it
>is OLE.
>This package works perfectly if I right click on it and select
>execute. However, if I schedule it, the first step works perfectly but
>the second step fails. I know that the first step works because the
>tables are empty. If I remove the first step and the workflow from the
>package, the transform data task still does not work when scheduled,
>but is fine when I run it manually. In the error log, it just says:
>"SQL Server Scheduled Job 'Update SAGE
>Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
>Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
>was invoked by Schedule 6 (Update SAGE Tables). The last step to run
>was step 1 (Update SAGE Tables)."
>Any idea why this package should work manually but not when scheduled?
>Thanks
>Colin|||On 30 Mar, 12:52, Sue Hoegemeier <S...@.nomail.please> wrote:
> Check the following knowledge base article for information
> on troubleshooting this issue:
> INF: How to Run a DTS Package as a Scheduled Jobhttp://support.microsoft.c
om/?id=269074
> -Sue
Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
It's set up on my p/c, which is why it works manually, but when it's
scheduled it runs from the server and can't find the link to SAGE.
Thanks
Colin|||> Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
> It's set up on my p/c, which is why it works manually, but when it's
> scheduled it runs from the server and can't find the link to SAGE.
>
Hmmm... Not quite as simple as I thought. Anybody know how to install
the SAGE ODBC driver without installing the whole software package?
Colin|||On 30 Mar, 13:58, "Bobby" <bob...@.blueyonder.co.uk> wrote:
> Hmmm... Not quite as simple as I thought. Anybody know how to install
> the SAGE ODBC driver without installing the whole software package?
> Colin
Ok, forget it - I've worked it out
Colin

Scheduled Job

Hi ,
I created a batch only to transfer the files from local server to share
folder on another server. I put the batch in the DTS package and scheduled it.
When I trace the job , the file have been copied but the "Status" of the
job still stick on "Executing Step 1 ..." and it no turn to success although
the file had been copied. What's wrong with that actually ?
Thanks ,
Travis
--
Travis TanHi ,
why u are making ur work complex .
U can transfer the files using file tranfer protocol task in DTC
package.
When the batch finishes tanfer sqlserver doesnt come to know the status
and it shows executing status.
from
Doller
Travis wrote:
> Hi ,
> I created a batch only to transfer the files from local server to share
> folder on another server. I put the batch in the DTS package and scheduled it.
> When I trace the job , the file have been copied but the "Status" of the
> job still stick on "Executing Step 1 ..." and it no turn to success although
> the file had been copied. What's wrong with that actually ?
> Thanks ,
> Travis
> --
> Travis Tan|||Travis wrote:
> Hi ,
> I created a batch only to transfer the files from local server to share
> folder on another server. I put the batch in the DTS package and scheduled it.
> When I trace the job , the file have been copied but the "Status" of the
> job still stick on "Executing Step 1 ..." and it no turn to success although
> the file had been copied. What's wrong with that actually ?
> Thanks ,
> Travis
>
Are you looking at the status in Enterprise Manager? In that case you
might need to refresh it to see the actual status.
Regards
Steen|||Hi Doller ,
Thanks for your info and I understand what you said. The actually process
in DTS was
1) Transfer The Files
2) UnZip The Files
3) Restore the transaction logs
Because the Transfer Files pending in "executing" so no Unzip process is
done. Means that no way for me to resolve that ?
Thanks ,
Travis
Travis Tan
"doller" wrote:
> Hi ,
> why u are making ur work complex .
> U can transfer the files using file tranfer protocol task in DTC
> package.
> When the batch finishes tanfer sqlserver doesnt come to know the status
> and it shows executing status.
> from
> Doller
>
> Travis wrote:
> > Hi ,
> >
> > I created a batch only to transfer the files from local server to share
> > folder on another server. I put the batch in the DTS package and scheduled it.
> >
> > When I trace the job , the file have been copied but the "Status" of the
> > job still stick on "Executing Step 1 ..." and it no turn to success although
> > the file had been copied. What's wrong with that actually ?
> >
> > Thanks ,
> > Travis
> >
> > --
> > Travis Tan
>

Scheduled Job

Hi ,
I created a batch only to transfer the files from local server to share
folder on another server. I put the batch in the DTS package and scheduled i
t.
When I trace the job , the file have been copied but the "Status" of the
job still stick on "Executing Step 1 ..." and it no turn to success althoug
h
the file had been copied. What's wrong with that actually ?
Thanks ,
Travis
Travis TanHi ,
why u are making ur work complex .
U can transfer the files using file tranfer protocol task in DTC
package.
When the batch finishes tanfer sqlserver doesnt come to know the status
and it shows executing status.
from
Doller
Travis wrote:
> Hi ,
> I created a batch only to transfer the files from local server to share
> folder on another server. I put the batch in the DTS package and scheduled
it.
> When I trace the job , the file have been copied but the "Status" of the
> job still stick on "Executing Step 1 ..." and it no turn to success altho
ugh
> the file had been copied. What's wrong with that actually ?
> Thanks ,
> Travis
> --
> Travis Tan|||Travis wrote:
> Hi ,
> I created a batch only to transfer the files from local server to share
> folder on another server. I put the batch in the DTS package and scheduled
it.
> When I trace the job , the file have been copied but the "Status" of the
> job still stick on "Executing Step 1 ..." and it no turn to success altho
ugh
> the file had been copied. What's wrong with that actually ?
> Thanks ,
> Travis
>
Are you looking at the status in Enterprise Manager? In that case you
might need to refresh it to see the actual status.
Regards
Steen|||Hi Doller ,
Thanks for your info and I understand what you said. The actually process
in DTS was
1) Transfer The Files
2) UnZip The Files
3) Restore the transaction logs
Because the Transfer Files pending in "executing" so no Unzip process is
done. Means that no way for me to resolve that ?
Thanks ,
Travis
Travis Tan
"doller" wrote:

> Hi ,
> why u are making ur work complex .
> U can transfer the files using file tranfer protocol task in DTC
> package.
> When the batch finishes tanfer sqlserver doesnt come to know the status
> and it shows executing status.
> from
> Doller
>
> Travis wrote:
>

Scheduled DTS not running

I created a DTS Local Package that should run on a specified time (ex. 9:00 AM) using EnterPrise Manager on my PC.

It is basically copying a file from our AS400 to the SQL server. It works fine if you execute it but the scheduler does not run at the specified time.

Am I missing anything here?

TIFOriginally posted by ARPRINCE
I created a DTS Local Package that should run on a specified time (ex. 9:00 AM) using EnterPrise Manager on my PC.

It is basically copying a file from our AS400 to the SQL server. It works fine if you execute it but the scheduler does not run at the specified time.

Am I missing anything here?

TIF

chk if SQL Agent is started|||Yup. The Agent is running. When I checked the jobs, I see an "X" on the DTS job I created and says that it failed. However, I can't see a log that gives me the exact reason why it failed.|||Check your Agent service account has permission on AS 400 server!|||When I configured my DTS, I entered the AS400 user credentials so I figured this is enough since when I execute my DTS, in works just fine. It's only when I use the schedule that it doesn't work.

How do you check anagent service account permission on a AS400? Sorry, I'm relatively new using this DTS thing.

Thanks|||can you just check sql agent error, see what it says!!
Agent right-click--Display error log.|||Don't forget that when you interactivly run a DTS package, it runs under your credentials. When SQLAgent runs it, it runs with the permissions given to SQLAgent. Maybe you have permissions to access the AS400 but SQLAgent does not??|||Originally posted by tomh53
Don't forget that when you interactivly run a DTS package, it runs under your credentials. When SQLAgent runs it, it runs with the permissions given to SQLAgent. Maybe you have permissions to access the AS400 but SQLAgent does not??

I see the error log but it does not show my any logs for yesterday and today. As a matter of fact, the last log date is 2/15/2004.|||Probably Agent configured to clear all jobhistory logs..
In anycase as tom said, look into SQLAgent service account has permission to connect AS400. When you run it manually it takes your credentials..when it runs under SqlAgent it looks for SqlAgent service account.|||Thanks for the TIPs. I will look into it more thoroughly.

Scheduled DB Backup Never Executed, Why? Why?

Howdy folks,
I am running win 2000 server + SP3 and SQL Server 7 with
SP3. I used Enterprise Manager to schedule weekly local
disk backup but it never executed. How do I know? I
browse throught the local disk, sql server log and could
not find any indications at all.
In Enterprise Manager->Management->Sql Server Log (no new
logs)
In Enterprise Manager->select the db->all task->backup db
1) On General Tab
Backup Portion -> DB Complete
Destinatin Portion -> Add and navigated to default
location, C:\MSSQL\BACKUP\AprilBackup.bak
Overwrite Portion -> overwrite existing media
Schedule -> recurring and entered the desinated day & hour
2) On Option Tab
I selected "Verify Backup upon completion"
I scheduled to run on Every Thursday at 4:00am but for the
past 4 weeks, no scheduled backup had ever executed.
Why? Can anyone help me, please.
Vito Corleone
President
Export & Import Oliver Oil Co.Vito,
Check if sqlagent is running.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Vito Corleone" <anonymous@.discussions.microsoft.com> wrote in message
news:13fa01c4265a$edae9410$a301280a@.phx.gbl...
> Howdy folks,
> I am running win 2000 server + SP3 and SQL Server 7 with
> SP3. I used Enterprise Manager to schedule weekly local
> disk backup but it never executed. How do I know? I
> browse throught the local disk, sql server log and could
> not find any indications at all.
> In Enterprise Manager->Management->Sql Server Log (no new
> logs)
> In Enterprise Manager->select the db->all task->backup db
> 1) On General Tab
> Backup Portion -> DB Complete
> Destinatin Portion -> Add and navigated to default
> location, C:\MSSQL\BACKUP\AprilBackup.bak
> Overwrite Portion -> overwrite existing media
> Schedule -> recurring and entered the desinated day & hour
> 2) On Option Tab
> I selected "Verify Backup upon completion"
> I scheduled to run on Every Thursday at 4:00am but for the
> past 4 weeks, no scheduled backup had ever executed.
> Why? Can anyone help me, please.
> Vito Corleone
> President
> Export & Import Oliver Oil Co.|||I'm sure you have verified this, but have you checked to make sure that the job is enabled. In EM go to Management - Sql Server Agent - Jobs. Make sure that the job in question has a yes in the enabled column.|||Hi,
As Dinesh posted.. Please check whether your "SQL Agent" service in SQL
Server machine is
running. If stopped "start" the service and verify whether the job gets
executed.
Incase if the service failed to start, go to Control Panel -- Services-- SQL
Agent Log ON window.. Re- enter the
OS user name and password (if it is not starting in Local system account).
Enter the same OS User you used to start MSSQL
Server service.This will probably solve your issue
Thanks
Hari
MCDBA
"Vito Corleone" <anonymous@.discussions.microsoft.com> wrote in message
news:13fa01c4265a$edae9410$a301280a@.phx.gbl...
> Howdy folks,
> I am running win 2000 server + SP3 and SQL Server 7 with
> SP3. I used Enterprise Manager to schedule weekly local
> disk backup but it never executed. How do I know? I
> browse throught the local disk, sql server log and could
> not find any indications at all.
> In Enterprise Manager->Management->Sql Server Log (no new
> logs)
> In Enterprise Manager->select the db->all task->backup db
> 1) On General Tab
> Backup Portion -> DB Complete
> Destinatin Portion -> Add and navigated to default
> location, C:\MSSQL\BACKUP\AprilBackup.bak
> Overwrite Portion -> overwrite existing media
> Schedule -> recurring and entered the desinated day & hour
> 2) On Option Tab
> I selected "Verify Backup upon completion"
> I scheduled to run on Every Thursday at 4:00am but for the
> past 4 weeks, no scheduled backup had ever executed.
> Why? Can anyone help me, please.
> Vito Corleone
> President
> Export & Import Oliver Oil Co.

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.

Schedule Local Package to perform FTP and DB restore

Hi,

Did anyone successfully set up a local package to first ftp a db.bak
and second perform an automated db restore?

I need to perform an automated task, which ftp nightly backup file to
another server and then restore onto a database and leave the database
in read-only mode for additional transaction logs restore during the
day.

Can someone help and provide the procedures on how to do that?

Thanks in advance."xo55ox" <xo55ox@.hotmail.com> wrote in message
news:abbcb3d7.0405101048.1ce74ed6@.posting.google.c om...
> Hi,
> Did anyone successfully set up a local package to first ftp a db.bak
> and second perform an automated db restore?
> I need to perform an automated task, which ftp nightly backup file to
> another server and then restore onto a database and leave the database
> in read-only mode for additional transaction logs restore during the
> day.
> Can someone help and provide the procedures on how to do that?
> Thanks in advance.

You don't mention your MSSQL version or edition, but you might want to check
out this article about implementing log shipping with the SQL 2000 Standard
edition using a reskit tool:

http://www.winnetmag.com/Article/Ar...3231/23231.html

Or try these links:

http://sqlguy.home.comcast.net/logship.htm
http://www.sql-server-performance.c...og_shipping.asp

If you want to use DTS, it might be easier to execute the package on the
destination (standby) server, because the DTS FTP task can only GET, not
PUT. There is an alternative implementation that will do both here, by the
way:

http://www.sqldts.com/?302

To implement a log shipping package should be straightforward:

1 - Run BACKUP DATABASE on the source server (Execute SQL task)
2 - Use an FTP task to GET the backup file on to the destination server
3 - Run RESTORE DATABASE WITH STANDBY on the target server (Execute SQL
task)

But to add error handling, logging etc. can become more complicated, so you
may want to see if one of the existing solutions is good enough for you.

Simon