exit code: -2145124329: (0x80240017)
"Operation was not performed because there are no applicable updates."
If you run a new Patch Analysis does it still show this as missing?
Jim, Thanks for the reply.
We cannot re-execute the patch analysis job since another downtime has to be requested. Also what does exact error code denotes
No down time is required for Patch Analysis - it is analyzing the target, not updating it.
That exit code -2145124329: (0x80240017) means "Operation was not performed because there are no applicable updates."
So it means that the patch you are trying to install does not apply to this target.
If you still get the patch shown as missing in the next patch analysis, then we need to look into that more closely,
But if it is no longer shown as missing, then it was a one off and it can be ignored.
Some customers add this code to the Successful or Warning codes in Patch Global Configuration
Since the patches are showing as "Missing Bulletin" in the patch analysis job so is there any way to identify that particular patch is applicable or not.
If its applicable for a OS version then its obvious that it will be applicable for all the servers under that OS version.
What version of BSA is this?
When was the Patch Catalog last updated?
Please can you set the Job Property DEBUG_MODE_ENABLE=True on the Patch Analysis Job (PAJ) and rerun it Then attach the shavlik_results.xml and the trace.txt (the location will be mentioned in the PAJ Job Run Log
(To attach files, use the advanced editor)
If you don't want to post these files in a public domain, please log a support case
Jim BSA version using is 8.2.04.437
and Patch catalog was updated before the activity in the month of November.
Trace.txt and Shavlik-results.xml are no more available since they are deleted once the PAJ is executed and I have set the DEBUG_MODE_ENABLED as true. We have a environment where we cannot execute the patch analysis job without downtime.
Shavlik have issue no updated detection logic for MS15-063 since it's original inclusion in XML Version 220.127.116.1198 on 6/9/2015 (9th June)
The detection logic used to test whether it is missing will be based on the published Microsoft Bulletin.
The details of the testing will be in the trace.txt.
We need to run the analysis (in debug mode) and collect the output to make a detailed review.
Thanks for the help Jim!!
Will try to re-run the PAJ and analyze further.