Failed to convert Job State Current Status [N/A], we will use default state [NONE] (4371058)

Failed to convert Job State Current Status [N/A], we will use default state [NONE]

Messages like the following are printed in the SQL Server agent log file for Jobs that have never yet been run.

ERROR [AGENTNAME-lowPriorityPool-2-[DBSS_Agent_Job_List][]] com.quest.qsi.fason.sqlserver.collection.processor.DBSSAgentJobListProcessor - Failed to convert Job State Current Status [N/A], we will use default state [NONE]

ERROR [AGENTNAME-lowPriorityPool-2-[DBSS_Agent_Job_List][]] com.quest.qsi.fason.sqlserver.collection.processor.DBSSAgentJobListProcessor - Unexpected current status [NONE], last_outcome [empty] 

The SQL Server Job Status collection looks at the last run outcome value to determine the Job State Current Status.

When a job has never been run, the collection finds that the last run outcome is NA (Not Available) in the query. The collection processor code then uses the default status of "None". The logging then prints a None status in the SQL Server agent log and that the last outcome is empty.

Workaround

This message should be cleared once the job has been run in SQL Server.

Status

Enhancement ID FGSS-I-154 has been created to indicate in the SQL Server agent log file that the job has never been run before. This will be reviewed by Product Management for a future release of the SQL Server cartridge.

FGSS-I-154