|
|
4 Overview of Error Codes and Messages
This chapter provides general information about SequeLink's error handling strategy and describes the types of errors that can occur when using SequeLink.
Each generated error message includes a description of the most probable cause of the error, prefixed by the name of the component that returned the error.
For information about the error formats and the types of errors that can occur when using SequeLink:
SequeLink® ODBC Driver
The following types of errors can occur when you are using the SequeLink Client for ODBC:
SequeLink® ODBC Driver Errors
An error generated by the SequeLink ODBC driver has the following format:
For example:
The native error code is always zero (0).
If you receive this type of error, check the last ODBC call your application made. Contact your ODBC application vendor, or refer to the ODBC documentation available from Microsoft. The ODBC 3.0 Software Development Kit and Programmer's Reference is available from Microsoft Press. For information on later versions of ODBC, refer to the documentation included in the ODBC SDK.
SequeLink® Client Errors
An error generated by the SequeLink Client for ODBC has the following format:
For example:
[DataDirect] [ODBC SequeLink driver] [SequeLink Client] The specified transliteration module is not found.Use the native error code to look up details about the possible cause of the error. See Chapter 5 "Error Messages" for a list of all error codes and messages.
SequeLink® Server Errors
An error generated by SequeLink Server has the following format:
For example:
[DataDirect] [ODBC SequeLink driver] [SequeLink Server] Only Select statements are allowed in this read-only connection.Use the native error code to look up details about the possible cause of the error. See Chapter 5 "Error Messages" for a list of all error codes and messages.
Database Errors
An error generated by the database has the following format:
For example:
Use the native error code to look up details about the possible cause of the error. For these details, refer to your database documentation.
SequeLink® ADO Data Provider
The following types of errors can occur when you are using the SequeLink Client for ADO:
SequeLink® ADO Data Provider Errors
An error generated by the SequeLink ADO data provider has the following format:
For example:
The native error code is always zero (0).
If you receive this type of error, check the last ADO call your application made. Contact your ADO or OLE DB application vendor, or refer to the ADO and OLE DB documentation available from Microsoft.
SequeLink® Client Errors
An error generated by the SequeLink Client for ADO has the following format:
For example:
Use the native error code to look up details about the possible cause of the error. See Chapter 5 "Error Messages" for a list of all error codes and messages.
SequeLink® Server Errors
An error generated by SequeLink Server has the following format:
For example:
[DataDirect] [SequeLink ADO provider] [SequeLink Server] Only Select statements are allowed in this read-only connection.Use the native error code to look up details about the possible cause of the error. See Chapter 5 "Error Messages" For a list of all error codes and messages.
Database Errors
An error generated by the database has the following format:
For example:
Use the native error code to look up details about the possible cause of the error. For these details, refer to your database documentation.
SequeLink® JDBC Driver
The SequeLink JDBC driver reports errors to the calling application by returning SQLExceptions. Errors can be generated by the following components:
SequeLink® JDBC Driver Errors
An error generated by the SequeLink JDBC driver has the following format:
For example:
Use the native error code to look up details about the possible cause of the error. See Chapter 5 "Error Messages" for a list of all error codes and messages. Sometimes, you may need to check the last JDBC call your application made and refer to the JDBC specification for recommended action.
SequeLink® Server Errors
An error generated by SequeLink Server has the following format:
For example:
[DataDirect] [SequeLink JDBC Driver] [SequeLink Server] Only Select statements are allowed in this read-only connection.Use the native error code to look up details about the possible cause of the error. See Chapter 5 "Error Messages" for a list of all error codes and messages.
Database Errors
An error generated by the database has the following format:
For example:
Use the native error code to look up details about the possible cause of the error. For these details, refer to your database documentation.
SequeLink® .NET Data Provider
The following types of errors can occur when you are using the SequeLink Client for .NET:
SequeLink® Client Errors
Errors generated by the .NET Client have different formats, depending on the cause and source of the problem. Formats include:
If a native error code is displayed, you can look up details about the possible cause of the error. See Chapter 5 "Error Messages" for a list of all SequeLink error codes and messages.
SequeLink® Server Errors
An error generated by SequeLink Server has the following format:
For example:
Use the native error code to look up details about the possible cause of the error. See Chapter 5 "Error Messages" for a list of all error codes and messages.
Database Errors
An error generated by the database has the following format:
For example:
Use the native error code to look up details about the possible cause of the error. For these details, refer to your database documentation.
|
|