Issue description
The ADSelfService Plus service fails to start on the hosted server. Users and administrators are unable to access the application, impacting functionality across the organization. No specific error messages may be displayed, making the root cause less apparent.
Possible causes
Service not installed: The service may not be properly installed on the system.
Application already running in console mode: If the application is already running manually in console mode, the service cannot start simultaneously.
Invalid service logon credentials: The credentials configured under the service logon may have expired or changed.
Permission issues: The installation directory may not have the necessary read/write/execute permissions.
Corrupted files or database: Critical application or database files in the installation directory may be damaged.
Failed database migration: An incomplete or failed migration from an older instance to a new instance may prevent the service from initializing properly.
Prerequisite
Resolution
Step 1: Check service installation
Open services.msc and verify if ManageEngine ADSelfService Plus is listed.
If the application is missing, reinstall it. Alternatively, you can manually register the service by running the command InstallNTService.bat in the Command Prompt. Open the Command Prompt with administrative privileges before executing the command.
Step 2: Ensure the application is not running in console mode
Open Task Manager and check if ADSelfService Plus is already running. You can also check the system tray for the ADSelfService Plus icon.
If yes, terminate it and try starting the service again.
Step 3: Verify service logon credentials
In services.msc, right-click the ManageEngine ADSelfService Plus service, then go to Properties > Log On.
Ensure the configured account used has valid credentials and necessary privileges.
Reenter the credentials if required and click Apply.
Step 4: Check folder permissions
Navigate to the installation directory (default: C:\Program Files\ManageEngine\ADSelfService Plus\). Ensure the service account has full control over this directory and subfolders.
Step 5: Inspect for file or database corruption
Look for any error logs under <Installation_Dir>\logs.
If corruption is detected, consider restoring from a known good backup.
Step 6: Validate database migration (if applicable)
Ensure that database migration was completed successfully.
Rerun the migration tool if necessary and check logs for success or failure status.
How to reach support
If the issue persists, contact our support team here.