Job not working in SQL server

Hi,
I have put a job with 3 steps.
But appear this message : "The job failed. The Job was
invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last step
to run was step 3 (IMPORT_DBF_TO_SQL)".
What I Can do to solve this problem'
ThanksYou need to see what Step 3 :- IMPORT_DBF_TO_SQL is trying to do.
I would imagine it executes a DTS Package, hopefully that DTS package was
designed to produce a Log output file. That Log file will give you the real
reason for the failure.
--
HTH
Ryan Waight, MCDBA, MCSE
"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
> Hi,
> I have put a job with 3 steps.
> But appear this message : "The job failed. The Job was
> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last step
> to run was step 3 (IMPORT_DBF_TO_SQL)".
> What I Can do to solve this problem'
> Thanks
>|||Hi,
But its very strange, because i have in another SQL server
the same job and it's ok!!
the steps are:
1- DeleteCurrentData -- Transact-SQL Script
2- Convert DAT to DBF -- Transact-SQL Script
3- IMPORT_DBF_TO_SQL -- Operating System Command
>--Original Message--
>You need to see what Step 3 :- IMPORT_DBF_TO_SQL is
trying to do.
>I would imagine it executes a DTS Package, hopefully that
DTS package was
>designed to produce a Log output file. That Log file will
give you the real
>reason for the failure.
>--
>HTH
>Ryan Waight, MCDBA, MCSE
>"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
>news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
>> Hi,
>> I have put a job with 3 steps.
>> But appear this message : "The job failed. The Job was
>> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last
step
>> to run was step 3 (IMPORT_DBF_TO_SQL)".
>> What I Can do to solve this problem'
>> Thanks
>>
>
>.
>|||It is impossible for us to know why it fails when all you tell us is that it fails.
Specify an output file for that jobstep and look at the messages in there. Hopefully this program
produces output from which you can determine what it wrong.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
news:084901c3b4df$9edff550$a501280a@.phx.gbl...
> Hi,
> But its very strange, because i have in another SQL server
> the same job and it's ok!!
> the steps are:
> 1- DeleteCurrentData -- Transact-SQL Script
> 2- Convert DAT to DBF -- Transact-SQL Script
> 3- IMPORT_DBF_TO_SQL -- Operating System Command
>
>
> >--Original Message--
> >You need to see what Step 3 :- IMPORT_DBF_TO_SQL is
> trying to do.
> >
> >I would imagine it executes a DTS Package, hopefully that
> DTS package was
> >designed to produce a Log output file. That Log file will
> give you the real
> >reason for the failure.
> >
> >--
> >HTH
> >Ryan Waight, MCDBA, MCSE
> >
> >"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
> >news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
> >> Hi,
> >>
> >> I have put a job with 3 steps.
> >> But appear this message : "The job failed. The Job was
> >> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last
> step
> >> to run was step 3 (IMPORT_DBF_TO_SQL)".
> >>
> >> What I Can do to solve this problem'
> >>
> >> Thanks
> >>
> >>
> >
> >
> >.
> >|||In the output file the message that appear are
"SQL Server Scheduled Job 'import-DBF_to_SQL'
(0x3CB9A4AA25D87B408BF4C3272F2F4C8B) - Status: Failed -
Invoked on: 2003-11-27 04:00:00 - Message: The job
failed. The Job was invoked by Schedule 15
(IMPORT_DBF_TO_SQL). The last step to run was step 3
(IMPORT_DBF_TO_SQL). "
>--Original Message--
>It is impossible for us to know why it fails when all you
tell us is that it fails.
>Specify an output file for that jobstep and look at the
messages in there. Hopefully this program
>produces output from which you can determine what it
wrong.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
>news:084901c3b4df$9edff550$a501280a@.phx.gbl...
>> Hi,
>> But its very strange, because i have in another SQL
server
>> the same job and it's ok!!
>> the steps are:
>> 1- DeleteCurrentData -- Transact-SQL Script
>> 2- Convert DAT to DBF -- Transact-SQL Script
>> 3- IMPORT_DBF_TO_SQL -- Operating System Command
>>
>>
>> >--Original Message--
>> >You need to see what Step 3 :- IMPORT_DBF_TO_SQL is
>> trying to do.
>> >
>> >I would imagine it executes a DTS Package, hopefully
that
>> DTS package was
>> >designed to produce a Log output file. That Log file
will
>> give you the real
>> >reason for the failure.
>> >
>> >--
>> >HTH
>> >Ryan Waight, MCDBA, MCSE
>> >
>> >"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in
message
>> >news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
>> >> Hi,
>> >>
>> >> I have put a job with 3 steps.
>> >> But appear this message : "The job failed. The Job
was
>> >> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last
>> step
>> >> to run was step 3 (IMPORT_DBF_TO_SQL)".
>> >>
>> >> What I Can do to solve this problem'
>> >>
>> >> Thanks
>> >>
>> >>
>> >
>> >
>> >.
>> >
>
>.
>|||That is not the output file. In the job *step*, right tab, you have an option to specify an output
file for the jobstep. This is where all the messages from the command are written. After executing
the job, check this file.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
news:0a2d01c3b4fb$b7513790$a501280a@.phx.gbl...
> In the output file the message that appear are
> "SQL Server Scheduled Job 'import-DBF_to_SQL'
> (0x3CB9A4AA25D87B408BF4C3272F2F4C8B) - Status: Failed -
> Invoked on: 2003-11-27 04:00:00 - Message: The job
> failed. The Job was invoked by Schedule 15
> (IMPORT_DBF_TO_SQL). The last step to run was step 3
> (IMPORT_DBF_TO_SQL). "
>
> >--Original Message--
> >It is impossible for us to know why it fails when all you
> tell us is that it fails.
> >Specify an output file for that jobstep and look at the
> messages in there. Hopefully this program
> >produces output from which you can determine what it
> wrong.
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at: http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
> >news:084901c3b4df$9edff550$a501280a@.phx.gbl...
> >> Hi,
> >>
> >> But its very strange, because i have in another SQL
> server
> >> the same job and it's ok!!
> >> the steps are:
> >> 1- DeleteCurrentData -- Transact-SQL Script
> >> 2- Convert DAT to DBF -- Transact-SQL Script
> >> 3- IMPORT_DBF_TO_SQL -- Operating System Command
> >>
> >>
> >>
> >>
> >> >--Original Message--
> >> >You need to see what Step 3 :- IMPORT_DBF_TO_SQL is
> >> trying to do.
> >> >
> >> >I would imagine it executes a DTS Package, hopefully
> that
> >> DTS package was
> >> >designed to produce a Log output file. That Log file
> will
> >> give you the real
> >> >reason for the failure.
> >> >
> >> >--
> >> >HTH
> >> >Ryan Waight, MCDBA, MCSE
> >> >
> >> >"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in
> message
> >> >news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
> >> >> Hi,
> >> >>
> >> >> I have put a job with 3 steps.
> >> >> But appear this message : "The job failed. The Job
> was
> >> >> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last
> >> step
> >> >> to run was step 3 (IMPORT_DBF_TO_SQL)".
> >> >>
> >> >> What I Can do to solve this problem'
> >> >>
> >> >> Thanks
> >> >>
> >> >>
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

