In one of my SQL Server 2008 sp1 standalone instances, syspolicy_purge_history job is fails at step 3 Erase Phantom System Health Records.
Below is the command -
Executed as user: domain\xxxxx. The process could not be created for step 3 of job 0x3183E8EEDE9C3A4DA0F20ABD41B573DC (reason: %1 is not a valid Win32 application). The step
Service account is same for SQL Server and Agent and it is admin on the server. I'm aware that clustered instances usually fail because of virtual name mismatch but I tried searching Google but I don't see correct solution to this problem.