Reason 1: If your system date is set to a future or a past date, you will get this error message.

Solution: Uninstall Applications Manager, set the system date settings to current date and time and re-install it.

Reason 2: You might have applied the Professional Edition License in the Enterprise Edition Server.

Solution: You can check in <Applications Manager Home>/conf/install.txt or <Applications Manager Home>/conf/AMServer.properties file. Here check for am.server.type (AAM for Admin Server, MAS for Managed Server, NORM for Professional Server). If you have got License for Professional Edition, you need to choose Applications Manager as Professional Edition instead of Enterprise Edition while installing the product.

Also, make sure that the license file is not corrupted. If the problem persists, contact appmanager-support@manageengine.com with your license and contact information.

Reason: When Applications Manager is started, its Web Server (Tomcat) starts in port 9090 by default. If the port is occupied by other applications, you will not be able to start Applications Manager.

Solution: You have shutdown Applications Manager and tried to restart it but it's old instance/process are still running. If so:

• For Windows installation, make sure that the corresponding ManageEngine Applications Manager service is stopped.
• Kill Applications Manager and restart it. (To kill Applications Manager, open command prompt and goto <Applications Manager Home> directory and execute the command shutdownApplicationsManager.bat / .sh -force)

If the problem persists, contact appmanager-support@manageengine.com with support information file and contact information.

Reason: This is because the absolute path of the working directory will be updated in server.xml and tomcat server will not start if non-english charaters are present in server.xml.

Solution: As of now, Applications Manager should be installed in a directory that has english characters only.

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 <Applications Manager 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 <Applications Manager Home>/working directory if it exist. Restart Applications Manager.

If still you have the same problem try to stop AppManager. Via command prompt, go to <Applications Manager Home> directory and execute the command shutdownApplicationsManager.bat / .sh -force and restart AppManager.

Reason: For the Applications manager to run, all the server main process should start. Some process has problem in starting, in this case

Solution:

Linux Installation: Use shutdownApplicationsManager.sh with force option found under <Applications Manager Home> by executing the command "sh shutdownApplicationsManager.sh -force" from the command prompt and stop the corresponding ManageEngine Applications Manager service. Try starting ManageEngine Applications Manager service now using sh startApplicationsManager.sh command from command prompt.

Windows Installation: Use shutdownApplicationsManager.bat with force option found under <Applications Manager Home> by executing the command "shutdownApplicationsManager.bat -force" from the command prompt and stop the corresponding ManageEngine Applications Manager service. Try starting ManageEngine Applications Manager service now using startApplicationsManager.bat command from command prompt.

If it is still not working, send Support Information File to appmanager-support@manageengine.com

Reason: You may have logged into Applications Manager with user access as 'Operator' or 'User'. With the Operator or User roles, you can only view Monitor details. You will not have the privilege to configure or edit the different components of the product.

Solution: To work with or configure the product, log in as 'Admin' user. For more information on user access, refer to the User Administration section in the User Guide .

This could be because the DNS name of the machine would not have been configured in their DNS Server. In this case, use the machines' IP Address to connect to the client.

Reason: Your PC's time zone ( eg: French ) is different from Applications Manager's java time zone (eg: GMT).

Solution: Follow the steps given below to set the Applications Manager's clock to a time zone different from that of the server time zone.

1. Stop Applications Manager using command "shutdownApplicationsManager.bat -force"

2. Edit the startApplicationsManager.bat / startApplicationsManager.sh file in Notepad/Wordpad present under the <Applications Manager Home> directory. In this file, add the entry -Duser.timezone=CET in the following lines (depending upon your time zone you have to use either EST / CST / MST / PST in the "-Duser.timezone" attribute)

In Windows (startApplicationsManager.bat)

