Showing posts with label shceduled. Show all posts
Showing posts with label shceduled. Show all posts

Monday, March 12, 2012

Job Fails when scheduled

Another user who has sa privledges created a job to run an update on a table
.
I modifed it for him. Then I shceduled it. I or he can run it manaully and i
t
works fine, but when scheduled, it bombs everytime. HELPHope this article might be of some help
http://support.microsoft.com/defaul...;283811&sd=tech
"DBA" wrote:

> Another user who has sa privledges created a job to run an update on a tab
le.
> I modifed it for him. Then I shceduled it. I or he can run it manaully and
it
> works fine, but when scheduled, it bombs everytime. HELP

Job Failing if shceduled from DTS

Hi,
I have an .exe executed from DTS and it is running successfully but when I
schedule a job for the DTS it fails."Detail Records: Error: -214722033
0
(80040496); Provider Error: 0 (0) Error string: CreateProcessTask
'DTSTask_DTSCreateProcessTask_1': Process returned code -532459699, which
does not match the specified Succ... Process Exit Code 1. The step failed.
"
Can anyone please help me?
Thanks.
Riz"Riz" <Riz@.discussions.microsoft.com> wrote in message
news:8032F201-CA6F-42C7-97B4-38F99003331E@.microsoft.com...
> Hi,
> I have an .exe executed from DTS and it is running successfully but when I
> schedule a job for the DTS it fails."Detail Records:
Error: -2147220330
> (80040496); Provider Error: 0 (0) Error string: CreateProcessTask
> 'DTSTask_DTSCreateProcessTask_1': Process returned code -532459699, which
> does not match the specified Succ... Process Exit Code 1. The step
failed."
When you run the job it is running under your permissions, when the SQL
Agent runs a scheduled job it runs under the Agent's permissions.
Most likely the agent does not have access to a resource such as the Network
or a particular share. Or, you need to use the full path in the DTS.
Try the Following:
1. Check in Services to see what account the SQL Server Agent is logging in
as.
If it is logging in to local machine it does not have access to any network
resources.
2. Make sure the executable, including any necessary data files, is
available to the SQL Server Agent account.
3. Use UNC Paths (\\CompName\ShareName\) to avoid drive mapping issues.
Good Luck,
Jim