I use SSM document AWS-RunPatchBaseline to patch my windows servers. while trying to run it, I had this error with one of my servers:
Invoke-PatchBaselineOperation : Exception Details: An error occurred when
attempting to search Windows Update.
Exception Level 1:
Error Message: Server execution failed (Exception from HRESULT: 0x80080005
(CO_E_SERVER_EXEC_FAILURE))
Stack Trace: at WUApiLib.IUpdateSearcher.Search(String criteria)
at Amazon.Patch.Baseline.Operations.PatchNow.Implementations.WindowsUpda
teAgent.SearchByGuids(List`1 kbGuids)
At C:\ProgramData\Amazon\SSM\InstanceData\i-0931550e0e5fd124d\document\orchestr
ation\52bc9b99-6ee4-4819-9234-8461530012f9\PatchWindows\_script.ps1:198 char:13
+ $response = Invoke-PatchBaselineOperation -Operation Install -SnapshotId
'0b2d54 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
+ CategoryInfo : OperationStopped: (Amazon.Patch.Ba...UpdateOpera
tion:InstallWindowsUpdateOperation) [Invoke-PatchBaselineOperation], Excep
tion
+ FullyQualifiedErrorId : Exception Level 1:
Error Message: Exception Details: An error occurred when attempting to
se arch Windows Update.
Exception Level 1:
Error Message: Server execution failed (Exception from HRESULT:
0x800800 05 (CO_E_SERVER_EXEC_FAILURE))
Stack Trace: at WUApiLib.IUpdateSearcher.Search(String criteria)
at
Amazon.Patch.Baseline.Operations.PatchNow.Implementations.WindowsU
pdateAgent.SearchByGuids(List`1 kbGuids)
Stack Trace: at
Amazon.Patch.Baseline.Operations.PatchNow.Implementati
ons.InstallWindowsUpdateOperation.DoWindowsUpdateOperation()
at
Amazon.Patch.Baseline.Operations.PatchNow.Implementations.WindowsUp
dateOperation.DoBeginProcessing()
,Amazon.Patch.Baseline.Operations.PowerShellCmdlets.InvokePatchBaselineOpe
ration
failed to run commands: exit status 4294967295
I tried to check this key : HKEY_LOCAL_MACHINE > Software > Policies > Microsoft > Windows > WindowsUpdate > UseWUServer
but I could not find it inside my server.
My server is windows server 2012 R2.
I also looked into the CPUUtilization metric on Cloudwatch during the execution of the patch baseline and it seemed normal.
Any clues?
User contributions licensed under CC BY-SA 3.0