Job Steps Displayed Out of Order

When selecting to start a job manually, the job steps
appear out of order (step 3 is above steps 1 and 2 and
the like).
Any ideas what is causing this, and how to correct it?And, as I said, I don't see this and can't reproduce it. So something must
be different about *your* job, which is why I asked to see the SQL script.
We're not going to be able to guess at what's wrong unless we actually have
a script that we can use to reproduce your scenario!
"Arbiter Becker" <absql@.hotmail.com> wrote in message
news:0b7e01c356a5$12262c30$a601280a@.phx.gbl...
> Note;
> The job runs fine, if running off a schedule, and is
> displayed correctly if looking at the individual job
> steps. It is only when doing the manual start option for
> the job does it display incorrectly.
>
> >--Original Message--
> >When selecting to start a job manually, the job steps
> >appear out of order (step 3 is above steps 1 and 2 and
> >the like).
> >
> >Any ideas what is causing this, and how to correct it?
> >.
> >|||Hi Arbiter,
When you say step 3, 2, 1..., do you refer to the ID shown on Steps tab, or
the number prefix you may have added in the name of each job step?
If you click on "Move step" (up and down arrows), the ID always stays in
ascending order but the actual job steps move.
Richard
"Arbiter Becker" <absql@.hotmail.com> wrote in message
news:0da801c3569f$f4d71130$a101280a@.phx.gbl...
> When selecting to start a job manually, the job steps
> appear out of order (step 3 is above steps 1 and 2 and
> the like).
> Any ideas what is causing this, and how to correct it?

Job Status Wrong

Hello,
In my Enterprise Manager i see one job that i know its running(i look
locally on server) and jobs status appear like job is not executing(job
status is wrong)
Is there any patch to apply to EM?
Thanks and best regards.
Hi
I take it that by wrong status, you mean it is showing as sleeping under
current activity in Enterprise Manager. This is quiet normal as Sql Server
pages in and out processes as it runs them. If you keep refreshing it you may
catch it as active.
If you want to check that it is actually doing something, you can monitor it
with profiler or if you double click on the current activity, you get details
of the current SQL statement being performed. If you refresh that you should
see it change.
Hope this helps
John
"CC&JM" wrote:

> Hello,
> In my Enterprise Manager i see one job that i know its running(i look
> locally on server) and jobs status appear like job is not executing(job
> status is wrong)
> Is there any patch to apply to EM?
> Thanks and best regards.
|||Hello John,
Thanks for your answer, now i see the status of the job quit well but
yesterday i had a job that runs 4 example at 10:00 12:00 14:00 and so on..
and at 18:00 when i look at EM "Last Run Status" showed 10:00 and "Next Run
Date" showed 12:00.
I know that the problem was with my EM because in the EM of my partner i saw
the job status normally.
Thanks John,
Best regards
"John Bandettini" wrote:
[vbcol=seagreen]
> Hi
> I take it that by wrong status, you mean it is showing as sleeping under
> current activity in Enterprise Manager. This is quiet normal as Sql Server
> pages in and out processes as it runs them. If you keep refreshing it you may
> catch it as active.
> If you want to check that it is actually doing something, you can monitor it
> with profiler or if you double click on the current activity, you get details
> of the current SQL statement being performed. If you refresh that you should
> see it change.
> Hope this helps
> John
> "CC&JM" wrote:
|||Hi
I misunderstood your problem, I thought you were looking at current
activity. If you were looking at jobs and the job did not seem to be running,
did you refresh the display? Once you have opened something in Enterprise
manager, like jobs it will not automatically refresh. You need to either
right click and choose refresh or press F5.
Regards
John
"CC&JM" wrote:
[vbcol=seagreen]
> Hello John,
> Thanks for your answer, now i see the status of the job quit well but
> yesterday i had a job that runs 4 example at 10:00 12:00 14:00 and so on..
> and at 18:00 when i look at EM "Last Run Status" showed 10:00 and "Next Run
> Date" showed 12:00.
> I know that the problem was with my EM because in the EM of my partner i saw
> the job status normally.
> Thanks John,
> Best regards
> "John Bandettini" wrote:
sql

Job Status Wrong

