-
Question
-
Hi ,
I am using SQL server 2014, Jobs is successfully executing for more than a year. For few days step#3 «Erase Phantom System Health Records» gives following error:
«Executed as user: User_name. The step did not generate any output. Process Exit Code 255. The step failed.»
I am unable to find exact solution.
Thanks for help.
Answers
-
Hi Cathy,
We just restarted the server and issue resolved.
Thanks
-
Marked as answer by
ZahidButt
Thursday, February 20, 2020 5:17 PM
-
Marked as answer by
All replies
-
Hi Cathy,
I found an error in event viewer:
«Faulting application name: SQLPS.exe, version: 12.0.2000.8, time stamp: 0x5306bda0
Faulting module name: KERNELBASE.dll, version: 6.3.9600.19478, time stamp: 0x5d6aa558
Exception code: 0xc0000142″I think this is the culprit. If it is so then what is the solution ?
I found following 2 links explaining solution:
https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/error-0xc0000142/3da27a75-178c-4de5-b43c-c538e6005540
Thanks
-
Edited by
ZahidButt
Tuesday, February 11, 2020 2:37 PM
-
Edited by
-
Hi ZahidButt,
Any other more error information? Did you try to apply
SP3 for SQL server 2014 and
CU4 for SQL 2014 SP3?Best regards,
Cathy
MSDN Community Support
Please remember to click «Mark as Answer» the responses that resolved your issue, and to click «Unmark as Answer» if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to
MSDN Support, feel free to contact MSDNFSF@microsoft.com -
Hi Cathy,
We just restarted the server and issue resolved.
Thanks
-
Marked as answer by
ZahidButt
Thursday, February 20, 2020 5:17 PM
-
Marked as answer by
- Remove From My Forums
-
Вопрос
-
Hello, On standalone server job step is failing with below message.
==================================
Date 02/08/2010 12:07:48
Log Job History (syspolicy_purge_history)Step ID 3
Server DPRSQL1
Job Name syspolicy_purge_history
Step Name Erase Phantom System Health Records.
Duration 00:00:00
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0Message
Executed as user: DPRdprsql1. The process could not be created for step 3 of job 0xA4E39092C0176B4AB4A2A2FE0B743FB1 (reason: 193). The step failed.=====================
—————————————————————————————
SEELCT @@VERSION:
=======================================
Microsoft SQL Server 2008 (SP1) — 10.0.2531.0 (X64)
Mar 29 2009 10:11:52
Copyright (c) 1988-2008 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2)
=======================================
No error in SQL Server Errorlog
Ответы
-
This weird problem got resolved now. The root cause was detected when I ran
ProcesMon tool which in it’s [Path] column listed «C:Program» with [Result] column value as «FILE LOCKED WITH ONLY READERS». When I checked in “C:” I found a file strangely named as
«Program.Because of this
SQL Server Agent(SQLAGENT.exe) could not continue to navigate the exact PATH of SQLPS.exe i.e. «C:Program Files (x86)Microsoft SQL Server100ToolsBinnSQLPS.exe»After renaming that the file «C:Program”
all is working now.Tom!! Thanks for looking into the issue.
Regards,
Ajay
-
Помечено в качестве ответа
2 августа 2010 г. 17:01
-
Помечено в качестве ответа
Asked
3 years, 11 months ago
Viewed
3k times
The Erase Phantom System Health Records step failing after upgrading from SQL Server 2008 R2 to SQL Server 2012. Please find the below error and advise.
Executed as user: abcabc
A job step received an error at line 1 in a PowerShell script. The corresponding line is ‘import-module SQLPS -DisableNameChecking’.Correct the script and reschedule the job. The error information returned by PowerShell is: ‘File C:Program Files (x86)Microsoft SQL Server110ToolsPowerShellModulesSQLPSSqlps.ps1 cannot be loaded because the execution of scripts is disabled on this system.
Please see «get-help about_signing» for more details. File C:Program Files
(x86)Microsoft SQL Server110ToolsPowerShellModulesSQLPSSqlps.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see «get-help about_signing» for more details. ‘. Process Exit Code
-1. The step failed.
asked Jun 19, 2019 at 13:55
1
So lved the issue after turnon Script Execution and execution policy to Allow all scripts.
Run->gpedit.msc
Computer Configuration
—>Windows administrative templates->Windows Components-> Windows Powershell-> turnon Script Execution and Allow all scripts(Execution Policy)
answered Jun 20, 2019 at 13:12
NoorNoor
111 silver badge2 bronze badges
Question: In SQL Server 2008 there is a SQL Server Agent Job called syspolicy_purge_history . Step 3 — Erase Phantom System Health Records is failing with reason 193. I have a daily Powershell script — List failed SQL server Jobs with Powershell which reports the failure
How can I fix?
Answer:Look at the command in the Job Step. It will be something like:
It’s attempting a mapping to the SQL Server Instance Path. Which is probably something like:
(Get-Item SQLSERVER:SQLPolicyMyServerInstance).EraseSystemHealthPhantomRecords()
C:Program Filesxxxxxxx
Look at the C: , is there a file called “Program” ? Not a directory , but a file. If so , rename it and rerun the job. It should fix the error .
If this solution does not fix the reason 193 issue on Erase Phantom System Health Records, contact me and I’ll help you out
Related Posts
How to request SQL Server troubleshooting
SQL Server Agent Job Steps
List failed SQL server Jobs with Powershell
Author: Tom Collins (http://www.sqlserver-dba.com)
Share:
Verify your Comment
Previewing your Comment
Posted by:
|
This is only a preview. Your comment has not yet been posted.
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment
The letters and numbers you entered did not match the image. Please try again.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Post a comment on How to Erase Phantom System Health Records – reason 193
Workaround for syspolicy_purge_history step 3 error on SQL 2012
Posted on October 7, 2014 Updated on October 7, 2014
I have started setting up a couple of servers with SQL 2012 SP2. And I noticed that the syspolicy_purge_history job is failing on Step 3 with the following error message:
A job step received an error at line 1 in a Powershell script. The corresponding line is ‘set-executionpolicy RemoteSigned -scope process -Force’. Correct the script and reschedule the job.
So far I have not seen any valid resolution online, so as a workaround, I have setup the Execution policy to UNDEFINED on the following registry entry:
ComputerHKLMSoftwarePowerShell1ShellldsMicrosoft.SqlServer.Management.PowerShell.sqlps110Execution Policy, REG_SZ,Undefined
And as a warning, changing the execution policy to UNDEFINED may open security holes on your server. If you found a fix for this issues, please feel free to leave a comment so I can update this post.
Update: I found a Microsoft KB article that talks about adding a GPO to correct the issue. http://support.microsoft.com/kb/2995870
Thank you
This entry was posted in SQL and tagged Erase Phantom, Erase Phantom System Health Records, SQL, SQL 2012, syspolicy_purge_history.