For Sybase server products, there are two categories of errors:
Errors generated by the installation, upgrade, and setup utilities
Errors generated by the server (Adaptive Server, Backup Server, and so on)
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 Server Config unexpectedly quits, or if you cannot correct the problem, see the Troubleshooting and Error Messages Guide.
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. If you have a FAT-based file system, you may have given the server a name that is more than 31 characters, which prevents the installation program from starting and causes the installation to fail. This occurs because the server tries to create a shared memory file with the same name as the server. Shut down Monitor Server before restarting Adaptive Server. |
Sybase products cannot locate their required DLLs. |
The installation program makes several modifications to your operating environment to locate required files. Log out of Windows NT, and log in again for the changes to take effect. Use the System Administrator’s login account or assign yourself System Administrator privileges. Verify that you are logged in to Windows NT as a member of the Administrators group. |
After upgrading from SQL Server, you cannot use Server Config. |
After you begin upgrading a server, you may be unable to use the same Server Config session for other tasks. Exit and restart Server Config. |
The installation program cannot connect to the upgraded Adaptive Server. |
After you begin upgrading a server, you may be unable to use the same Server Config session for other tasks. Exit and restart Server Config. |
The installation program detects reserved word conflicts. |
|
The upgrade fails. |
|
Attempts to create a server at the network level. |
Use the Open Client/Open Server configuration utility to edit %SYBASE%\ini\libtcl.cfg. The file should contain one of the following entries, depending on the protocol you have chosen to use: NLWNSCK = Windows Socket driver NLMSNMP = Named Pipes driver NLNWLINK = spx/ipx driver If the entry is missing or incorrect, enter the correct value.
|
Do not use a text editor, such as Notepad, to edit the libtcl.cfg file.