Determine the cause of problems and apply the recommended solution.
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.
This table lists possible causes and solutions for common problems that you might encounter during a first-time installation, or an upgrade. If you continue to have problems, retry the installation or upgrade.
If the installation program or srvbuild unexpectedly quits, or if you cannot correct the problem, see the Error Messages and Troubleshooting Guide.
Problem | Solution |
---|---|
The installation program cannot start the SAP ASE 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, and log in again for the changes to take effect. Use the system sdministrator login account or assign yourself system sdministrator privileges. Verify that you are logged in to Windows as a member of the Administrators group. |
The installation program cannot connect to the upgraded SAP ASE server. | Exit and restart Server Config. |
Cannot start SAP ASE as a service on a Windows 32-bit machine. | You cannot start SAP ASE as a service on
32-bit Windows OS machines because it cannot open the master device. This occurs because the installation process configures the SAP ASE service to run as "LocalSystem" instead of "Administrator." You can successfully access the SAP ASE server by logging in as Administrator and running the start_server.bat file, but attempting to start SAP ASE as a service fails due to incorrect permission settings. To resolve this issue:
You can now start SAP ASE as a service. |