Troubleshooting SYSPOLICY_PURGE_HISTORY Job Failure in Failover Cluster Instance of SQL Server 2008
Jun 07, 2012
This article describes troubleshooting steps for SYSPOLICY_PURGE_HISTORY SQL Server Job failure in Failover Cluster Instance of SQL Server 2008. In case of SYSPOLICY_PURGE_HISTORY Job has failed in a Stand-Alone Instance of SQL Server 2008 then refer the following article titled "Troubleshooting SYSPOLICY_PURGE_HISTORY Job Failure in Stand Alone Instance of SQL Server 2008"
SYSPOLICY_PURGE_HISTORY Job fails in Failover Cluster Instance of SQL Server 2008
The SYSPOLICY_PURGE_HISTORY Job fails with the below mentioned error at step 3 “Erase Phantom System Health Records” of a Failover Cluster Instance of SQL Server 2008. The reason why this job is falling at Step 3 “Erase Phantom System Health Records” is within the PowerShell script still SQL Server Node Name is mentioned. To resolve this issue you need to replace the SQL Server Node Name with the SQL Server Virtual Name.
Executed as user: Domain\UserName. A job step received an error at line 1 in a PowerShell script. The corresponding line is '(Get-Item SQLSERVER:\SQLPolicy\MYTECHMANTRACLUSB\DEFAULT).EraseSystemHealthPhantomRecords()'. Correct the script and reschedule the job. The error information returned by PowerShell is: 'Failed to connect to server . A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (Provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) '. Process Exit Code -1. The step failed.
Wrong Value of SQL Server Virtual Name in Erase Phantom System Health Records job step
Correct Value of SQL Server Virtual Name in Erase Phantom System Health Records job step
You need to make the changes to the PowerShell script and then click OK to save the change to SYSPOLICY_PURGE_HISTORY Job as shown in the snippet below.
In this article you have seen troubleshooting steps for SYSPOLICY_PURGE_HISTORY Job failure in Failover Cluster Instance of SQL Server 2008.
Continue Free Learning...
Geeks who read this article also read…
- Troubleshooting SYSPOLICY_PURGE_HISTORY Job Failure in Stand Alone Instance SQL Server 2008
- Troubleshooting OLE DB Provider Microsoft.ACE.OLEDB.12.0 is not registered Error
- Troubleshooting SQL Server blocked access to procedure sp_send_dbmail
- Performance Dashboard Reports in SQL Server 2012
- Tips to Avoid Account Lockout Issues
- Encrypt Database Backups in SQL Server Using MEDIAPASSWORD Option
- Using SP_SERVER_DIAGNOSTICS Stored Procedure Quickly Gather Diagnostic Data and Health Information in SQL Server 2012
- New Features in Microsoft SQL Server 2012 for Database Administrators
- New Features in SQL Server 2012 for Database Developers
- Why an SQL Server Database from a higher version cannot be restored onto a lower version?
- How to identify if the database was upgraded from a previous version of SQL Server
- Installing SQL Server 2008 R2 on Windows Server 2008 R2
- Using Transparent Data Encryption Feature of SQL Server 2008
- New Date and Time Data Types in SQL Server 2008
- Date and Time Functions in SQL Server 2008
- Configuring Database Instant File Initialization Feature of SQL Server
- Changing the default location of SQL Server Data and Log files
- Changing Default SQL Server Backup Folder in SQL Server 2008
- How to repair a Suspect Database in SQL Server
- Steps to Rebuild System Databases in SQL Server
- How to Get Exclusive Access to SQL Server Database
- Read More SQL Server Articles…