By-Passing Jobs?

Hi all,
Has anyone heard of a problem like this?
I’m using ‘Start job’ facility (right clinking in jobs in server enterprise) however for some reason the program keeps by passing all but the last ‘CmdExec’ that were built. I cannot see why that is – has anyone come across before?
I’m using SQL server 2000.
Thanks
Sam
You mean, it is not executing all the job steps? Have you checked the 'On
success/failure flow' in the 'Advanced' tab of the job step properties
dialog box?
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:7214D381-3109-44F1-BB75-D2014FC3E671@.microsoft.com...
Hi all,
Has anyone heard of a problem like this?
I'm using 'Start job' facility (right clinking in jobs in server enterprise)
however for some reason the program keeps by passing all but the last
'CmdExec' that were built. I cannot see why that is - has anyone come across
before?
I'm using SQL server 2000.
Thanks
Sam
|||Thanks - these have not changed. I have also rebooted the server. It’s still bypassing all the command lines. They work fine if I fire them using start-run on the server itself. But will not run from the Management Interface in Ent manager?
Most grateful for any other ideas?
"Narayana Vyas Kondreddi" wrote:

> You mean, it is not executing all the job steps? Have you checked the 'On
> success/failure flow' in the 'Advanced' tab of the job step properties
> dialog box?
> --
> HTH,
> Vyas, MVP (SQL Server)
> http://vyaskn.tripod.com/
> Is .NET important for a database professional?
> http://vyaskn.tripod.com/poll.htm
>
> "Sam" <Sam@.discussions.microsoft.com> wrote in message
> news:7214D381-3109-44F1-BB75-D2014FC3E671@.microsoft.com...
> Hi all,
> Has anyone heard of a problem like this?
> I'm using 'Start job' facility (right clinking in jobs in server enterprise)
> however for some reason the program keeps by passing all but the last
> 'CmdExec' that were built. I cannot see why that is - has anyone come across
> before?
> I'm using SQL server 2000.
> Thanks
> Sam
>
>
|||You might want to use Profiler to see if these steps are being called at
all?
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:E6C511C6-9AA9-4E21-B38B-0C9117E42D21@.microsoft.com...
Thanks - these have not changed. I have also rebooted the server. It's still
bypassing all the command lines. They work fine if I fire them using
start-run on the server itself. But will not run from the Management
Interface in Ent manager?
Most grateful for any other ideas?
"Narayana Vyas Kondreddi" wrote:

> You mean, it is not executing all the job steps? Have you checked the 'On
> success/failure flow' in the 'Advanced' tab of the job step properties
> dialog box?
> --
> HTH,
> Vyas, MVP (SQL Server)
> http://vyaskn.tripod.com/
> Is .NET important for a database professional?
> http://vyaskn.tripod.com/poll.htm
>
> "Sam" <Sam@.discussions.microsoft.com> wrote in message
> news:7214D381-3109-44F1-BB75-D2014FC3E671@.microsoft.com...
> Hi all,
> Has anyone heard of a problem like this?
> I'm using 'Start job' facility (right clinking in jobs in server
enterprise)
> however for some reason the program keeps by passing all but the last
> 'CmdExec' that were built. I cannot see why that is - has anyone come
across
> before?
> I'm using SQL server 2000.
> Thanks
> Sam
>
>