Loading...

Knowledge Center


Dependency errors after starting the "ePolicy Orchestrator Application Server" service for the first time after performing a Disaster Recovery
Technical Articles ID:   KB81754
Last Modified:  7/9/2018
Rated:


Environment

McAfee ePolicy Orchestrator (ePO) 5.x, 4.x

Summary

After performing a Disaster Recovery of ePO, you may see dependency errors on the ePO console log on screen and in the orion.log file, which prevents you from logging into the ePO console.

Problem

When a fresh copy of ePO is reinstalled as part of the Disaster Recovery (DR) process, and then the DR files are restored, the ePolicy Orchestrator Application Server service will start, but there will be dependency errors on the log on screen (and within the orion.log file) similar to the following:

EPOAGENTMETA - Dependency DataChannel had initialization error  
ComputerMgmt - Dependency ldap had initialization error  
RepositoryMgmt - Dependency ComputerMgmt had initialization error  
 

A similar error will display for each of the installed extensions. In addition, the following error will display in orion.log:

core - Error creating bean with name 'core.ext.taskGlobals' defined in URL [jndi:/localhost/core/WEB-INF/beans.xml]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: The following extensions are in a partially installed state: [DataChannel:4.5.7.166, AvertAlerts:4.5.7.166, Notifications:4.5.7.166, rsd:4.5.7.166, epolicensing:2.0.0.117, hip_help:700.321, help:2.0.1, Issue:2.0.2, InstallHelper:4.5.7.166, SIARevocation:1.0, epo_help:450.399, msa_help:450.378, scheduler:2.0.6, vse_help:880.848, PolicyMgmt:4.5.7.166, VIRUSCAN8700:8.7.0.174, console:2.0.5, ldap:2.0.4, rs:2.0.1, CommonEvents:4.5.7.166, sae_200_help:200.321, VIRUSCANREPORTS:1.2.0.183, epoMigration:4.5.7.166, Countermeasures:4.5.7.166, EPOCore:4.5.7.166, VIRUSCAN8800:8.8.0.322, response:2.0.5, AgentMgmt:4.5.7.166, EPOAGENTMETA:4.8.0.296, ComputerMgmt:4.5.7.166, VSEMAS870000:8.7.0.106, VSESTOMD1000:1.0.0.339, RepositoryMgmt:4.5.7.166]  


NOTE: 
The names and version numbers of the extensions listed in the error message will vary depending on the ePO version and the extensions installed.
 

Cause

This can occur if you create a folder inside ..\Program files (x86)\McAfee\ that starts with the name 'ePolicy'. For example, ePolicy Orchestrator backup.
 
This can cause a change to the 8.3 path for the new ePO installation directory when ePO is reinstalled, rendering the 8.3 paths contained within the config files (that were backed up during the DR process) incorrect. 
 
