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

[kblowe]

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?

[JoeBidgood]

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]

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 · Accepted 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

[kblowe]

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]

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]

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]

No problem, glad it's working now 🙂

Joe

[kblowe]

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