ELA Upgrade to Latest | Online help - EventLog Analyzer

ELA Distribution Upgrade to Latest

How to:   Upgrading EventLog Analyzer (*Distributed Edition) to the latest Service Pack.

 

Note:

  1. A folder backup or a snapshot of the Admin and the Managed Server VMs
    is MANDATORY.

  2. If the backend database is customer's MSSQL, it is recommended to take a backup/snapshot of the MSSQL Database.

  3. The backup/Snapshot of ELA Servers and MSSQL instance/Server should not be deleted before confirming the upgrade status.

  4. The upgrade process should not be cancelled or interrupted. If the upgrade fails, the customer should contact Support at the earliest.

 

Important: For distributed edition, only the Admin Server should be upgraded. This will in turn upgrade the Managed Servers automatically.
Point to be noted: The Automatic Upgrade process of Managed Servers is time-consuming.

 

PPM file download link: <PPM download link>

 

The steps given below are to be followed in the Admin Server:

  1. Stop the ManageEngine EventLog Analyzer service in the Admin server.

  2. Open a command prompt with administrative privileges.

  3. In this cmd window, navigate to <dir>:\ManageEngine\EventLog Analyzer\bin and execute the following batch files to ensure that the instance is completely shut down.

    1. shutdown.bat

    2. stopDB.bat

    3. stopSEC.bat

  4. In the same location, execute "initPGSQL.bat". (wait until its completion)

  5. In the same location, execute "UpdateManager.bat".

  6. Click on "Browse" ⇾ select the appropriate ppm file. The below window will popup.

  1. Click on "Install" and wait for it to complete.

  1. Start the ManageEngine EventLog Analyzer service in the Admin Server.

  2. Log onto the GUI, click on "?" at the right-top corner, and check the build number, or the build number can be checked in the <Dir>:\ManageEngine\EventLogAnalyzer\troubleshooting\Build.properties file.

Finally, the Admin Server will automatically upgrade the Managed Servers but this is a time-consuming process (~20min per Managed Server). Hence, this automatic process should not be disturbed.
        New to M365 Manager Plus?
        New to M365 Manager Plus?
          New to RecoveryManager Plus?
          New to RecoveryManager Plus?
            New to Exchange Reporter Plus?
            New to Exchange Reporter Plus?
              New to SharePoint Manager Plus?
              New to SharePoint Manager Plus?
                  See all integrations
                  New to ADManager Plus?

                    New to ADSelfService Plus?

                    Start your free trial

                      • Related Articles

                      • How to upgrade the EventLog Analyzer Agent?

                        Usually, an agent upgrade would happen automatically if the credentials provided for agents under the "Manage agents" section are valid or has the appropriate rights for accessing services or logs in the agent machine. However, in recent builds ...

                      • What to do if the component inside Log360 is not loading?

                        Troubleshooting Steps: Please ensure that the connection is proper, if in case of a connection issue, the components will not load within Log360. Local Integration: It is less likely to be a connection issue, in case of local integration, because ...

                      • STATUS_MARKED_ROLLBACK in export

                        Issue: STATUS_MARKED_ROLLBACK in export Steps to fix: i) For postgres Database, download attachment<StatusMarkedRollback.txt> and rename file extension to .bat. 1. Copy patch statusMarkedRollback.bat to <ELA-HOME>\pgsql\bin folder. 2. Open Command ...

                      • License file on a Log360 Instance

                        How to: Applying a License file on a Log360 Instance Open the Log360 UI and login using the default/super admin credentials. Go to the Admin tab ⇾ Administration ⇾ Log360 Integration ⇾ click on "Sync Now" and ensure that all the required components ...

                      • File Integrity Monitoring Issues for Linux

                        Linux - File Integrity Monitoring Issues (FIM) Ensure that the Linux agent is installed in the respective machine. (Location: /opt/ManageEngine/EventLogAnalyzer_Agent) Check whether the agent service responds to the start and stop commands: To start: ...

                        Related Products