A tool is attached to this article, which rebuilds the services according to the version of ePO detected.
NOTE: The tool doesn't work on a clustered ePO install. If you experience this issue on a clustered ePO environment, contact Support for assistance. See the "Related Information" section of this article.
Tool contents:
- Readme.txt file. The instructions from the Readme.txt file are listed below for reference.
- A batch file.
Instructions
- Reboot the affected ePO server or agent handler. This is necessary in case any services have been marked for deletion.
- Create a temporary folder on the affected ePO server or agent handler, for example, C:\RebuildSrv
- Extract ePO5_10_service_rebuild_v5.bat to the temporary folder.
- Open an administrator command prompt by right-clicking cmd.exe and choosing Run As Administrator.
- Navigate to the temporary folder, for example:
- Run the batch file by typing the following command and pressing Enter:
ePO5_10_service_rebuild_v5.bat
The tool works as follows:
- Detects the version of a core ePO file on disk—If it's unable to do so, it prompts you to re-run it in manual mode. If this happens, see the "Manual Mode" section below.
- Detects the amount of installed RAM—Again, if it's unable to do so, it prompts you to re-run it in manual mode. if this happens, see the "Manual Mode" section below.
- Backs up any existing service registry entries to the temporary folder
- Stops and removes any existing services—If it detects that any existing services are marked for deletion, it prompts you to reboot the system and then re-run it.
- Creates new services to match the file version and amount of RAM
- Starts the newly created services
The tool logs its progress to the window, and also writes
ePO5_10_Service_rebuild.log in the temporary folder where it's run from.
Once complete, the services should be running correctly. If required, you can reapply the update or service pack.
Manual Mode
If the tool is unable to detect the required file version, or the amount of installed RAM, it prompts you to run it again in manual mode, where it asks for a build number and the amount of RAM.
- To run the tool in manual mode, use the -manual switch. Run the batch file by typing the following command and pressing Enter.
ePO5_10_service_rebuild_v5.bat -manual
The tool asks you to enter the four-digit build number for
eventparser.exe:
To determine the build number, locate
eventparser.exe in the ePO install folder (by default:
C:\Program Files (x86)\McAfee\ePolicy Orchestrator):
- Right-click eventparser.exe and choose Properties.
- Select the Details tab, and find the File Version value.
- The build number is the last four-digit number. For example, if the file version is shown as 5.10.0.4159, the build number is 4159.
- Enter the build number and press Enter.
- If the tool is being run on the ePO server, it then asks for the amount of installed RAM in GB.
NOTE: You need to enter an integer value. For example, if the ePO server has 32 GB of RAM installed, enter 32 and press Enter. The ePO Application Server service will be configured to use a maximum of half the value specified, which is the default.
The tool then proceeds to steps 3–6 as described in the "Workflow" section above.
