In one of my sql 2008 sp1 standalone instance, syspolicy_purge_history job is fails at step 3 Erase Phantom System Health Records....
Below is the command -
Error : 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
can anyone please take a look at this and let me know your findings ?
Service account is same for sql 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 dont see correct solution to this problem
Thanks in advance