start /B %JAVA_HOME%\bin\javaw -cp %CLASSPATH% -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=%TOMCAT_HOME%\conf\logging.properties -Duser.timezone=CET -Dfile.encoding=UTF-8 -Dhttps.protocol=TLSv1.2,TLSv1.1,TLSv1 -Dcom.sun.jndi.ldap.object.disableEndpointIdentification=true -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Xms64m -Xmx1024m -XX:MetaspaceSize=64m -XX:MaxMetaspaceSize=256m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=%NMS_HOME%\heapdump com.adventnet.appmanager.server.startup.StartServer %exit_code% > %outfile%

In Linux (startApplicationsManager.sh file)

JAVA_OPTS="-Duser.timezone=CET -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=$TOMCAT_HOME/conf/logging.properties -Dcatalina.home=$TOMCAT_HOME -Dfile.encoding=UTF-8 -Dhttps.protocol=TLSv1.2,TLSv1.1,TLSv1 -Dcom.sun.jndi.ldap.object.disableEndpointIdentification=true -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true"

If Applications Manager is installed as a Windows service, you have to add a new entry in the <Applications Manager Home>/working/conf/wrapper.conf file as shown below:

# Java Additional Parameters
wrapper.java.additional.2=-Dfile.encoding=UTF-8
wrapper.java.additional.3=-XX:PermSize=64m -XX:MaxPermSize=128m
wrapper.java.additional.4=-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
wrapper.java.additional.5=-Djava.util.logging.config.file=apache/tomcat/conf/logging.properties
wrapper.java.additional.5=-Duser.timezone=CET

#Parameter to disable ldap endpoint identification

wrapper.java.additional.31=-Dcom.sun.jndi.ldap.object.disableEndpointIdentification=true

wrapper.java.additional.32=-Duser.timezone=CET

Start Applications Manager. Applications Manager's clock will now show French timezone.

Solution:
Follow the steps given below to generate Support Information File (SIF) in Applications Manager:

• The log files are located in <Applications Manager Home>/logs directory. If the Logging level in Settings tab → Logging → is not 'Print all logs', then change it to 'Print all logs' and reproduce the issue once. Ignore this step if product GUI is not accessible.
• If the product is running and the web client is accessible, navigate to Settings tab → Support link → Create SIF link under Support Information table. Then fill up the required information and submit using the "Create Support Information File" button to create the file.
• To create support information file via command prompt with administrator permission, execute createSupportFile.bat or createSupportFile.sh (in case of Linux) file present under <Applications Manager Home>/bin directory. The support information file along with time stamp will be in <Applications Manager Home>/working/support directory.
• If the Support Information file is less than 2GB, upload it to ManageEngine Upload site. Do mention the issue and Ticket ID before uploading the file.

Existing customers: https://bonitas.zohocorp.com/#to=appmanager-support@manageengine.com

Evaluation users: https://bonitas.zohocorp.com/#to=eval-apm@manageengine.com

• Once you have uploaded the file, contact appmanager-support@manageengine.com (for existing customers) or eval-apm@manageengine.com (for trial users) with the name/location of the file.

To migrate from one machine to a different machine, please follow the steps given here.

Error:

FATAL: could not create semaphores: No space left on device

DETAIL: Failed system call was semget(xx, xx, xxxxx).

Reason: The reason could either be that there was no disk space or there were too many PostgreSQL connections open.

Solution: Check if sufficient free disk space is available for Applications Manager to start. Try stopping any old PostgreSQL instance or Applications Manager instance in the machine (if it is already running). Refer steps here for stopping old instances and then check if still the startup fails.

If you are still unable to start Applications Manager using bundled PostgreSQL, then send us the support information file.

Steps to change the password of a “Postgres” user account:

• Shut down Applications Manager.
• Open the Command Prompt as Administrator and go to the Applications Manager installation directory ($<Applications Manager Home>/working)
• Run startPGSQL.sh/startPGSQL.bat to start the PostgreSQL database.

  Example:

  Windows Command:

  <Applications Manager Home>\working\bin>startPGSQL.bat

  Linux Command:

  <Applications Manager Home>/working$./bin/startPGSQL.sh

