cancel
Showing results for 
Search instead for 
Did you mean: 

Fail to upgrade Move extension from 4.6 to 4.8

Hi,

We planned to upgrade Move Agentless from 4.6 to 4.8 during the process we were not able to proceed. We failed on extension upgrade.
We use EPO 5.3.3 build 279
We received message like:

Unable to install extension. Extension dir already exists: C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions\installed\DC__GS__4000\4.8.0.114

and 

Can't upgrade extension DC__GS__4000 because an extension with that name is already present in a partially installed state. Remove the extension before attempting an upgrade.

Any though & idea is Welcome.

Rgds,

MA

 

6 Replies
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 2 of 7

Re: Fail to upgrade Move extension from 4.6 to 4.8

Turn off epo services, then go into the C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions\installed\DC__GS__4000 directory.  Delete the 4.8.0.114 folder - there should be a 4.6 folder still there.

Then go to C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\conf\catalina\localhost and look for the dc_gs_4000 xml file and edit it to match the build number that the 4.6 folder is.  Then restart epo and try again.

 

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: Fail to upgrade Move extension from 4.6 to 4.8

Hello,

Thank you for quick answer. On C:\Program Files (x86)\McAfee\ePolicy no Move 4.8 folder exist.

Then go to C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\conf\catalina\localhost and look for the dc_gs_4000 xml  file version match with the installed.

Thank you in advance for your Help.


*******************************************************************************
Below the logs we had.

1. First attempt to install extension MOVE-AV_Meta_Package_Ext_4.8.0.104.zip failed after long time with following errors:
 
(ApplicationFilterChain.java:208) at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at com.mcafee.orion.core.server.DisableUrlSessionFilter.doFilter(DisableUrlSessionFilter.java:62) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:603) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:1025) at com.mcafee.orion.core.server.mfsvalve.ValveContext.invokeNextInChain(ValveContext.java:27) at com.mcafee.orion.core.server.AccessControlValveHook.invoke(AccessControlValveHook.java:82) at com.mcafee.orion.core.server.mfsvalve.ValveContext.invokeNextInChain(ValveContext.java:25) at com.mcafee.orion.core.server.mfsvalve.MfsValve.invoke(MfsValve.java:38) at com.mcafee.orion.core.server.AjaxValve.invoke(AjaxValve.java:84) at com.mcafee.orion.core.server.OrionUserSetupValve.invoke(OrionUserSetupValve.java:41) at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:321) at com.mcafee.orion.core.server.OrionSingleSignOn.invoke(OrionSingleSignOn.java:218) at com.mcafee.orion.core.server.ClientCertValve.invoke(ClientCertValve.java:61) at com.mcafee.orion.core.server.ExternalAuthenticationStrategyExtPointValve.invoke(ExternalAuthenticationStrategyExtPointValve.java:99) at com.mcafee.orion.core.server.ParameterEncodingValve.invoke(ParameterEncodingValve.java:34) at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:695) at com.mcafee.orion.core.server.ThreadLocalInfoCleanupValve.invoke(ThreadLocalInfoCleanupValve.java:21) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:445) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1137) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1775) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1734) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748) Caused by: java.sql.SQLException: Transaction (Process ID 154) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:373) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2985) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2418) at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:668) at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:614) at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:573) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:730) at sun.reflect.GeneratedMethodAccessor207.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.mcafee.orion.core.db.sqlserver.JtdsStatementRetryInvocationHandler.invoke(JtdsStatementRetryInvocationHandler.java:87) at com.sun.proxy.$Proxy17.executeUpdate(Unknown Source) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.mcafee.epo.policy.services.PolicyObjectServiceInternal.savePolicySettingValue(PolicyObjectServiceInternal.java:1279) at com.mcafee.epo.policy.services.PolicyObjectServiceInternal.savePolicySettings(PolicyObjectServiceInternal.java:997) at com.mcafee.epo.policy.services.PolicyObjectServiceInternal.savePolicySettings(PolicyObjectServiceInternal.java:891) at com.mcafee.epo.policy.services.PolicyImportExportServiceInternal.installPolicyObjectFromXML(PolicyImportExportServiceInternal.java:1216) ... 75 more Total time: 1 minute 56 seconds
 
 
2. Second attempt to install the extension failed after short time with different error:
 
Unable to install extension. Extension dir already exists: C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions\installed\DC__GS__4000\4.8.0.114
 
Even when deleting or renaming the extension folders, we were unable to install the extension. Later on, it was referring to additional error:
 
Can't upgrade extension DC__GS__4000 because an extension with that name is already present in a partially installed state. Remove the extension before attempting an upgrade.
 

 

 

 

 

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

Re: Fail to upgrade Move extension from 4.6 to 4.8

Please open a ticket with McAfee then so we can fix the partially installed extension for you. 

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: Fail to upgrade Move extension from 4.6 to 4.8

All,

Finally we had to totally remove incomplete installed extensions (4.8). We restarted the server but Move is not working. Base on Mc Afee expert root cause could be some incoherence in the SQL DB.
We've planned to restore the EPO & SQL server to the date before install extension tentative.

Re: Fail to upgrade Move extension from 4.6 to 4.8

Actually that works for me today, I had the same issue, but you will need to delete the extension also in SQL Data Base, there are a KB for that, I'll share later

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

Re: Fail to upgrade Move extension from 4.6 to 4.8

I know kb81737 tells you to remove it from the database, but please be very cautious doing that, as a help extension it is ok, but other extensions add tables, stored procedures, etc.  So if you remove it from the orionextensions table, the other related tables remain and you will be unable to reinstall the extension because they already exist. 

KB70963 is a better kb for this issue.  One thing it is missing - if the database has a lower version than the file system folder versions, then modify the xml to match the database and remove the higher version of the extension folder that is higher than the database - so the same version folder should remain. 

 

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
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator