non-existent step?

My package runs fine in Business Studio. When I schedule it the error log message is 'jobmanager tried to run a non-existent step (2) for job ...'

There is only the one step defined in the package schedule. Does anyone know what the problem is?

Right-click on the agent job and select "Script Job as " and select create to new query window.

Look through the resulting code and search for the phrase, "sp_add_jobstep." How many are listed?|||I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.

What could be causing this?
|||bump|||

graemeo wrote:

I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.

What could be causing this?

Have you tried recreating the job? What job type is it? (SSIS, Command, etc...)

|||Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

|||

graemeo wrote:

Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

Good to know!

non-existent step?

My package runs fine in Business Studio. When I schedule it the error log message is 'jobmanager tried to run a non-existent step (2) for job ...'

There is only the one step defined in the package schedule. Does anyone know what the problem is?

Right-click on the agent job and select "Script Job as " and select create to new query window.

Look through the resulting code and search for the phrase, "sp_add_jobstep." How many are listed?|||I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.

What could be causing this?
|||bump|||

graemeo wrote:

I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.

What could be causing this?

Have you tried recreating the job? What job type is it? (SSIS, Command, etc...)

|||Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

|||

graemeo wrote:

Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

Good to know!

non-existent step?

My package runs fine in Business Studio. When I schedule it the error log message is 'jobmanager tried to run a non-existent step (2) for job ...'

There is only the one step defined in the package schedule. Does anyone know what the problem is?

Right-click on the agent job and select "Script Job as " and select create to new query window.

Look through the resulting code and search for the phrase, "sp_add_jobstep." How many are listed?|||I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.

What could be causing this?
|||bump|||

graemeo wrote:

I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.

What could be causing this?

Have you tried recreating the job? What job type is it? (SSIS, Command, etc...)

|||Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

|||

graemeo wrote:

Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

Good to know!

non-existent step?

My package runs fine in Business Studio. When I schedule it the error log message is 'jobmanager tried to run a non-existent step (2) for job ...'

There is only the one step defined in the package schedule. Does anyone know what the problem is?

Right-click on the agent job and select "Script Job as " and select create to new query window.

Look through the resulting code and search for the phrase, "sp_add_jobstep." How many are listed?|||I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.

What could be causing this?
|||bump|||

graemeo wrote:

I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.

What could be causing this?

Have you tried recreating the job? What job type is it? (SSIS, Command, etc...)

|||Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

|||

graemeo wrote:

Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

Good to know!sql

non-existent step?

My package runs fine in Business Studio. When I schedule it the error log message is 'jobmanager tried to run a non-existent step (2) for job ...'

There is only the one step defined in the package schedule. Does anyone know what the problem is?

Right-click on the agent job and select "Script Job as " and select create to new query window.

Look through the resulting code and search for the phrase, "sp_add_jobstep." How many are listed?|||I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.

What could be causing this?
|||bump|||

graemeo wrote:

I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.

What could be causing this?

Have you tried recreating the job? What job type is it? (SSIS, Command, etc...)

|||Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

|||

graemeo wrote:

Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

Good to know!

Non-Equi Joins

I am taking Microsoft Course 4329 on Joining Data from Multiple Tables in
SQL Server 2005, and I am stumped in the Lab, Task 2, Step 3.

How can I rewrite the following SQL Statement to produce the same results by
using a non-equality operator in the join?

use adventureworks
select firstname + ' ' + lastname as name, gender, vacationhours as hours
from humanresources.employee e join person.contact c on e.contactid=c.contactid
where gender='f' and vacationhours>50
order by hours desc

Thanks in advance for your help!

--Justin--

There may be mulitple answers,

use adventureworks
select firstname + ' ' + lastname as name, gender, vacationhours as hours
from humanresources.employee e CROSS JOIN person.contact c where e.contactid=c.contactid
and gender='f' and vacationhours>50
order by hours desc

or

use adventureworks
select firstname + ' ' + lastname as name, gender, vacationhours as hours
from humanresources.employee e JOIN person.contact c On vacationhours>50 where e.contactid=c.contactid
and gender='f'
order by hours desc