Canal de datos. Manager. error: no se ha podido cargar el paquete en el servidor de ePO
Last Modified: 2022-07-18 19:00:29 Etc/GMT
Aviso de isenção de responsabilidade
Produtos afetados
Idiomas:
Este artigo está disponível nos seguintes idiomas:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
Canal de datos. Manager. error: no se ha podido cargar el paquete en el servidor de ePO
Technical Articles ID:
KB92553
Last Modified: 2022-07-18 19:00:29 Etc/GMT Environment
McAfee Agent (MA) 5.x McAfee ePolicy Orchestrator (ePO) 5.x Problem
Aunque la comunicación general entre la McAfee Agent y el servidor de ePO funciona, para los Los siguientes errores se registran en el ------------------------------------------------------------------------------------------ masvc(9096.15416) ahclient.Info: Spipe connection response received, network return code = 1008, response code 503.v 2020-03-18 15:37:34.558 masvc(9096.15416) DataChannel.Manager.Error: Failed to upload DataChannel items - Network<1008>, HTTP Response<503> masvc(9096.15416) DataChannel.Manager.Error: Failed to upload package to ePO Server ------------------------------------------------------------------------------------------ masvc(9096.15416) msgbus.Debug: topic <ma.logger.msg.pub.topic> reachability <1> masvc(9096.15416) loop_worker.Trace: scheduled an async work request, now has 2 pending work requestsv 2020-03-18 15:37:34.558 masvc(9096.15416) ahclient.Info: Agent communication session closed masvc(9096.15416) msgbus.Debug: topic <ma.logger.msg.pub.topic> reachability <1> masvc(9096.15416) loop_worker.Trace: scheduled an async work request, now has 3 pending work requests masvc(9096.15416) network.Trace: poller closed 1164v En el I #04192 MOD_EPO epo request processed, rc=503, session ID=8192, session time=2296ms I #04192 NAIMSERV Received [MsgUpload] from <client_computer_name>:{6CE6286C-6959-11EA-361B-0050569CAB4D} ------------------------------------------------------------------------------------------ E #04192 MCUPLOAD SecureHttp.cpp(984): Failed to send HTTP request. Error=12007 (12007) E #04192 MCUPLOAD SecureHttp.cpp(986): System error 12007 means unable to resolve target address for <server name>, adjust machine DNS configuration as necessary to resolve this issue ------------------------------------------------------------------------------------------ E #04192 NAIMSERV server.cpp(558): Failed to send request, err=0x80004005, HTTP status code=0 E #04192 NAIMSERV server.cpp(923): Error sending data channel message to application server I #04192 NAIMSERV Processed [MsgUpload] from <client_computer_name>:{6CE6286C-6959-11EA-361B-0050569CAB4D} in 2282ms E #04192 NAIMSERV AgentServerCommHandler.cpp(656): Failed to process agent request I #04192 MOD_EPO epo request processed, rc=503, session ID=8193, session time=2297ms Cause
El Controlador de agentes remoto y el Controlador de agentes principal no pueden resolver el nombre de dominio completo (FQDN) del servidor de ePO (servicio Tomcat) en una dirección IP. NOTA: Si ePO se encuentra en el grupo de trabajo, no puede resolver el nombre de la host. Solução
Opción 1 Resuelva el problema de DNS. Opción 2 Agregue el FQDN y la dirección IP del servidor de ePO al Nota: Location del Ejemplo de edición de archivos de host: Aviso de isenção de responsabilidadeO conteúdo original deste artigo foi redigido em inglês. Se houver diferenças entre o conteúdo em inglês e sua tradução, o conteúdo em inglês será o mais exato. Parte deste conteúdo foi criado por meio de tradução automática da Microsoft.
Produtos afetadosIdiomas:Este artigo está disponível nos seguintes idiomas: |
|