Use the following process to determine the 8.3 name for the ePolicy Orchestrator installation folder on the ePO server:
  1. Click Start, Run, type cmd and click OK.
  2. Change to the McAfee Directory (Example: cd c:\program files (x86)\McAfee).
  3. Use the Dir /x command to view the 8.3 names of all folders in the McAfee directory.

    A typical dir /x listing for the McAfee folder will look similar to the following:

    **************
    c:\Program Files (x86)\McAfee>dir /x
     Volume in drive C has no label.
     Volume Serial Number is 948C-0BDC

     Directory of c:\Program Files (x86)\McAfee

    04/21/2014  10:19 AM    <DIR>                       .
    04/21/2014  10:19 AM    <DIR>                       ..
    01/29/2014  01:36 PM    <DIR>          COMMON~1    Common Framework
    03/20/2014  09:31 AM    <DIR>          EPOLIC~1     ePolicy Orchestrator
    06/18/2013  04:12 PM    <DIR>          VIRUSS~1     VirusScan Enterprise

                   0 File(s)              0 bytes
                   3 Dir(s)   1,091,317,760 bytes free
    **************

    In the above list, the 8.3 name of the ePolicy Orchestrator folder is EPOLIC~1.

    If you create another folder in the root of McAfee that starts with the same eight characters as the ePolicy Orchestrator folder (for example, ePolicy backup) after the ePO is uninstalled and the original ePolicy Orchestrator folder is deleted, and before re-installing ePO, this will change the 8.3 name for the new ePolicy Orchestrator folder that is created during the reinstallation of ePO. Therefore, the dir /x listing will look similar to the following after ePO is re-installed:

    *************
    c:\Program Files (x86)\McAfee>dir /x
    Volume in drive C has no label.
    Volume Serial Number is 948C-0BDC

    Directory of c:\Program Files (x86)\McAfee


    04/21/2014  10:19 AM    <DIR>                       .
    04/21/2014  10:19 AM    <DIR>                       ..
    01/29/2014  01:36 PM    <DIR>          COMMON~1     Common Framework
    04/21/2014  11:12 AM    <DIR>          EPOLIC~1     epolicy backup
    03/20/2014  09:31 AM    <DIR>          EPOLIC~2     ePolicy Orchestrator
    06/18/2013  04:12 PM    <DIR>          VIRUSS~1     VirusScan Enterprise

                   0 File(s)              0 bytes
                   4 Dir(s)   1,091,317,760 bytes free
    *************

    In the above list, the 8.3 name of the newly created ePolicy Orchestrator folder is now EPOLIC~2 instead of EPOLIC~1 like it was originally.

    To further clarify, when ePO is uninstalled during the DR process, the ePolicy Orchestrator folder is removed and the 8.3 name that was reserved for this folder (EPOLIC~1) is no longer reserved. If a new folder is created under the McAfee directory that starts with the same eight characters (for example, ePolicy Backup), this automatically gets assigned the 8.3 name of EPOLIC~1, which was previously used for the original ePO installation folder. When ePO is reinstalled, the installer creates a new folder with the name of ePolicy Orchestrator. Because there is already another folder in this same directory that starts with the same eight characters, Windows then assigns the 8.3 name of EPOLIC~2. Any configuration file for the original ePO installation that was backed up as part of the DR process before ePO was removed, will point to the original 8.3 name of the ePolicy Orchestrator folder (for example: c:\PROGRA~2\McAfee\EPOLIC~1). In this instance, this now equates to the long path name of c:\Program Files (x86)\McAfee\ePolicy Backup. Therefore, once the DR process is complete and any configuration files pointing to the now incorrect 8.3 path are restored, ePO will not work correctly.
     

Solution

Perform another Disaster Recovery, following the steps in KB66616. However, prior to following these steps, locate the exact Program Files directory that ePO is being installed to and remove any folder in the root of the McAfee folder that starts with ePolicy that is not the actual ePolicy Orchestrator folder being used by the current ePO installation.  

Examples:
c:\Program Files\ePolicy Orchestrator Backup
OR
c:\Program Files (x86)\ePolicy backup
OR
d:\Program Files\epolicy

NOTE: Prior to reinstalling ePO, there should be no folders in the McAfee directory that start with the name ePolicy.

Once ePO is reinstalled, the 8.3 name of the ePolicy Orchestrator folder should be EPOLIC~1, and will match the 8.3 path contained in all of the configuration files backed up prior to uninstalling ePO. In this case, this same issue should not be seen after the DR process is complete.
 

Solution

Change the path for all config files that were recovered during the DR process (referenced in step 2 of the "Backing Up" section in KB66616) to point to the new 8.3 path.  
 
Use the following process to determine the correct 8.3 path for the current ePolicy Orchestrator installation directory on the ePO server:

  1. Click Start, Run, type cmd and click OK.
  2. Change to the McAfee Directory (for example: cd c:\program files (x86)\McAfee).
  3. Use the Dir /x command to view the 8.3 names of all folders in the McAfee directory.
     
    NOTE: Given the issue, the 8.3 name listed at this point will likely be EPOLIC~2, so the full path will look similar to: C:\PROGRA~2\McAfee\EPOLIC~2

  4. Open the following files in a text editor, locate the lines specified for each, and change the paths to reflect the correct/current 8.3 path determined in the previous step:

    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\APACHE2\conf\httpd.conf

    • ServerRoot
    • DocumentRoot 
    • <Directory
    • ErrorLog 

    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\APACHE2\conf\ssl.conf 

    • DocumentRoot 
    • ErrorLog  

    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\conf\epo\epo.properties

    • epo.install.dir
    • epo.db.dir

    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\conf\orion\log-config.xml

    • change the paths on the lines starting with <param name="File"

    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\conf\orion\orion.properties

    • extension.install.dir
    • extension.tmp.dir

     

