Solutions to Common Installation Problems

If this section does not describe the problem you are experiencing, see the Error Messages and Troubleshooting Guide.

Solutions to common installation problems
Problem Possible cause and solution
Cannot use X-Windows If the setup and configuration utilities do not display correctly, you may have to adjust the resolution on your monitor.
To change to a smaller font size, issue the following UNIX commands:
% cd $SYBASE/ASE-15_0
% chmod +w xappdefaults
% cd xappdefaults
% chmod +w *
% foreach i(*) 
? cat $i | sed -e "s/140/100/g" | sed -e "s/^#D/D/g" | sed -e "s/^#S/S/g" > p
? mv p $i
? end
%
The installation utilities will now use approximately 25 percent less window space.
Cannot eject the CD or DVD from the drive
If you cannot eject the CD from the drive, check:
  • To see whether the CD drive path is the current directory (pwd) in a UNIX terminal window. If it is, change (cd) to another directory.
  • For sybhelp processes. If these processes exist, kill them using the UNIX kill command.
DISPLAY environment variable not set correctly This error message means that the DISPLAY environment variable on the remote machine is not set correctly to display the installer to your local machine:
The DISPLAY environment variable is not set correctly.
To correct the problem, enter the following command at the UNIX prompt of the remote machine, where host_name is the name of the machine on which you want the installer to appear (that is, on your local machine):For C shell:
setenv DISPLAY host_name:0.0
For Bourne shell:
DISPLAY=host_name:0.0; export DISPLAY
Client not authorized to connect to server
If you run the installer and you get this error message, it means the remote machine does not have permission to display the user interface on the local machine where you start working:
Xlib: connection to "host_name" refused by server
Xlib: Client is not authorized to connect to Server
xhost: unable to open display "host_name"
To correct the problem:
  1. Enter the following command at the UNIX prompt of your local machine, where remote_machine is the machine on which you are running the installer:
    xhost +remote_machine
  2. Restart the installer.
Address already in use This message from srvbuild means you entered a port number that is already in use:
kernel: ninit: bind, Address already in use
To correct the problem, enter a different port number on the srvbuild window. The command netstat -a produces a list of port numbers in use.
Adaptive Server fails to start The shared memory of the operating system may not be set high enough.

To correct the problem, see the Installing the Server topic, for instructions on adjusting the shared memory value. Restart the installation or upgrade process.
The Installer fails to start
If the installer does not start, restart it using the debug mode:
  1. Set the environment variable LAX_DEBUG to true before running the installer.
Cannot start XP Server You may receive the following message from XP Server when it is invoked by xp_cmdshell or some other extended stored procedure:
Msg 11018, Level 16, State 1:
Procedure "xp_cmdshell", Line 2:
XP Server must be up for ESP to execute.
(return status = -6)

Verify that there is an XP Server entry in the Adaptive Server sysservers table. If you created XP Server in a different srvbuild session than Adaptive Server and you did not specify a related Adaptive Server, srvbuild cannot update the sysservers table. Verify that the XP server exists in the interfaces file or LDAP server.

Use sp_addserver to add an entry to the sysservers table.
Troubleshooting Resource File Installations If you encounter problems during the build, configuration, or upgrade process while using the srvbuild[res], sqlloc[res], or sqlupgrade[res], it may be that these utilities did not allow enough time for Adaptive Server to shut down properly. Set the SYBSHUTWAIT environment variable to force the utilities to wait for Adaptive Server to shut down. For example, this command forces the utility to wait for two minutes to allow Adaptive Server to shut down before proceeding with the next task:
% setenv SYBSHUTWAIT 120
Configuration Failed Check the location of the system shared libraries. The shared libraries libXt.a and libX11.a are normally stored in /usr/lpp/X11/lib/R5. The libXm.a library is normally located in either /usr/lpp/X11/Motif1.2/lib or /usr/lpp/X11/R5/Motif1.2.

If these shared libraries are located in directories different from the above, set the LIBPATH environment variable to indicate these other directories.

The shared libraries libXt.so and libX11.so are normally stored in /usr/openwin/lib. The shared library libsocket.so is normally located in /usr/lib.

If the shared libraries on your operating system are located in directories other than those mentioned in the preceding paragraph, set the environment variable LD_LIBRARY_PATH to indicate the new locations.
Parent topic: Troubleshoot the Server