Unable to log on to the ePO console (Extensions are disabled after an upgrade)
Last Modified: 2023-07-12 11:40:01 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Veja como um ecossistema XDR que está sempre se adaptando pode energizar sua empresa.
O CEO da Trellix, Bryan Palma, explica a necessidade crítica por uma segurança que está sempre aprendendo.
Faça download do relatório Magic Quadrant, que avalia os 19 fornecedores com base na capacidade de execução e na abrangência de visão.
De acordo com a Gartner, “o XDR é uma tecnologia emergente que pode oferecer melhor prevenção, detecção e resposta a ameaças”.
Quais ameaças à segurança cibernética devem estar no radar das empresas em 2022?
A indústria da segurança cibernética nunca descansa, e não há melhor momento do que agora para enxergar isso como uma vantagem e um catalisador para o empoderamento dos negócios.
Duas líderes confiáveis em segurança cibernética se uniram para criar um mundo digital resiliente.
O CEO da Trellix, Bryan Palma, explica a necessidade crítica por uma segurança que está sempre aprendendo.
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.
Unable to log on to the ePO console (Extensions are disabled after an upgrade)
Technical Articles ID:
KB77855
Last Modified: 2023-07-12 11:40:01 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.x
Problem 1
You're unable to log on to the ePO console. This problem is seen after you upgrade to ePO 5.x and restart the system or restart the ePO services. The following message displays when the above occurs: Problem 2
The INFO [main] core.StandardService - Starting service Catalina INFO [main] core.StandardEngine - Starting Servlet Engine: INFO [main] core.StandardHost - XML validation disabled INFO [main] http11.Http11BaseProtocol - Starting Coyote HTTP/1.1 on http-8443 INFO [main] http11.Http11BaseProtocol - Starting Coyote HTTP/1.1 on http-8444 INFO [main] storeconfig.StoreLoader - Find registry server-registry.xml at classpath resource WARN [main] email.EmailServiceConfig - username was null. assuming no username or password ERROR [main] plugin.PluginManager - Initialization of plugin AgentMgmt failed. com.mcafee.orion.core.plugin.PluginException: Plugin excluded from initializing At com.mcafee.orion.core.plugin.PluginManager.initPlugin(PluginManager.java:427) At com.mcafee.orion.core.plugin.PluginManager.init(PluginManager.java:249) At com.mcafee.orion.core.OrionCore.afterStart(OrionCore.java:406) At com.mcafee.orion.core.server.OrionLifecycleListener.lifecycleEvent(OrionLifecycleListener.java:135) At org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120) At org.apache.catalina.core.StandardServer.start(StandardServer.java:705) At org.apache.catalina.startup.Catalina.start(Catalina.java:552) At sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) At sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) At sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) At java.lang.reflect.Method.invoke(Method.java:597) At org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) At org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) ERROR [main] plugin.PluginManager - Initialization of plugin EPOCore failed. com.mcafee.orion.core.plugin.PluginException: Plugin excluded from initializing At com.mcafee.orion.core.plugin.PluginManager.initPlugin(PluginManager.java:427) At com.mcafee.orion.core.plugin.PluginManager.initPlugin(PluginManager.java:459) At com.mcafee.orion.core.plugin.PluginManager.init(PluginManager.java:249) At com.mcafee.orion.core.OrionCore.afterStart(OrionCore.java:406) System Change
The ePO server has successfully upgraded, and the Tomcat service or system is restarted.
Cause
The ePO upgrade installer sets a registry key that identifies the extensions that aren't loaded at startup. During this stage, it leaves the Tomcat service in the install mode. When the services (or system) are restarted, the Tomcat service remains in install mode. This issue occurs when When this crash occurs, the following occur:
Solution
Remove the registry key of the incorrect data: Cuidado Este artigo contém informações sobre como abrir ou modificar o registro.
Affected ProductsLanguages:This article is available in the following languages: |
|