Question

You maintain a SQL Server Agent job that runs a CmdExec step. The step uses the token $(ESCAPE_SQUOTE(SRVR)) to pass the server name to a batch file. After upgrading to a newer SQL Server version, the job step now fails immediately with an error stating that the job step contains an unsafe, unescaped token. Other steps that reference $(DATE) and $(TIME) run without error. What is the MOST likely cause and correct fix?

Accepted Answer

A token used in a job step must be wrapped with one of the escape macros (such as ESCAPE_SQUOTE, ESCAPE_DQUOTE, or ESCAPE_RBRACKET); the failing step references a token like $(A-DBM_EVENT) without an escape macro, which newer versions reject.

Answer

The SQL Server Agent service account lacks the CmdExec proxy permission; grant the account membership in the sysadmin fixed server role.

Answer

The job history retention limit was reached, so Agent stops evaluating tokens; increase the maximum job history rows setting.

Answer

Token replacement is only supported for T-SQL job steps, not CmdExec steps; convert the CmdExec step to a T-SQL step that calls xp_cmdshell.