Hi @oxxy ,
Thank you for reporting this case. Our Developers are currently working on it and we will reach back to you with updates as soon as possible through email.
I am also experiencing this patching procedure failed issue.
| 2019/02/04 08:00:06 PM | Failed | PROFILE operation failed. 0 patch(es) successfully installed. 0 patch(es) installation failed. |
| 2019/02/04 08:00:06 PM | Failed | Resolving Procedure is failed because failed to retrieve hidden updates from service. |
| 2019/02/04 08:00:06 PM | Started | Resolving Procedure is started. |
Hello @msp_security,
Our development team is still working on this case and fix is planned to be implemented this coming February 16 release. We will also notify you with updates via email.
Thank you for your patience.
I’m getting this error on all my updates: Resolving Procedure is failed because failed to retrieve hidden updates from service.
Hello @msapgroupllc, we have also added you on the list of customers who will be notified for updates regarding on this case. Fix is planned be implemented this coming February 16 release.
Thank you for your patience.
I also have this error - can i be added to the notification list please.
We have communicated with our Product Developers regarding this experience on your account. Rest assured that our Product Team is exhausting all efforts in getting this issue resolved.
To everyone who are experiencing issues with the ‘patch procedures’, you can still deploy OS patches through the Patch Management manually.
I would also like to report this same issue. Please add me to any list of updates about a fix. Thanks
We have looped you in to the escalated ticket @eztech as requested.
I too am eagerly waiting for this to be fixed. It’s been over 2 weeks since the major update and these problems began. Please add me to the list to be notified, but do you all have some type of status page or blog or news page we can follow for these issues that appear to affect everyone?
Hello @davidc1,
We have added you in the email update for the escalated ticket and any update will be relayed via this forum page as well. Thank you
I am having this same issue. Please add me to the notification list. Thank you
Hi @Infintech, a ticket has been created for you regarding the concern on Patch Management. We will update you thru the ticket and this forum post.
Although I previously confirmed that whatever you did to correct this hidden updates problem worked, I would have to report the same issue again:
TIME STATUS ADDITIONAL INFORMATION| 2019/02/20 09:15:17 AM | Failed | PROFILE operation failed. 0 patch(es) successfully installed. 0 patch(es) installation failed. |
| 2019/02/20 09:15:17 AM | Failed | Resolving Procedure is failed because failed to retrieve hidden updates from service. |
| 2019/02/20 09:14:58 AM | Started | Resolving Procedure is started. |
We are saddened to hear that this issue has resurfaced on your end. We would like to clarify as well that these are the updated versions of your communication agent and Client Security on your devices.
Communication Client - 6.26.22863.19020 2019/02/16
Client - Security 11.1.0.7229 2019/02/16
I have updated them. However, it still happened on three computers today.
Would you please clarify how procedure is handled in case device is not online at the scheduled time?
Also, if reboot is suppressed, how it affects procedure realization?
Thanks,
If a command is sent to an endpoint using a schedule patch procedure/process and the device is offline then the command will fail. Then it moves to the next schedule. It the command was triggered manually, it will remain in the queue until the device goes online. However, when a “suppress reboot” comes into play, the EM Portal might show mismatched patches since for “reboot required” patches, the actual remaining patch might not reflect yet on the portal unless you restart the device thus refreshing the ITSM service in the process.
This issue (Resolving Procedure is failed because failed to retrieve hidden updates from service.) is happening to me as well even after the Feb 16th update and all my clients are running 6.26.22863.19020 (2/16/2019) and client security 11.1.0.7229 (2/16/2019)
We are saddened to hear that you are still experiencing this issue after the February release. We will gladly help in investigating this issue. Please respond to the support email we have created for you. We thank you for your patience.