Solution

Change the 8.3 name for the ePO installation directory back to the original, and then change the 8.3 path for all files and registry key entries listed below, which will have been created during the fresh ePO installation during the DR process:
  1. Click StartRun, type services.msc, and click OK.
  2. Right-click each of the following ePO services and select Stop:
    • McAfee ePolicy Orchestrator Application Server
    • McAfee ePolicy Orchestrator Event Parser
    • McAfee ePolicy Orchestrator Server
       
  3. Click Start, Run, type explorer and click OK.
  4. Navigate to: ..\Program Files\McAfee\
  5. Delete any backup folders in the McAfee directory (for example: ..\Program Files\McAfee\ePolicy Backup), leaving only the ePolicy Orchestrator directory being used by the current installation.
  6. Rename the ePolicy Orchestrator directory being used by the current installation so that the first eight characters are changed (for example: c:\Program Files\New_ePolicy Orchestrator).

    A dir /x list command should look similar to the following:

    *************
    c:\Program Files (x86)\McAfee>dir /x
     Volume in drive C has no label.
     Volume Serial Number is 948C-0BDC

     Directory of c:\Program Files (x86)\McAfee

    04/21/2014  10:19 AM    <DIR>                       .
    04/21/2014  10:19 AM    <DIR>                       ..
    01/29/2014  01:36 PM    <DIR>          COMMON~1     Common Framework
    03/20/2014  09:31 AM    <DIR>          NEW_EP~1     New_ePolicy Orchestrator
    06/18/2013  04:12 PM    <DIR>          VIRUSS~1     VirusScan Enterprise
                   0 File(s)              0 bytes
                   3 Dir(s)   1,091,317,760 bytes free
    *************
     
  7. Rename this folder back to ePolicy Orchestrator. This should change the 8.3 path back to the original. A dir /x should look similar to the following:

    **************
    c:\Program Files (x86)\McAfee>dir /x
     Volume in drive C has no label.
     Volume Serial Number is 948C-0BDC

     Directory of c:\Program Files (x86)\McAfee

    04/21/2014  10:19 AM    <DIR>                       .
    04/21/2014  10:19 AM    <DIR>                       ..
    01/29/2014  01:36 PM    <DIR>          COMMON~1     Common Framework
    03/20/2014  09:31 AM    <DIR>          EPOLIC~1     ePolicy Orchestrator
    06/18/2013  04:12 PM    <DIR>          VIRUSS~1     VirusScan Enterprise
                   0 File(s)              0 bytes
                   3 Dir(s)   1,091,317,760 bytes free
    **************
     
  8. Open the following files in a text editor, locate the lines specified for each, and change the paths to reflect the correct/current 8.3 path determined in the step above, which were created by the new installation:

    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\bin\setenv.bat

    • Djava.security.auth.login.config==
    • set JRE_HOME=
     
    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\bin\setenv.sh

    • export CATALINA_HOME=
    • Djava.security.auth.login.config==
    • export JRE_HOME=
     
  9. Navigate to the following registry keys, locate the values specified for each, and change the paths to reflect the correct/current 8.3 path determined in the step above:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\MCAFEETOMCATSRV250\Parameters\Java]

    • Classpath  (There are several paths that need to be updated in this multi-string)
    • JavaHome
    • JVM
    • Options

    [HKLM\Software\Network Associates\ePolicy Orchestrator\]

    • ApacheFolder 
    • DBFolder
    • DBPropsFile
    • InstallFolder
    • ServerINI
    • TomcatFolder

    [HKLM\Services\CurrentControlSet\Services\MCAFEEAPACHESRV\]

    • ImagePath
       

    [HKLM\Services\CurrentControlSet\Services\MCAFEEEVENTPARSERSRV\]

    • ImagePath
       

    [HKLM\Services\CurrentControlSet\Services\MCAFEETOMCATSRV250\]

    • ImagePath
       

    (NOTE: The paths listed for the above service keys might be using the long path name (ie...c:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\bin\tomcat5.exe")  In this case, it is not necessary to change the path, assuming it is correct)

     

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.