cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
kblowe
Level 10
Report Inappropriate Content
Message 1 of 9

Upgrade to 5.10 & now see Failed to upload package to ePO Server

Jump to solution

I recently upgraded from the latest ePO 5.9.1 with Hotfixes to ePO 5.10 Update 9. Now I'm seeing "Failed to upload package to ePO Server" on my ePO server & client.

Do I need to manually regenerate the Agent Handler certificate on the ePO server?

1 Solution

Accepted Solutions
JoeBidgood
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 9

Re: Upgrade to 5.10 & now see Failed to upload package to ePO Server

Jump to solution

Ah, OK, this is a very similar issue which can also be resolved by regenerating the agent handler cert: see KB92703  for details. Hopefully that will take care of it 🙂

Regards -

Joe

View solution in original post

8 Replies
JoeBidgood
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 9

Re: Upgrade to 5.10 & now see Failed to upload package to ePO Server

Jump to solution

Check the server_<servername>.log in the ..\DB\Logs folder on the ePO server - do you see errors like "Failed to send HTTP request. Error=12175 (12175)" and "Error sending data channel message to application server"?
If so please have a look at KB91298 . There are a number of things that can cause the symptom you describe but this is one of the more common ones.

 

Regards -

 

Joe

kblowe
Level 10
Report Inappropriate Content
Message 3 of 9

Re: Upgrade to 5.10 & now see Failed to upload package to ePO Server

Jump to solution

Not specifically the "12175". But I'm seeing a lot of these errors "12186" below since the 5.10 upgrade. Could be related to the - regenerated SSL (ssl.crt). I had something similar happen when I upgrade to 5.9. I will check out cipher suite too but I think the regenerated SSL (ssl.crt) is what solved my issue in the past. What do you think?

server<epo>.logs:

-NAIMSERV server.cpp(907): Error sending data channel message to application server in 

-Failed to send HTTP request. Error=12186 (12186)

 

masvc_clientname.log are showing:

-masvc(2080.3484) ahclient.Info: Agent handler reports server busy. response code 503.

-masvc(2080.3484) ahclient.Info: Spipe connection response received, network return code = 1008, response code 503.

-masvc(2080.3484) DataChannel.Manager.Error: Failed to upload DataChannel items - Network<1008>, HTTP Response<503>

-masvc(2080.3484) DataChannel.Manager.Error: Failed to upload package to ePO Server

 

 

JoeBidgood
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 9

Re: Upgrade to 5.10 & now see Failed to upload package to ePO Server

Jump to solution

Ah, OK, this is a very similar issue which can also be resolved by regenerating the agent handler cert: see KB92703  for details. Hopefully that will take care of it 🙂

Regards -

Joe

View solution in original post

kblowe
Level 10
Report Inappropriate Content
Message 5 of 9

Re: Upgrade to 5.10 & now see Failed to upload package to ePO Server

Jump to solution

Ok regenerating the certs fixed the issue.

Do you know what I can do about the Debug events that didn't parse to ePO since the upgrade? I tried to reparse a few but doesn't appear that will work.

JoeBidgood
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 6 of 9

Re: Upgrade to 5.10 & now see Failed to upload package to ePO Server

Jump to solution

Hm - this particular problem wouldn't cause events to fail to parse: it actually causes datachannel messages to fail (which look a lot like event failures but are not quite the same.)
If you have a lot of event files piling up in the DB\Events\Debug folder, the first thing to try is simply to move the files up one level into the DB\Events folder. ePO will try to parse them again.

if they go back to the Debug folder it means the events themselves can't be parsed, in which case please check the eventparser_<servername>.log in the DB\Logs folder. Are any errors reported?

HTH-

Joe

kblowe
Level 10
Report Inappropriate Content
Message 7 of 9

Re: Upgrade to 5.10 & now see Failed to upload package to ePO Server

Jump to solution

Right. I understand. I just was asking. I looked deeper and its a specific product event ID not parsing. I will have to look into that issue separately from the ePO issue initially reported in this post. I will check the logs for errors.

Thanks for your time & assistance.

JoeBidgood
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 8 of 9

Re: Upgrade to 5.10 & now see Failed to upload package to ePO Server

Jump to solution

No problem, glad it's working now 🙂

Joe

kblowe
Level 10
Report Inappropriate Content
Message 9 of 9

Re: Upgrade to 5.10 & now see Failed to upload package to ePO Server

Jump to solution

I also checked my cipher suite and those mentioned in KB91298  are already enabled.

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