Skip to Content
0
Former Member
Apr 17, 2009 at 04:03 PM

DB13 failed after upgrade to SQL Server 2005

222 Views

We just migrated to our BW database from SQL 2000 to SQL 2005 and found out could not schedule a database consistence check via DB13. It failed immediate with following error message in the log:

"Unable to start execution of step 1 (reason: The job step contains tokens. For SQL Server 2005 Servi

ce Pack 1 or later, you must use the appropriate ESCAPE_xxx macro to update job steps containing tokens before the job can run.). The step failed."

Anyone know what this ESCAPE_xxx macro is and how do we fix the problem?

Thanks,

Yujun Ran