Troubleshooting

If Symphony DE does not start up correctly, take a look at this section for troubleshooting.

Non-administrative user cannot install

The following error message may indicate that the system administrator has set policies to prevent the installation of software by non-administrative users.
The system administrator has set policies to prevent this installation
  • Ask your Windows local administrator to set group policy to allow users to install software.

Cannot access Platform Management Console

The Symphony DE Platform Management Console is not supported on Solaris.

When you launch Symphony on Linux, you see a message that the page cannot be displayed.

  • To check for port conflicts, see %SOAM_HOME%\gui\logs\catalina.out (Windows) or $SOAM_HOME/gui/logs/catalina.out (Linux/UNIX).

    Important:

    Symphony DE must be restarted if port numbers are changed.

  • To change port numbers that are in conflict, refer to Change port numbers.

Port conflicts during soamstartup

The following error message may indicate there are port conflicts.
Failed to start the Symphony process on the local host, please check logs ...
  • To see which port numbers have conflicts, check the files in %SOAM_HOME%\logs on Windows or $SOAM_HOME/logs on Linux/UNIX.

    Important:

    Symphony DE must be restarted if port numbers are changed.

  • To change port numbers that are in conflict, refer to Change port numbers.

Environment variables

You cannot start up Symphony DE or run commands if your environment variables are not set correctly.

Windows

  • Ensure the SOAM_HOME environment variable is set to your Symphony DE installation directory. From the command prompt, enter:

    echo %SOAM_HOME%

  • From the command prompt, enter echo %Path% and ensure the following is in your Path environment variable: %SOAM_HOME%\4.1\win32-vc7\bin;%SOAM_HOME%\4.1\win32-vc7\etc;%SOAM_HOME%\4.1\win32-vc7\lib\

Note:

System settings change when you install Symphony DE 4.1 on the same host as the previous version of Symphony DE.

Linux/UNIX

From the command shell if you enter env, the following environment variables are set to your current environment.

For example, on Linux:

  • LD_LIBRARY_PATH=$SOAM_HOME/4.1/linux2.x-glibc2.x-x86/lib

  • LIBPATH=$SOAM_HOME/4.1/linux2.x-glibc2.x-x86/lib

  • PATH=$SOAM_HOME/4.1/linux2.x-glibc2.x-x86/bin: $SOAM_HOME/4.1/linux2.x-glibc2.x-x86/etc

  • SOAM_BINDIR=$SOAM_HOME/4.1/linux2.x-glibc2.x-x86/bin

  • SOAM_HOME=$SOAM_HOME

  • SOAM_SERVERDIR=$SOAM_HOME/4.1/linux2.x-glibc2.x-x86/etc

MD5 checksum failure

Under some circumstances, RPM cannot verify the MD5 checksum. In these cases RPM fails because it cannot unpack the Symphony DE archive. Re-enter the command with the --nomd5 option. For example
rpm -ivh ‑‑dbpath /usr/soam/db ‑‑prefix /usr/soam symphonyDE‑linux2.6‑glibc2.3-x86-4.1.0-build_number.rpm ‑‑nomd5

RPM versions 4.2 and 4.1

RPM database directory must exist and the ‑‑prefix option does not work

The RPM database directory, as --dbpath specifies, must exist on the local disk before installing. Also, these RPM versions do not support the rpm --prefix option. RPM uses the RPM_INSTALL_PREFIX to determine the installation directory. To install in a different directory, set RPM_INSTALL_PREFIX so that RPM can install Symphony DE to the specified destination directory.

For example, to install Symphony DE to /opt/symphonyDE/DE41:
mkdir /opt/symphonyDE/DE41/db
setenv RPM_INSTALL_PREFIX /opt/symphonyDE/DE41
rpm -ivh --dbpath /usr/share/soam/db symphonyDE-linux2.6-glibc2.3-x86-4.1.0-build_number.rpm

RPM blocks during installation

For RPM 4.2, log on as root and delete all files in /var/lib/rpm prefixed with _db.00.

Cannot get shared lock

RPM 4.1.1 cannot install on a Quadrics Resource Management System (RMS) kernel. RPM cannot get a shared lock in this environment, so it cannot update the RMS data base directory.

Restart your system under a different kernel to install Symphony DE. After installing, you can restart the RMS kernel.

RPM version 3.0.6

The RPM database directory you specify with the --dbpath option must exist on the local disk before installing. You must also specify the --nodeps option

For example, to install Symphony DE on SuSE Linux Enterprise Server 9
mkdir /opt/symphonyDE/DE41/db
setenv RPM_INSTALL_PREFIX /opt/symphonyDE/DE41
ln -s ./opt/symphonyDE/DE41 /soam 
rpm -iv --dbpath /opt/symphonyDE/DE41/db --prefix /soam symphonyDE-linux2.6-glibc2.3-x86-4.1.0-build_number.rpm --nodeps

If you install Symphony DE using the customized dbpath, then when you uninstall DE ensure that you use the same dbpath.