cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Ufoto
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 1 of 6

Repository-related automatic responses no longer work after Update 13

Jump to solution

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!

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?
1 Solution

Accepted Solutions
aguevara
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 6

Re: Repository-related automatic responses no longer work after Update 13

Jump 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?

 

 

View solution in original post

5 Replies
aguevara
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 6

Re: Repository-related automatic responses no longer work after Update 13

Jump to solution

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?

 

Ufoto
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 3 of 6

Re: Repository-related automatic responses no longer work after Update 13

Jump to solution

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,

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?
aguevara
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 6

Re: Repository-related automatic responses no longer work after Update 13

Jump 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?

 

 

ezim
Level 9
Report Inappropriate Content
Message 5 of 6

Re: Repository-related automatic responses no longer work after Update 13

Jump to solution

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

aguevara
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 6 of 6

Re: Repository-related automatic responses no longer work after Update 13

Jump to solution

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?

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community