Issue description   

ADManager Plus may sometimes fail to start, either displaying an error message while initiating as a console or stopping unexpectedly during the startup process. This issue can disrupt administrative tasks and delay critical operations.  

• The application stops or crashes unexpectedly while launching.

• Services fail to initialize properly.  

Identifying the root cause and resolving the issue promptly is essential to ensure uninterrupted access to ADManager Plus.

Possible causes   

This issue may occur due to one or more of the following reasons:

• Port conflicts: ADManager Plus ports are in use by another application.

• Database issues: External database is down, unreachable, or misconfigured.

• Insufficient permissions: The PostgreSQL database may fail to start due to inadequate permissions, or Windows Authentication in Microsoft SQL may lack the necessary access. The service account used to run the ManageEngine ADManager service mush have Full Control permission for the ADManager Plus folder.

• Background processes: Residual ADManager Plus processes (Java, PostgreSQL) are preventing a clean restart.

• Insufficient system resources: Low memory, CPU, or disk space.

• Corrupt or missing application files: Installation files may be damaged or deleted.

• High availability: The file mirroring task failed. 

• SSL configuration: SSL misconfiguration or certificate expired.

• Logon failure: Due to the service account password expiring. 

Prerequisites   

Before troubleshooting, ensure:

• You have full control access to the ADManager Plus installation folder.

• The server meets the system requirements for ADManager Plus.

• Database connectivity (if an external database is utilized).

Resolution 

Follow the steps below to identify and resolve exceptions.  

Step 1: Check logs for exceptions  

1. Review wrapper.log. 

2. Navigate to <ADManager Plus Installation Directory>/logs/wrapper.log.

• Exception: Port 8080 already in use. Change WebServer port in <ProductHome>/conf/server.xml

• Cause: The port is already in use.

• Solution:

1. Open the Command Prompt as an administrator.

2. Run the following command to check if ADManager Plus ports (default: 8080, 8443) are occupied:

• netstat -ano | findstr :8080

• netstat -ano | findstr :8443

3. If another process is using the port, identify it using

• tasklist | findstr <PID>

4. Either terminate the conflicting process or change ADManager Plus to use a different port.

5. To change the port manually, follow these steps:

1. Navigate to the ADManager Plus installation directory (C:\ManageEngine\ADManager Plus\conf).

2. Open the server.xml file in a text editor.

3. Locate the following line: <Connector port="8080" protocol="HTTP/1.1"

4. Change the port number to an available port (e.g., 8090).

5. Save the file and restart ADManager Plus.

If no exceptions are found, proceed to Step 2.  

Step 2: Check serverout.log for the current day  

• Open serverout_<current_date>.txt (e.g., serverout_20231001.log).  

2. Search for exceptions, use keywords like Exception, Error, or specific phrases from the error message.

3. If exceptions are found, refer to the matching exception below and perform the resolutions mentioned.  

4. If no exceptions are found, contact support with logs for further analysis.  

Step 3: Cross-check the exceptions and errors you encounter with the following

1. SQL connection issues   

• Error message: Check that the hostname and port are correct and SQL Server is accepting connections.

• Exception: NFO | jvm 1 | Check that the hostname and port are correct...

• Logs to check: wrapper.log and serverout.log

• Cause: Unstable SQL connection.  

• Solution:  

1. Verify database configuration:  

1. Open ADManager Plus Installation Directory/conf/database.conf.  

2. Confirm the database type, hostname, port, username, and password.  

1. Test connectivity:  

1. From the ADManager Plus server, run:

• Test-NetConnection <DB_IP> -Port <DB_PORT>  

If it fails, check if the Microsoft SQL service is running and the port is open in the firewall.

2. Database access denied  

• Error message: Cannot open database 'ADMP' requested by the login. The login failed.  

• Exception: Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open database...

• Logs to check: serverout.log  

• Cause: Incorrect credentials or permissions.  

• Solution:  

1. Verify the database credentials:  

1. Check database.conf for the correct username and password.  

2. Validate permissions:  

1. Ensure the login has access to the ADMP database in SQL Server.  

3. Disk space issues  

• Error message: There is not enough space on the disk.  

• Exception: java.io.IOException: There is not enough space on the disk  

• Logs to check: serverout.log and wrapper.log

• Cause: Low disk space.  

• Solution:  

1. Check system resources:  

1. Free up space on the drive where ADManager Plus is installed.  

2. Ensure at least 20% of the disk space is available.  

4. PostgreSQL startup failures  

• Error message: Trying to start PostgreSQL server failed.

• Exception: Caused by: java.lang.RuntimeException: Trying to start PostgreSQL server failed

• Logs to check: serverout.log

• Cause: Insufficient permissions.  

• Solution:  

1. Verify permissions:  

1. Grant Full Control to the ADManager Plus service account over the installation directory.  

2. Restart the PostgreSQL service:  

1. Open services.msc and restart the PostgreSQL service.  

5. File mirroring failure  

• Error message: ERROR 5 (0x00000005) Getting File System Type of Source.

• Exception: java.lang.RuntimeException: Error in replication directory

• Logs to check: fileRepl.txt

• Cause: Insufficient permissions.  

• Solution:  

1. Verify directory permissions:  

1. Ensure the ADManager Plus service account has Read and Write access to the source and target directories.  

6. Out of memory errors  

• Error message: ERROR: out of memory Detail: Failed on request of size 280.

• Exception: org.postgresql.util.PSQLException: ERROR: out of memory...

• Logs to check: serverout.log and PostgreSQL logs  

• Cause: High memory usage or insufficient RAM.  

• Solution:  

1. Check system resources.  

2. Increase JVM heap size (via wrapper.conf ).  

3. Upgrade server RAM if required.

If the issue persists after following these steps, contact support@admanagerplus.com with logs and error details.  

Tips 

• Assign a dedicated port to prevent conflicts with other applications.

• Set up alerts to monitor external database availability and performance.

• Allow ADManager Plus in antivirus and firewall to avoid disruptions.

• Perform regular backups of configurations and the database for quick recovery.

• Always stop ADManager Plus to prevent data corruption.

• Configure automatic service restart using the services.msc recovery option.

• Use Windows Performance Monitor (perfmon) to track system resource usage.

How to reach support