cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
it1024
Level 9
Report Inappropriate Content
Message 1 of 4

Agent 4.8.0 upgrade to 5.5.1

Hi,

When trying to install Agent 5.5.1 on a machine where 4.8.0 is installed the task is successful but the machine is out of control afterwards. However when I try to install 4.8.0 again the problem is solved immediately after seconds.

 

3 Replies
McAfee Employee Hawkmoon
McAfee Employee
Report Inappropriate Content
Message 2 of 4

Re: Agent 4.8.0 upgrade to 5.5.1

Hi it1024,

Regarding MA 4.8, when it was supported the minimum required was 4.8 Patch3, is this the version you have?
(If not can you updgrade to P3 and upgrade again?)

Assumming you are working with v4.8 p3, the logs from the 'new' v5 install would hold details about what is happening with the new agent. Can you review the following logs see if they report error messages, share with us so we can have a look to help?

Logs to review (no particulare order):

  1. McScript.log
  2. masvc_<machine name>.log
  3. macmnsvc_<machine name>.log
  4. macompatsvc_<machine name>.log

I suspect and so wonder if you have messages like the examples below:

  • Error: UV connect Failed - uv error <34> <no such file or directory>
  • Error: UV write failed - uv error <36> <broken pipe>
  • Error: WinHttpGetProxyForUrl failed with windows err <12006>

Or messages offering 'curl error <number>' or maybe a 'HTTP error 403'

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?

Re: Agent 4.8.0 upgrade to 5.5.1

Hello, all

Im having the same issue with only one client. It fails to get the AMCore update with the massage

  • Error: WinHttpGetProxyForUrl failed with windows err <12006>

ePO 5.10

Agent 5.6.0.702

2019-08-06 14:00:09.368 masvc(4588.7588) msgbus.Info: Allowing <21180> onto msgbus
2019-08-06 14:00:09.415 masvc(4588.7588) proxy_detect.Error: WinHttpGetProxyForUrl failed with windows err <12006>
2019-08-06 14:00:09.415 masvc(4588.7588) proxy_detect.Info: no system proxy, proxy detect returns rc <1014>
2019-08-06 14:00:09.415 masvc(4588.7588) compatservice.Info: Received notifications for changes on backcompat watcher
2019-08-06 14:00:09.415 masvc(4588.7588) compatservice.Info: is_compat_running: 1, is_compat_required: 1
2019-08-06 14:00:09.446 masvc(4588.7588) proxy_detect.Error: WinHttpGetProxyForUrl failed with windows err <12006>
2019-08-06 14:00:09.446 masvc(4588.7588) proxy_detect.Info: no system proxy, proxy detect returns rc <1014>
2019-08-06 14:00:09.446 masvc(4588.7588) proxy_detect.Error: WINHTTP_ACCESS_TYPE_NO_PROXY

 

Anyone?

Thanks in advance

 

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 4 of 4

Re: Agent 4.8.0 upgrade to 5.5.1

Try going through the steps here - https://community.mcafee.com/t5/ePolicy-Orchestrator/HOW-TO-TROUBLESHOOT-CLIENT-UPDATE-DEPLOYMENT-FA...

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?

More McAfee Tools to Help You

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