Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

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 -

(Get-Item SQLSERVER:\SQLPolicy\servername\DEFAULT).EraseSystemHealthPhantomRecords()

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

share|improve this question
2  
Are you running 32-bit SQL Server on a 64-bit OS? –  Aaron Bertrand Jul 15 at 19:04

1 Answer 1

I ran into this error a while back and found this link, hope it resolves your issue. http://www.mssqltips.com/sqlservertip/2041/why-syspolicypurgehistory-job-fails-in-sql-server-2008-failover-cluster-instance/

share|improve this answer
    
Thanks Jeff, but this is a standalone server...still i'm getting the same error... –  Robin16 Jul 16 at 14:31

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.