LiteSpeed-specific activity is not getting logged into a failed SQL Server job history log. I want to know why this job failed, not the next time the error occurs (after we enable LiteSpeed logging). I need to know what went wrong with this run. Every SQL job logs why it failed in the history (except for LiteSpeed apparently). I need to know why a backup failed immediately so I can fix it and run what was missed. Backups are critical. If it fails, it should not take an SR with Quest to find out why.
In the below job log of a job run by LiteSpeed, there is no logging about the error, about what caused the step to fail.
EXAMPLE AGENT HISTORY ENTRY (nothing there from LiteSpeed) :
00:50:00,qcm_IntelligentDefragmentationJob_3.3,Error,1,NBCDPSAEC01V\INSTANCE_A,qcm_IntelligentDefragmentationJob_3.3,Execute usp_intelligentdefragmentation<c/> step 1,,Executed as user: IAC_NT\SQLSAPProd. ...inst: 1 [SQLSTATE 01000] (Message 0) Read queue [SQLSTATE 01000] (Message 0) usedmv: 512 [SQLSTATE 01000] (Message 0) End: no [SQLSTATE 01000] (Message 0) id: 163474 [SQLSTATE 01000] (Message 0) 10 s [SQLSTATE 01000] (Message 0) Set update flag [SQLSTATE 01000] (Message 0) Check database name [SQLSTATE 01000] (Message 0) Database name: QuestSoftware [SQLSTATE 01000] (Message 0) Check READ_ONLY [SQLSTATE 01000] (Message 0) Read recovery mode [SQLSTATE 01000] (Message 0) Check table name [SQLSTATE 01000] (Message 0) Table name: qcm_partitionsize [SQLSTATE 01000] (Message 0) Check ability to reorg online [SQLSTATE 01000] (Message 0) Index name: qcm_IX_partitionsize_partitionid [SQLSTATE 01000] (Message 0) Check filegroup [SQLSTATE 01000] (Message 0) Update reorg status [SQLSTATE 01000] (Message 0) Build cmd for INDEX REBUILD [SQLSTATE 01000] (Message 0) Execute cmd [SQLSTATE 01000] (Message 0) Update reorg status [SQLSTATE 01000] (... The step failed.,01:55:46,16,2552,,,,0