Hello,
In my Enterprise Manager i see one job that i know its running(i look
locally on server) and jobs status appear like job is not executing(job
status is wrong)
Is there any patch to apply to EM?
Thanks and best regards.Hi
I take it that by wrong status, you mean it is showing as sleeping under
current activity in Enterprise Manager. This is quiet normal as Sql Server
pages in and out processes as it runs them. If you keep refreshing it you may
catch it as active.
If you want to check that it is actually doing something, you can monitor it
with profiler or if you double click on the current activity, you get details
of the current SQL statement being performed. If you refresh that you should
see it change.
Hope this helps
John
"CC&JM" wrote:
> Hello,
> In my Enterprise Manager i see one job that i know its running(i look
> locally on server) and jobs status appear like job is not executing(job
> status is wrong)
> Is there any patch to apply to EM?
> Thanks and best regards.|||Hello John,
Thanks for your answer, now i see the status of the job quit well but
yesterday i had a job that runs 4 example at 10:00 12:00 14:00 and so on..
and at 18:00 when i look at EM "Last Run Status" showed 10:00 and "Next Run
Date" showed 12:00.
I know that the problem was with my EM because in the EM of my partner i saw
the job status normally.
Thanks John,
Best regards
"John Bandettini" wrote:
> Hi
> I take it that by wrong status, you mean it is showing as sleeping under
> current activity in Enterprise Manager. This is quiet normal as Sql Server
> pages in and out processes as it runs them. If you keep refreshing it you may
> catch it as active.
> If you want to check that it is actually doing something, you can monitor it
> with profiler or if you double click on the current activity, you get details
> of the current SQL statement being performed. If you refresh that you should
> see it change.
> Hope this helps
> John
> "CC&JM" wrote:
> > Hello,
> >
> > In my Enterprise Manager i see one job that i know its running(i look
> > locally on server) and jobs status appear like job is not executing(job
> > status is wrong)
> > Is there any patch to apply to EM?
> >
> > Thanks and best regards.|||Hi
I misunderstood your problem, I thought you were looking at current
activity. If you were looking at jobs and the job did not seem to be running,
did you refresh the display? Once you have opened something in Enterprise
manager, like jobs it will not automatically refresh. You need to either
right click and choose refresh or press F5.
Regards
John
"CC&JM" wrote:
> Hello John,
> Thanks for your answer, now i see the status of the job quit well but
> yesterday i had a job that runs 4 example at 10:00 12:00 14:00 and so on..
> and at 18:00 when i look at EM "Last Run Status" showed 10:00 and "Next Run
> Date" showed 12:00.
> I know that the problem was with my EM because in the EM of my partner i saw
> the job status normally.
> Thanks John,
> Best regards
> "John Bandettini" wrote:
> > Hi
> >
> > I take it that by wrong status, you mean it is showing as sleeping under
> > current activity in Enterprise Manager. This is quiet normal as Sql Server
> > pages in and out processes as it runs them. If you keep refreshing it you may
> > catch it as active.
> >
> > If you want to check that it is actually doing something, you can monitor it
> > with profiler or if you double click on the current activity, you get details
> > of the current SQL statement being performed. If you refresh that you should
> > see it change.
> >
> > Hope this helps
> >
> > John
> >
> > "CC&JM" wrote:
> >
> > > Hello,
> > >
> > > In my Enterprise Manager i see one job that i know its running(i look
> > > locally on server) and jobs status appear like job is not executing(job
> > > status is wrong)
> > > Is there any patch to apply to EM?
> > >
> > > Thanks and best regards.

Job Status Wrong

Hello,
In my Enterprise Manager i see one job that i know its running(i look
locally on server) and jobs status appear like job is not executing(job
status is wrong)
Is there any patch to apply to EM?
Thanks and best regards.Hi
I take it that by wrong status, you mean it is showing as sleeping under
current activity in Enterprise Manager. This is quiet normal as Sql Server
pages in and out processes as it runs them. If you keep refreshing it you ma
y
catch it as active.
If you want to check that it is actually doing something, you can monitor it
with profiler or if you double click on the current activity, you get detail
s
of the current SQL statement being performed. If you refresh that you should
see it change.
Hope this helps
John
"CC&JM" wrote:

> Hello,
> In my Enterprise Manager i see one job that i know its running(i look
> locally on server) and jobs status appear like job is not executing(job
> status is wrong)
> Is there any patch to apply to EM?
> Thanks and best regards.|||Hello John,
Thanks for your answer, now i see the status of the job quit well but
yesterday i had a job that runs 4 example at 10:00 12:00 14:00 and so on..
and at 18:00 when i look at EM "Last Run Status" showed 10:00 and "Next Run
Date" showed 12:00.
I know that the problem was with my EM because in the EM of my partner i saw
the job status normally.
Thanks John,
Best regards
"John Bandettini" wrote:
[vbcol=seagreen]
> Hi
> I take it that by wrong status, you mean it is showing as sleeping under
> current activity in Enterprise Manager. This is quiet normal as Sql Server
> pages in and out processes as it runs them. If you keep refreshing it you
may
> catch it as active.
> If you want to check that it is actually doing something, you can monitor
it
> with profiler or if you double click on the current activity, you get deta
ils
> of the current SQL statement being performed. If you refresh that you shou
ld
> see it change.
> Hope this helps
> John
> "CC&JM" wrote:
>|||Hi
I misunderstood your problem, I thought you were looking at current
activity. If you were looking at jobs and the job did not seem to be running
,
did you refresh the display? Once you have opened something in Enterprise
manager, like jobs it will not automatically refresh. You need to either
right click and choose refresh or press F5.
Regards
John
"CC&JM" wrote:
[vbcol=seagreen]
> Hello John,
> Thanks for your answer, now i see the status of the job quit well but
> yesterday i had a job that runs 4 example at 10:00 12:00 14:00 and so on..
> and at 18:00 when i look at EM "Last Run Status" showed 10:00 and "Next Ru
n
> Date" showed 12:00.
> I know that the problem was with my EM because in the EM of my partner i s
aw
> the job status normally.
> Thanks John,
> Best regards
> "John Bandettini" wrote:
>

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
> >> >>
> >> >>
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >