Overview

For Sybase server products, there are two categories of errors:

To determine the cause of an error, first look in the log file of the utility being used, to identify the task the utility was performing when it failed. Then check the server error log. See “Error log locations” for the location of the error log files for the installation utilities and the servers.

Table 10-1 lists possible causes and solutions for common problems that you might encounter during a first-time installation or upgrade. If you continue to have problems, retry the installation or upgrade.

If the installation program or svrbuild unexpectedly quits, or if you cannot correct the problem, see the Error Messages and Troubleshooting Guide.

Table 10-1: Troubleshooting guidelines

Problem

Possible cause and solution

The installation program cannot start Adaptive Server.

Failure to start Adaptive Server is generally caused by a lack of available RAM or disk space.

Make sure you meet RAM requirements. If you have the required RAM, remove, then reinstall all applications to the hard drive and restart the installation process.

After Adaptive Server is installed, there should be 25MB of free disk space left in the disk drive. Adaptive Server needs approximately 18MB for creating shared memory files.

Verify that you are logged in as System Administrator. You must log in as an administrator to start Adaptive Server.

Shut down Monitor Server before restarting Adaptive Server.

After upgrading Adaptive Server, you cannot use svrbuild.

After you begin upgrading a server, you may be unable to use the same svrbuild session for other tasks. Exit and restart svrbuild.

The installation program cannot connect to the upgraded Adaptive Server.

After you begin upgrading a server, you may be unable to use the same svrbuild session for other tasks. Exit and restart svrbuild.

The installation program detects reserved word conflicts.

“Stopping Adaptive Server after a failure”.

The upgrade fails.

See “Recovering from a failed upgrade”.