Hello,
We've noticed that since we started to upgrade ePO servers to Update 13, the automatic responses for distributed repository replication failure and main repository update failed are no longer working.
We tried to use both the event description (e.g. Distributed Repository Replication failed) and also the Event IDs (16005, 16003) as a filter but none of them work, the responses are not triggering at all. We verified this on several ePO servers so it is 100% reproducible in a test environment.
Are you aware whether this is an issue, bug, or if something on the back-end changed and these filters are no longer able to capture the events?
Thank you in advance!
Solved! Go to Solution.
Yes it will , this issue relates to an internal server event for the Main Repository affecting both issues.
You are welcome to open a service request and try the POC
Regards
Alejandro
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
It is indeed a bug we have, we have a Hot fix for this issue:
https://kc.mcafee.com/corporate/index?page=content&id=KB95452
Could you please raise a Service request so that we can hand that to you
Regards
Alejandro
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Hello,
Yes, I am aware of this bug, but could you confirm that the POC also resolves the automatic response issue I am referring to? As there is no mention of such problem in the KB article.
Thank you,
Yes it will , this issue relates to an internal server event for the Main Repository affecting both issues.
You are welcome to open a service request and try the POC
Regards
Alejandro
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Hello Alejandro,
Are you able to confirm an estimated time when there will be an official fix for this issue?
Not just the POC, as this is not recommended to run in a production environment?
Also, may I ask what the rationale was to change the name of the "Master Repository" to "Main Repository"?
Many thanks
This will be included on CU 14 and thats scheduled for Q3 this year
we started a campaign on trying to remove words that can be seen bad by different people and and replacing them with other terms 🙂
Im sure we had a doc somewhere out there explaining this but i cant find it now
Regards
Alejandro
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: