7000 to 7050
Distributed Tuning Interface Status Codes
This section lists the status codes you can receive when using the Distributed Tuning Interface. See Btrieve API Guide for more information on this interface.
7001: Invalid connection handle specified
Specify a valid connection handle with the API call.
7002: NULL pointer specified
Specify a valid pointer with the API call.
7003: Buffer was too small
Increase the buffer size. Some APIs report the required size in an out parameter.
7004: A general failure occurred
This error can be returned in the following situations:
•
You do not have the necessary permissions to perform the operation.
•
The engine on the target machine is not started.
7005: Invalid data type specified
Specify a valid data type for the operation.
7006: Setting value is out of range
Check the valid range for the setting in the configuration reference section of Advanced Operations Guide.
7007: At least one selection item is invalid
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.
7008: Invalid sequence number
Specify a valid sequence number for the operation.
7009: Data on open files is not available
Data related to open files is not currently available.
7010: Client ID is invalid
The client ID needed for this operation is invalid. Specify a valid client ID.
7011: Insufficient access rights
You have insufficient access rights to perform the operation requested. Many DTI functions require administrative rights on the server. See Btrieve API Guide for more information on rights required for DTI operations.
7012: Named database already exists
The named database you are trying to add already exists. Specify a unique name for the named database.
7013: Named database does not exist
The requested named database does not exist. Specify a valid named database.
7014: DTI not initialized
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 Btrieve API Guide for more information.
7015: File not open
The operation you requested requires an open file.
7016: Dictionary files already exist
Dictionary files for the specified database already exist.
7017: Dictionary path in use
Another process has the dictionary files in use. Close all other running applications and retry the operation.
7018: Invalid DSN name
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: []{}() ?*=!@,;
7019: DSN already exists
The DSN you are trying to create already exists. Specify a different name for the DSN.
7020: Specified DSN does not exist
The DSN you are trying to locate does not exist. Specify a valid DSN name.
7021: Invalid open mode for DSN
Specify a valid open mode. For DSN open modes, see DSN Open Mode in ODBC Guide.
7022: Component not loaded
A component needed for DTI is not loaded. Try restarting your PSQL engines.
7023: The database files cannot be deleted because they are shared with another database
You receive this status when trying to delete a database that shares DDF files with another database.
7024: Invalid Btrieve Security Policy
When creating a database, an invalid Btrieve Security Policy was specified. Specify one of:
•
PSQL_DB_POLICY_CLASSIC
•
PSQL_DB_POLICY_MIXED
•
PSQL_DB_POLICY_DBSEC
7025: Server name not found
The server you specified cannot be found. Check the server name and try again.
7026: Requester not loaded
The connection could not be established because the client requester is not loaded.
7027: Server table full
The connection could not be established because the internal server name table is full.
7028: Client connections limit exceeded
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.
7029: Permissions Error
The connection could not be established because DTI encountered a permissions error. Check your username and password and try again.
7030: Out of memory
The connection could not be established due to lack of memory resources.
7031: No transport is available
No remote connection could be established. Check your network configuration.
7032: Connection failure
The connection could not be established due to an unknown reason.
7033: Connection was lost
The remote connection to the server was lost. If this error persists, check your network configuration.
7034: Database name is too long
The database name you specified exceeds the length limit. In Advanced Operations Guide, see PSQL Database Concepts for information on valid database names.
7035: Insufficient number of data paths
When copying a database, you specified a smaller number of data paths than the original database contained.
7036: File name already exists
The file name you specified already exists. Choose a unique file name for the operation.
7037: Password is invalid
The password you specified for the operation is not valid.
7038: Destination data path is invalid
The path specified as the destination could not be found. Verify the path you provided to the API.
7039: Dictionary path is invalid
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 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.
7040: Filter option is invalid
A parameter passed to DTI was invalid. See the DTI documentation in Btrieve API Guide for the valid options.
7041:Cannot perform operation because database entries in FILE.DDF contain absolute paths
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.
7042: Bound database requires data dictionary files
The creation of a bound database requires data dictionary files (DDFs). For a bound database, ensure that the CREATE DATABASE statement or the Create New Database wizard also specifies the creation of dictionary files.
7043 Invalid character sent by client
One or more characters sent by the client in a DTI function argument string are invalid and cannot be translated to the server’s encoding. Verify the function arguments.
7044 Invalid character received by client
One or more characters received from the server in a DTI function argument string are invalid and cannot be translated to the client’s operating system encoding. It may be necessary to use a different client machine.
7045 Internal buffer too small
The internal buffer is too small to process a DTI argument. One possible workaround is to use shorter arguments.
7046 Invalid encoding translation option
The translation option in the DTI function PvCreateDSN2() or PvModifyDSN2() specifies an invalid encoding. For the valid options, see the argument translate in Distributed Tuning Interface Guide.
7047 Invalid code page for database
The code page specified for the database is invalid (not supported by the database engine). Verify the code page and use one supported by the database engine. The code pages supported can be viewed from the Create Database dialog within PSQL Control Center. See New Database GUI Reference in PSQL User's Guide.