Issue description   

Upgrade failure occurs when background processes from the ADManager Plus installation folder are still running. During an upgrade, if files within the installation directory are being accessed by other processes, the upgrade may fail. Additionally, if the technician performing the upgrade does not have full control permissions over all subfolders and files, the process may be obstructed.

To ensure a successful upgrade, it's crucial to terminate all background processes related to ADManager Plus and verify that the technician has full control access to the entire installation directory, including subfolders and files.

Possible causes   

1. Insufficient permissions: The system administrator account may have restrictions, while a local account works fine for executing the batch file.

2. GPO restrictions: Group Policy settings may be preventing the execution of batch files.

3. Security software blocking: Antivirus or Windows Defender might be blocking the batch file from running.

4. Corrupted PostgreSQL files: Damaged PostgreSQL files can prevent proper execution.

5. Windows updates impact: Recent Windows updates may have altered execution permissions.

Prerequisites   

• Ensure to run the Command Prompt using the same account that runs the ManageEngine ADManager Plus service.

• Take a backup of the ADManager Plus database and Installation folder.

• Ensure no other processes, such as antivirus or backup services, are locking the files.

Steps to identify the database type   

• For PostgreSQL:  

1. Navigate to the ADManager Plus installation directory (e.g., C:\Program Files\ManageEngine\ADManager Plus\Conf).

2. Open the conf folder and locate the database_params.conf file.

3. Check the database type mentioned in the file.

4. If it contains drivername=org.postgresql.Driver, ADManager Plus is using PGSQL.

• For Microsoft SQL Server:  

1. Navigate to the ADManager Plus installation directory.

• Open conf\database_params.conf.

2. Look for database connection details, such as SQL server name, username, and password.

3. If drivername=com.microsoft.sqlserver.jdbc.SQLServerDriver is mentioned, then ADManager Plus is using Microsoft SQL.

Resolution  

For PostgreSQL server:

1. Verify file permissions:

• Go to C:\Program Files\ManageEngine\ADManager Plus\pgsql.

2. Right-click on the pgsql folder > Properties.

3. Ensure the system, administrator, and the user performing the upgrade have Full Control.

4. Stop the ADManager Plus service.

5. Open the Command Prompt using the same account that runs the command:

• Stopadsm.bat

• stopdb.bat

• shutdown.bat.

6. Retry the upgrade process.

For Microsoft SQL Server:  

1. Check the database connectivity,

• Open SSMS.

2. Try connecting to the database using the service account credentials.

3. Ensure the service account has db_owner or sysadmin rights.

4. If needed, reset the SQL user password and update it in ADManager Plus by running updateMSSQLPassword.bat from the bin folder of ADManager Plus.

5. Stop the ADManager Plus service.

6. Retry the upgrade.

Tips  

• Always run the upgrade using the service account for ADManager Plus or an account with full folder permissions for the installation directory.

• Temporarily disable the antivirus and firewall if they interfere with installation.

• Take a server snapshot, and back up the database before upgrading.

• For Microsoft SQL, verify that Windows/SQL authentication possesses the necessary permissions to access the database.

How to reach support