SQL Advantage User's Guide

Home

SQL Advantage User's Guide

Appendix B: Error Messages

Appendix B

Error Messages

SQL Advantage displays error messages to alert you to abnormal conditions. Table B-1 lists the most significant SQL Advantage error messages and the corrective action to take when they appear.

Table B-1: Error Messages
Error Message
Corrective Action
Insufficient memory to initialize application. Please close other applications and try again.
Your machine needs more memory. Shut down other applications and try again.
Application has run out of memory while <performing some task>.
Your machine needs more memory. Close session and result windows and try again, or shut down other applications and try again.
Cannot open the selected file. <filename> <reason>
Cannot open error log file. <filename> <reason>
Cannot write to log file. <filename> <reason>
For each of these error messages, one of the following <reasons> may also be displayed:
The file has an incompatible format
The file was created with an earlier version of the application
File access denied
File I/O Error
File already in use
File lock violation
Disk is full
File cannot be found
Directory containing the file cannot be found
In all of the above cases, the solution to your problem should be self-evident.
Cannot find Server <SQLServerName> in your current Open Client Configuration.
You have made a typographical error in <SQLServerName>; retype name.
Run dsedit to add SQL Server <SQLServerName> to your list of servers.
Open Client not using correct Directory Service Driver; run osscfg to select appropriate Directory Service Driver.
Internal failure while initializing SQL Advantage. Please check that Open Client is configured correctly.
Exceeded system resources: free up resources by closing windows or applications.
Incorrect Open Client configuration:
Check for missing interfaces file
Check for error in registry
Check for missing character sets or locales
Internal failure has occurred while <performing some task>. Please contact your System Administrator or Sybase Technical Support.
Contact your System Administrator or Sybase Technical Support.
Internal failure has occurred while initializing result data.
Other messages should accompany this one to help you understand what to fix. Most probably, something is wrong with your configuration. If you can't resolve it, contact your System Administrator or Sybase Technical Support.
Internal failure has occurred, cannot open document.
Other messages should accompany this one to help you understand what to fix. Most probably, something is wrong with your configuration. If you can't resolve it, contact your System Administrator or Sybase Technical Support.
Internal Error: Bad Transaction State.
Quit the application and report the problem to Sybase Technical Support. To prevent the logfile from being overwritten, do not relaunch until after reporting the problem to Sybase Technical Support.
The connection has dropped.
No harm is done. Simply reconnect. Report the problem to Sybase Technical Support.
Failure has occurred in CT-Library call. Connection is no longer usable and will be automatically dropped.
No harm is done. Simply reconnect. Report the problem to Sybase Technical Support.

Error Message	Corrective Action
Insufficient memory to initialize application. Please close other applications and try again.	Your machine needs more memory. Shut down other applications and try again.
Application has run out of memory while <performing some task>.	Your machine needs more memory. Close session and result windows and try again, or shut down other applications and try again.
Cannot open the selected file. <filename> <reason> Cannot open error log file. <filename> <reason> Cannot write to log file. <filename> <reason>	For each of these error messages, one of the following <reasons> may also be displayed: The file has an incompatible format The file was created with an earlier version of the application File access denied File I/O Error File already in use File lock violation Disk is full File cannot be found Directory containing the file cannot be found In all of the above cases, the solution to your problem should be self-evident.
Cannot find Server <SQLServerName> in your current Open Client Configuration.	You have made a typographical error in <SQLServerName>; retype name. Run dsedit to add SQL Server <SQLServerName> to your list of servers. Open Client not using correct Directory Service Driver; run osscfg to select appropriate Directory Service Driver.
Internal failure while initializing SQL Advantage. Please check that Open Client is configured correctly.	Exceeded system resources: free up resources by closing windows or applications. Incorrect Open Client configuration: Check for missing interfaces file Check for error in registry Check for missing character sets or locales
Internal failure has occurred while <performing some task>. Please contact your System Administrator or Sybase Technical Support.	Contact your System Administrator or Sybase Technical Support.
Internal failure has occurred while initializing result data.	Other messages should accompany this one to help you understand what to fix. Most probably, something is wrong with your configuration. If you can't resolve it, contact your System Administrator or Sybase Technical Support.
Internal failure has occurred, cannot open document.	Other messages should accompany this one to help you understand what to fix. Most probably, something is wrong with your configuration. If you can't resolve it, contact your System Administrator or Sybase Technical Support.
Internal Error: Bad Transaction State.	Quit the application and report the problem to Sybase Technical Support. To prevent the logfile from being overwritten, do not relaunch until after reporting the problem to Sybase Technical Support.
The connection has dropped.	No harm is done. Simply reconnect. Report the problem to Sybase Technical Support.
Failure has occurred in CT-Library call. Connection is no longer usable and will be automatically dropped.	No harm is done. Simply reconnect. Report the problem to Sybase Technical Support.


	Expand Search