Re: Scheduling a simple local package won't stick
- From: Rockitman <Rockitman@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 12 Nov 2008 09:20:01 -0800
Well my domain account is the owner, and it is member of the local
administrator group on the server, so I assume that the SQL server service
account is running the job?
Where do I find out if this Sql server service account has the necessary
rights?
I do not see this account listed in Users, nor in SQL server logins.
"Russell Fields" wrote:
Rockitman,.
Now you are into the problem that I was describing to GC in this group.
1 - When you run the DTS package yourself, it runs with your credentials,
your file mappings, and so forth.
2 - When the server runs the DTS Package from SQL Agent it runs in one of
two security contexts.
(a) - The job is owned by a sysadmin account, so it runs as the SQL Server
service account.
(b) - The job is owned by a non-sysadmin account, so it runs as the SQL
Agent Proxy Account.
Likely, neither of these accounts will have your drive mapping, so using the
UNC path is better. E.g.
\\Servername\Sharename\Directory\File.Ext
Also, it may be that the two accounts doe not have rights to the folder. If
they do not, then that needs to be granted.
RLF
"Rockitman" <Rockitman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CE53C590-A123-4ACA-AAA6-CB3DD3F0378C@xxxxxxxxxxxxxxxx
Thanks for clarifying Russell.
I have viewed the job history in the SQL Server Agent and see an error
message for this package:
"Executed as user: S2K3-FRE-SQL1\SYSTEM. DTSRun: Loading... DTSRun:
Executing... DTSRun OnStart: DTSStep_DTSFTPTask_1 DTSRun OnError:
DTSStep_DTSFTPTask_1, Error = -2147220489 (800403F7) Error string:
Folder K:\Gasline Master Copy\ does not exist or is not accesible on
destination. Error source: File Transfer Protocol Task Help
file:
Help context: 0 Error Detail Records: Error: 0 (0);
Provider Error: 0 (0) Error string: Folder K:\Gasline Master Copy\
does not exist or is not accesible on destination. Error source:
File
Transfer Protocol Task Help file: Help context: 0 DTSRun
OnFinish: DTSStep_DTSFTPTask_1 DTSRun: Package execution complete.
Process Exit Code 1. The step failed."
So it appears that it doesn't like the destination folder that the FTP is
supposed to download the file to. I don't understand why though. When I
manually execute the package, it works just fine. Please advise.
"Russell Fields" wrote:
Rockitman,
DTS packages do not retain a schedule. That dialog is just to help you
create a SQL Agent job with a schedule to run the DTS package. If you
look
at the SQL Agent jobs on your server you should see one or more jobs that
you created when setting up schedules.
Look at those jobs to see their execution history, as well as any
problems
running that may have caused their failure.
RLF
"Rockitman" <Rockitman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1AA95AF3-8BEB-419F-A59A-48A28FEB95A2@xxxxxxxxxxxxxxxx
If I right click the local package I created in Enterprise Manager( a
simple
FTP download),
there
are options to Execute the package as well as Schedule the package.
When
I
select Execute package, it works fine. When I select Schedule package,
I
then set my schedule and click OK. But it never runs when scheduled.
When I
go back into Schedule package, my schedule is not there anymore either.
Just
the default schedule which states run daily every day at midnight with
no
end
date. It doesn't run there either, only when I manually execute the
package.
What gives?
- Follow-Ups:
- Re: Scheduling a simple local package won't stick
- From: Russell Fields
- Re: Scheduling a simple local package won't stick
- References:
- Scheduling a simple local package won't stick
- From: Rockitman
- Re: Scheduling a simple local package won't stick
- From: Russell Fields
- Re: Scheduling a simple local package won't stick
- From: Rockitman
- Re: Scheduling a simple local package won't stick
- From: Russell Fields
- Scheduling a simple local package won't stick
- Prev by Date: Re: Scheduling a simple local package won't stick
- Next by Date: SQL 2005 Integrated Services
- Previous by thread: Re: Scheduling a simple local package won't stick
- Next by thread: Re: Scheduling a simple local package won't stick
- Index(es):
Relevant Pages
|
