Hi Team, I hope I can get help on this issue.
We use third party tool to Install McAfee Agent after extracting RPM package.
Agent communicate back fine when installing the extracted RPM package with version 5.7.4. No issue. The issue we are seeing is when we upgrade the agent from 5.7.4 to any of the higher agent version using ePO, servers stops communicating with "Received response from broker with status <505>"
Solved! Go to Solution.
We use to get this before and I fixed it. Then it resurfaced in another environment and I forgot all about my fix and just reinvestigated this. Hopefully a fix can be implemented.
During upgrade the agent runs yum -y remove MAProvision which likely removed MFEdx due to dependencies. My fix was to run rpm -e MAProvision right after the agent is installed using yum install MAProvision or at least before you have the ePO server upgrade it.
Hello,
What if you install the application without third party application?
Is that getting installed?
Thanks,
Helo.
Do You resolved your problem with error 505 after upgrade agent?
If you are getting that error, you might want to open a ticket. We would need to see all the install logs plus some debug logging possibly from the agent.
Does it go away if you do a reboot?
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?
We use to get this before and I fixed it. Then it resurfaced in another environment and I forgot all about my fix and just reinvestigated this. Hopefully a fix can be implemented.
During upgrade the agent runs yum -y remove MAProvision which likely removed MFEdx due to dependencies. My fix was to run rpm -e MAProvision right after the agent is installed using yum install MAProvision or at least before you have the ePO server upgrade it.
The install guide has additional steps for adding dxl.
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?
We still have this issue. We are unable to upgrade from epo because of this issue. SR has been escalated to Development team three months ago.
can you send me your SR number in private chat please?
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?
@neutronscott Thank you for your suggestion. We tested on a couple of servers and in both cases, the error went away and the agent communicated fine.
The question is what is in MAProvision rpm that is causing 505 error? This question is really for Trellix Development team.
DXL component needs to be added separately per https://docs.trellix.com/bundle/trellix-agent-5.7.x-installation-guide/page/GUID-5E215352-6764-476B-...
Create the MFEdx-ma-<build_number>.rpm file
maprovision tries to provision the agent to epo and if all required files aren't there where expected to be, it may fail.
Do you have all the required files?
MAProvision.rpm, MFEma.rpm, MFErt.rpm, and MFEdx-ma-<build_number>.rpm
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: