Main Page | Report this Page
 
Computers Forum Index  »  Computer - Databases - MS SQL Server  »  False success in Agent Job...
Page 1 of 1    

False success in Agent Job...

Author Message
js...
Posted: Fri Oct 30, 2009 4:53 pm
Guest
I created a SSIS package that contains 6 Execute SQL Tasks and 1
Analysis Services Processing Task. I creted a nightly job that
contains only 1 step which is to execute the package. The job always
runs successfully with the following message. However, noe of the
tasks inside the job step is executed.

The job succeeded. The Job was invoked by Schedule 101 (Project Daily
Updates). The last step to run was step 1 (Project Daily Updates
Step).

When I execute the job step each morning, the tasks are then executed
successfully. I set the package ProtectionLevel property to
EncryptSensitiveWithUserKey and entered a key in PackagePassword
property. When using Importing Package into the SSIS storage, I also
sect Protection Level to "Encrypt sensitive data with user key".

Does anyone know why such a false success?
 
Erland Sommarskog...
Posted: Fri Oct 30, 2009 9:11 pm
Guest
js (androidsun at (no spam) gmail.com) writes:
Quote:
I created a SSIS package that contains 6 Execute SQL Tasks and 1
Analysis Services Processing Task. I creted a nightly job that
contains only 1 step which is to execute the package. The job always
runs successfully with the following message. However, noe of the
tasks inside the job step is executed.

The job succeeded. The Job was invoked by Schedule 101 (Project Daily
Updates). The last step to run was step 1 (Project Daily Updates
Step).

When I execute the job step each morning, the tasks are then executed
successfully. I set the package ProtectionLevel property to
EncryptSensitiveWithUserKey and entered a key in PackagePassword
property. When using Importing Package into the SSIS storage, I also
sect Protection Level to "Encrypt sensitive data with user key".

Does anyone know why such a false success?

Check under Advanced. You might have select "Quit the job reporting
success". You can also check the job step details in the job history,
to see if there is any output.

--
Erland Sommarskog, SQL Server MVP, esquel at (no spam) sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
 
js...
Posted: Fri Oct 30, 2009 11:18 pm
Guest
On Oct 30, 2:11 pm, Erland Sommarskog <esq... at (no spam) sommarskog.se> wrote:
Quote:
js (android... at (no spam) gmail.com) writes:
I created a SSIS package that contains 6 Execute SQL Tasks and 1
Analysis Services Processing Task.  I creted a nightlyjobthat
contains only 1 step which is to execute the package.  Thejobalways
runs successfully with the following message.  However, noe of the
tasks inside thejobstep is executed.

Thejobsucceeded.  TheJobwas invoked by Schedule 101 (Project Daily
Updates).  The last step to run was step 1 (Project Daily Updates
Step).

When I execute thejobstep each morning, the tasks are then executed
successfully.  I set the package ProtectionLevel property to
EncryptSensitiveWithUserKey and entered a key in PackagePassword
property.  When using Importing Package into the SSIS storage, I also
sect Protection Level to "Encrypt sensitive data with user key".

Does anyone know why such afalsesuccess?

Check under Advanced. You might have select "Quit thejobreportingsuccess".. You can also check thejobstep details in thejobhistory,
to see if there is any output.

--
Erland Sommarskog, SQL Server MVP, esq... at (no spam) sommarskog.se

Links for SQL Server Books Online:
SQL 2008:http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005:http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000:http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx- Hide quoted text -

- Show quoted text -

Thanks for the response. I tried to change the job step's "On success
action" to "Go to the next step" but the SQL Server does not allow it
because there is only one step.


The following is output of the exact job step details in the job
history:
The job succeeded. TheJobwas invoked by Schedule 101 (Project Daily
Updates). The last step to run was step 1 (Project Daily
UpdatesStep).
 
Erland Sommarskog...
Posted: Sat Oct 31, 2009 9:46 am
Guest
js (androidsun at (no spam) gmail.com) writes:
Quote:
Thanks for the response. I tried to change the job step's "On success
action" to "Go to the next step" but the SQL Server does not allow it
because there is only one step.

I'm sorry, I happened to leave out that you should check the second
dropdown, "On Failure action".

Quote:
The following is output of the exact job step details in the job
history:
The job succeeded. TheJobwas invoked by Schedule 101 (Project Daily
Updates). The last step to run was step 1 (Project Daily
UpdatesStep).

No, that is not the job-step details. That's the overall report for the job.
You need to click the squared plus icon to expand and see the job steps.


--
Erland Sommarskog, SQL Server MVP, esquel at (no spam) sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
 
 
Page 1 of 1    
All times are GMT
The time now is Sun Nov 22, 2009 8:19 am