job fails for sql 2005 run SSIS package

Hi, I created an SSIS package and deployed it by using the wizard that is
invoked when selecting the SSISDeploymentmanifest file. The deployment
worked as I can run the package from sql server management studio under MSDB
by right clicking and selecting excecute package, in the object explorer.
When I create a job under SQL Server agent the job is created succesfully.
It has 1 step to execute the package. When I try to run the job it fails and
the only message I get is
**************************************************
Message
The job failed. The Job was invoked by User domain\username. The last step
to run was step 1 (run package called package). I also checked the view
history and it has the same error message. I used windows authentication
when creating the step. Also when creating the step in the new job I
selected type = SQL Server Integration Package, Run as SQL Agent Service
Account, I then specified the server and selected windows authentication and
it found the package. I am running everything on one machine as I just have
the SQL2005 that comes with vs 2005.
thanks.
Paul G
Software engineer.I got it to work,it was a permissions issue that I fixed with the SQL server
configuration manager. Also had another problem where it would write out a
message box (it worked!) as part of a vb script. I had to disable this and
then rebuild /redeploy the package.
--
Paul G
Software engineer.
"Paul" wrote:
> Hi, I created an SSIS package and deployed it by using the wizard that is
> invoked when selecting the SSISDeploymentmanifest file. The deployment
> worked as I can run the package from sql server management studio under MSDB
> by right clicking and selecting excecute package, in the object explorer.
> When I create a job under SQL Server agent the job is created succesfully.
> It has 1 step to execute the package. When I try to run the job it fails and
> the only message I get is
> **************************************************
> Message
> The job failed. The Job was invoked by User domain\username. The last step
> to run was step 1 (run package called package). I also checked the view
> history and it has the same error message. I used windows authentication
> when creating the step. Also when creating the step in the new job I
> selected type = SQL Server Integration Package, Run as SQL Agent Service
> Account, I then specified the server and selected windows authentication and
> it found the package. I am running everything on one machine as I just have
> the SQL2005 that comes with vs 2005.
> thanks.
> Paul G
> Software engineer.