Failed status but each script task shows Completed

Usage and Config Platform
1

(imported topic written by jpeppers91)

I have an issue on some machine where the overall status is failed but if you open the fixlet for that action on a machine each task shows completed. So why would it show a failed status instead of Completed or Pending Restart?

jp

2

(imported comment written by SystemAdmin)

Check the action Success Criteria

3

(imported comment written by jpeppers91)

The actions are all successful

4

(imported comment written by SystemAdmin)

I too have had this happen and I know at least one time when we dug into it, it was becuase the action had a custom success criteria, which when you are looking at the action completion information, is not obvious at all.

So check the fixlet / task - look on the action tab - and see if the action you took has a “Include Custom Success Criteria” checked. That may be the cause.

Of course, I’ve also seen the opposite happen, where an individual task failed but the gui reported sucess and the action reported success. This has always been when an MSI install exists with an error code.

5

Hello, I got the same problem. Using a MS17-010 patch baseline, some number of target got fixed and some are Failed in status after restart. I tried to look at Event Viewer under “Setup” and I got these message.

Windows update could not be installed because of error 2148007941 “Server execution failed” (Command line: ““C:\Windows\system32\wusa.exe” “C:\Program Files (x86)\BigFix Enterprise\BES Client__BESData\Enterprise Security__Download\windows6.1-kb4012212-x64_2decefaa02e2058dcd965702509a992d8c4e92b3.msu” /quiet /norestart”)