 | Status Codes and Messages (v9 SP2 (9.5) revision 1) |  |
|
This section lists the status codes you can receive when using the Distributed Tuning Interface. See API Programmer's Reference for more information on this interface.
Specify a valid connection handle with the API call.
Specify a valid pointer with the API call.
Increase the buffer size. Some APIs report the required size in an out parameter.
This error can be returned in the following situations:
Specify a valid data type for the operation.
Check the valid range for the setting in the configuration reference section of Advanced Operations Guide.
Check the list of selection items to ensure all are valid selections. You can find the valid values in the configuration reference section of Advanced Operations Guide.
Specify a valid sequence number for the operation.
Data related to open files is not currently available.
The client ID needed for this operation is invalid. Specify a valid client ID.
You have insufficient access rights to perform the operation requested. Many DTI functions require administrative rights on the server. See API Programmer's Reference for more information on rights required for DTI operations.
The named database you are trying to add already exists. Specify a unique name for the named database.
The requested named database does not exist. Specify a valid named database.
Before you can use DTI functions, you must first initialize DTI by calling the PvStart() function. Then you can invoke DTI operations. When finished, use PvStop() to terminate the DTI session. See API Programmer's Reference for more information.
The operation you requested requires an open file.
Dictionary files for the specified database already exist.
Another process has the dictionary files in use. Close all other running applications and retry the operation.
The DSN you are trying to create contains invalid characters or is too long. DSN names cannot be longer than 20 characters and cannot contain the following symbols: []{}() ?*=!@,;
The DSN you are trying to create already exists. Specify a different name for the DSN.
The DSN you are trying to locate does not exist. Specify a valid DSN name.
Specify a valid open mode. DSN open modes are documented in Advanced Operations Guide.
A component needed for DTI is not loaded. Try restarting your Pervasive PSQL engines.
You receive this status when trying to delete a database that shares DDF files with another database.
When creating a database, an invalid Btrieve Security Policy was specified. Specify one of:
The server you specified cannot be found. Check the server name and try again.
The connection could not be established because the client requester is not loaded.
The connection could not be established because the internal server name table is full.
The number of client connections for DTI is limited to 100.
The connection could not be established because the limit on client connections has been reached.
The connection could not be established because DTI encountered a permissions error. Check your username and password and try again.
The connection could not be established due to lack of memory resources.
No remote connection could be established. Check your network configuration.
The connection could not be established due to an unknown reason.
The remote connection to the server was lost. If this error persists, check your network configuration.
The database name you specified exceeds the length limit. In Advanced Operations Guide, see Pervasive PSQL Database Concepts for information on valid database names.
When copying a database, you specified a smaller number of data paths than the original database contained.
The filename you specified already exists. Choose a unique filename for the operation.
The password you specified for the operation is not valid.
The path specified as the destination could not be found. Verify the path you provided to the API.
The path specified for dictionaries could not be found. Verify the path you provided to the API.
On Linux, this error can result if you try to create a database with Pervasive PSQL Control Center and the owner of the directory is not psql. Ensure that the owner of the directory where you want to create the database is psql. Use the chown command to change ownership. For example, chown psql directoryname.
A parameter passed to DTI was invalid. See the DTI documentation in API Programmer's Reference for the valid options.
You cannot perform the requested function because the database contains absolute paths in FILE.DDF. To resolve this issue, remove the absolute paths from the database and try again.
|
Chapter contents
Prev topic: 6000 to 6050
|