Distributed Edition - Trobleshooting Doc [INTERNAL]
Check if there is a Registration Issue exist:
1) In Managed Server, Run a RegistrationWithAdminServer.bat located on <Home_ela>/troubleshooting on comment prompt as administrator.
1) In Managed Server, Run a RegistrationWithAdminServer.bat located on <Home_ela>/troubleshooting on comment prompt as administrator.
note:
1) We need to open the webserver port bidirectionally both in admin and managed server or via VPN and optimal functionality by opening the port in the firewall.
1) We need to open the webserver port bidirectionally both in admin and managed server or via VPN and optimal functionality by opening the port in the firewall.
2) Using a Fully Qualified Domain Name (FQDN) as the hostname for the multiple server communication is not recommended; it is recommended to use either the IP address or the host name.
Troubleshooting Steps:
1) Reachability: Check whether both Admin Server and Manage Server are Up and pingable bidirectionally.
2) Connectivity: Check whether Admin Server Console can be accessed in Manage Server Machine and vice versa.
3) Build : Check Whether Admin Server Build and all Manage Server's Build are same.
4) Enterprise.txt : Check whether Enterprise.txt values are correctly present.
adminserver.webserver.port = Admin Server running Port.
adminserver.webserver.protocol = Admin Server running Protocol.
webserver.protocol = Managed Server running protocol.
webserver.port = Managed Server running port.
server.startidrange = Managed Server using startid.
isCentralArchiveEnabled = set true if Customer using Centralised Archives.
CollectorIP = Manage Server IP address. This parameter will not present if default hostname is used.
adminserver.hostname = Admin Server Name.
DisablePPMCheck = Set this option to false to enable the registration check with the admin server during the upgrade. Set it to true to disable the registration check when the admin server is down those you can start manual upgrade.
i) Query to find the Manage Server using Startid : select * from seqgenstate where seqname='server.startidrange'
i) Case 1
Query to find the managed server details - hostname, startid, port, protocol, SSL enabled status in Admin Server : Select * from Collectors (Refer to image)
The CollectorIP value in the managed server enterprise file and the hostname column in the admin server collectors table need to be the same.
If not same, edit correct details in managed server enterprice.txt and restart the managed server or update in Admin Server Manage Server Settings page.
ii)Case 2
Change in IP and hostname on managed server
If any changes in port and protocol alter that changes in Enterprise.txt file in EventLog Analyzer managed server and restart the EventLog Analyzer managed server and change managed server details in "Edit user logon details" in admin server.
Change in IP and hostname in admin server
If any changes in port and protocol alter that changes in Enterprise.txt file of all EventLog Analyzer managed server and restart the all EventLog Analyzer managed server.iii)Case 3
Update the password of the managed Server in Admin Server "manage setting page"
If the Sync Succeeded No. Of Device and Time Zone will appears.
iv) case 4
Check the Admin Server UI can open in Managed Server RDP and vice-versa.
v) case 5
Check the AV port blockage on both AS and MS
New to ADSelfService Plus?
Related Articles
How to migrate EventLog Analyzer standalone edition to different server or drive [Windows to Windows]
Objective This article provides a detailed step-by-step guide to migrate EventLog Analyzer Standalone instance (not integrated with Log360) to a new server or different server or drive. Prerequisites Refer to the System Requirement to plan the new ...IIS Issue Troubleshooting [INTERNAL]
Issue 1 : Site "Failed" status Scan the IIS Server in which the site status is Failed in IIS Server pages. You can get the IIS Log Folder name from Log Directory. eg : W3SVC4 Search in ELA serverout for that Log folder trace followed by "File does ...How to migrate EventLog Analyzer standalone edition to different server or drive [Linux to Linux]
Objective This article provides a detailed step-by-step guide to migrate a EventLog Analyzer standalone instance (not integrated with Log360) to a new server or a different drive. Prerequisites Refer to the System Requirements to plan the new server ...How to apply a license file in EventLog Analyzer
Objective This article explains how to apply a license file in both the standalone and distributed editions of ManageEngine EventLog Analyzer. For details about the different license types, refer to license details. Prerequisites For standalone and ...ELA Distribution Upgrade to Latest
How to: Upgrading EventLog Analyzer (*Distributed Edition) to the latest Service Pack. Note: A folder backup or a snapshot of the Admin and the Managed Server VMs is MANDATORY. If the backend database is customer's MSSQL, it is recommended to take a ...