• Once the server has started, go to the PostgreSQL directory and execute the following command to connect with postgres database: (Get the postgresql database running port from AMServer.properties file in <Applications Manager Home>/conf directory. Key is am.db.port)

  Windows Command:

  <Applications Manager Home>\working\pgsql\bin>psql -p 15432 -U postgres -h localhost -d postgres

  Linux Command:

  <Applications Manager Home>/working/pgsql/bin$./psql -p 15432 -U postgres -h localhost -d postgres

• Once connected with database, execute the following query:

  postgres=# ALTER USER postgres WITH PASSWORD ‘DBNewPwd’;

  postgres=# \q

• Go to the directory where Applications Manager is installed and open “database_params.conf” file under directory $<Applications Manager Home>/working/conf.
• Edit the following line and replace the existing password with new one:

  Existing Line :

  # login password for the database if any

  encryptedpassword eK6q1CJ9697s7O AppModules TopoDB-MapDB-EventDB-AlertDB-PollDB-PolicyDB-USERSTORAGEDB-ApplnDB

  Line with the new password :

  # login password for the database if any

  password DBNewPwd AppModules TopoDB-MapDB-EventDB-AlertDB-PollDB-PolicyDB-USERSTORAGEDB-ApplnDB

• Shut down Applications Manager again to terminate the existing database connection and restart it.

Solution: It is a simple warning message. You can ignore it.

Solution: Check if your host name contains any non-standard characters such as '_', ',', '.', or '@'. If any of these characters are present in your host name, Internet Explorer will block any attempts to set cookies on such domains.

Refer this link to know more about DNS naming conventions.

To access the Applications Manager web client, follow any of the steps given below:

• Access the web client through Firefox browser. Firefox supports host names with non-standard characters.
• Get a DNS alias to access the web client.
• Access the Applications Manager web client by replacing the host name with the IP address of the host.
• Rename the server where Applications Manager is installed.

Reason: This occurs when the DISPLAY variable is not set.

Solution 1: If you are installing the product in a non-GUI environment, execute the bin file as given below:

./ManageEngine_ApplicationsManager.bin -console

Solution 2: If you are installing the product in a GUI environment, set the DISPLAY variable and then install the product.

Example:

export DISPLAY=localhost:0.0 [To set the DISPLAY variable]

xhost + [To provide permission for the remote hosts to open the GUI]

./ManageEngine_ApplicationsManager.bin

Solution:
For silent installation, execute the installer (.bin) file as below:

<Installation file(.bin )> -silent -options ismp_silent.txt

For eg: .../AppManagerXX$ ./ManageEngine_ApplicationsManager_64bit.bin -silent -options ismp_silent.txt

The options which you normally enter while installation is stored in a text (reference) file which is provided in the -Options flag. Check the attached sample reference files:

Or use the Reference Template file and modify it as per your installation requirements:

Reason: As the product is installed in /root directory, you need to provide execute permission to /root to access the web client.

Solution: To provide permission use the following command (as superuser): chmod +x root from / directory

Reason: This is because some of the files in <Applications Manager Home>/working/mysql/data/AMDB/ will have permissions for the root user only.

Solution: Give all permissions for all the files and folders in Applications Manager for normal user by using chmod command.

Reason: This could be because you are trying to install a 64 bit version of Applications Manager on a 32 bit OS. Please make sure the Applications Manager binary that you have downloaded matches that of the OS where you are trying to install it.

Solution: Please comment out or remove the IPv6 address entry in the /etc/hosts file and then try to restart the product.

Example:

#::1   localhost6.localdomain6 localhost6

Problem: Charts/Graphs display junk characters in several places.

Reason: Applications Manager uses core Microsoft text fonts in graphs and charts. These fonts may be missing from your Linux machine.

Solution: Install Microsoft fonts and then restart your machine.

Please try to complete the installation from command prompt itself using the below command:

LANG=en_US.UTF-8 ./ManageEngine_ApplicationsManager_64bit.bin -console