![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, I've created a job in SQL Server 2005 with one step - call a SSIS package. The step on failure is set to quit the job reporting failure. The SSIS package has a maximum error count of 1. *Through logging built into the error handling, I can tell the package has failed, but the history of the job shows the step ( and the whole package) as succeeded. The package failure isn't being communicated to the job step. I don't have any special step options or command line parameters. Am I missing something? Thanks, J |
#3
| |||
| |||
|
|
On Oct 19, 11:18*am, jordan <jordan.sabou... (AT) gmail (DOT) com> wrote: Hi, I've created a job in SQL Server 2005 with one step - call a SSIS package. The step on failure is set to quit the job reporting failure. The SSIS package has a maximum error count of 1. *Through logging built into the error handling, I can tell the package has failed, but the history of the job shows the step ( and the whole package) as succeeded. The package failure isn't being communicated to the job step. I don't have any special step options or command line parameters. Am I missing something? Thanks, J This is a bug in 2005. *Create another step below your cube process step and put the following code in it, which will display the actual results of the cube process step. DECLARE @MESS NVARCHAR(1024) SELECT Top 1 @MESS=jh.message FROM [msdb].[dbo].[sysjobhistory] JH INNER JOIN [msdb].[dbo].[sysjobsteps] JS on JS.job_id=JH.job_id AND JS.step_id=JH.step_id Where JS.subsystem='ANALYSISCOMMAND' ORDER BY JH.instance_id desc IF CHARINDEX('ErrorCode',ISNULL(@MESS,''))>1 RAISERROR(@MESS,16,1) |
![]() |
| Thread Tools | |
| Display Modes | |
| |