When I try to start Applications Manager, it says ' Applications Manager is already running'. This happens even after I've verified that Applications Manager is not running.
Reason:
The system in which the Applications Manager has been installed would have been accidentally restarted or shutdown. The file am.lock may remain in the folder <AppManager_Home\working> to say that Applications Manager is running.
Solution:
If you are sure that Applications Manager is not running, then delete the file<am.lock> in <AppManager_Home>/working/> directory if it exist. Restart Applications Manager.
If still you have the same problem try to stop AppManager. Via command prompt goto AppManager_home directory and execute the command shutdownApplicationsManager.bat / .sh -force and restart AppManager.
New to ADSelfService Plus?
Related Articles
Applications Manager default tomcat is down
If your Tomcat Monitor is down, it could probably be due to changes in Hostname/IP address of the machine in which Applications Manager is installed. You can verify the same using the steps given below: Navigate to ...'Manager' application needs to be running in Tomcat server for Applications Manager to collect data from the Server. How can I enable the Manager application?
An application named Manager must be running in Tomcat Server Versions 5.x & above for Applications Manager to monitor the server. By default, this application will be running in the server. To check if it is already running, open the following url ...Oracle Server is running but when I try to add through Applications Manager it is saying "Service is not running".
Solution: Kindly do the following checks: 1) The "Connect String" given when you are connecting through the SQLPlus should be given as Database Name in Applications Manager. 2) Kindly check whether the "Database Name" that you have given is properly ...Applications Manager quits at startup with the message "Port :9090 needed by Applications Manager is being used by some other application. Please free the port and restart Applications Manager."
Reason 1: When Applications Manager is started, its Web Server (Apache) starts in port 9090 by default. If the port is occupied by other applications, you will not be able to start Applications Manager. Reason 2: You have shutdown Applications ...How to start/stop Applications Manager in Linux?
Starting Applications Manager From the command line, go to <Applications Manager Home> directory (by default it is /opt/ManageEngine/AppManager14) and execute the below command to start the product: nohup sh startApplicationsManager.sh & Execute the ...