Value
|
Error name
|
Description
|
10001
|
FP_INVALID_NAME
|
The name that you have used is not XML compliant.
|
10002
|
FP_UNKNOWN_OPTION
|
You have used an unknown option name with FPPool_SetIntOption() or FPPool_GetIntOption().
|
10003
|
FP_NOT_SEND_REQUEST_ERR
|
An error occurred when you sent a request to the server. This internal error was generated because the server could not accept the request packet. Verify all LAN connections and try again.
|
10004
|
FP_NOT_RECEIVE_REPLY_ERR
|
No reply was received from the server. This internal error was generated because the server did not send a reply to the request packet. Verify all LAN connections and try again.
|
10005
|
FP_SERVER_ERR
|
The server reports an error. An internal error on the server occurred. Try again.
|
10006
|
FP_PARAM_ERR
|
You have used an incorrect or unknown parameter. Example: Is a string-variable too long, null, or empty when it should not be? Does a parameter have a limited set of values? Check each parameter in your code.
|
10007
|
FP_PATH_NOT_FOUND_ERR
|
This path does not correspond to a file or directory on the client system. The path in one of your parameters does not point to an existing file or directory. Verify the path in your code.
|
10008
|
FP_CONTROLFIELD_ERR
|
The server reports that the operation generated a "Controlfield missing" error. This internal error was generated because the required control field was not found. Try again. (Obsolete fromv2.0.)
|
10009
|
FP_SEGDATA_ERR
|
The server reports that the operation generated a "Segdatafield missing" error. This internal error was generated because the required field containing the blob data was not found in the packet. Try again. (Obsolete fromv2.0.)
|
10010
|
FP_DUPLICATE_FILE_ERR
|
A duplicate CA already exists on the server. If you did not enable duplicate file detection, verify that you have not already stored this data and try again.
|
10011
|
FP_OFFSET_FIELD_ERR
|
The server reports that the operation generated an "Offsetfield missing" error. This internal error was generated because the offset field was not found in the packet. Try again. (Obsolete fromv2.0.)
|
10012
|
FP_OPERATION_NOT_SUPPORTED
|
This operation is not supported. If FPClip_Write(), FPTag_GetSibling(), FPTag_GetPrevSibling(), FPTag_GetFirstChild() or FPTag_Delete() returned this error, then this operation is not supported for C-Clips opened in 'flat' mode. If FPStream returned this error, then you are trying to perform an operation that is not supported by that stream.
|
10013
|
FP_ACK_NOT_RCV_ERR
|
A write acknowledgement was not received. Verify your LAN connections and try again.
|
10014
|
FP_FILE_NOT_STORED_ERR
|
Could not write the blob to the server ORcould not find the blob on the server. This internal error was generated because the store operation of the blob was not successful. Verify that the original data was correctly stored, verify your LAN connections and try again.
|
10015
|
FP_NUMLOC_FIELD_ERR
|
The server reports that the operation generated a "Numlockfield missing" error. This internal error was generated because the numlock field was not found in the packet. Try again. (Obsolete fromv2.0.)
|
10016
|
FP_SECTION_NOT_FOUND_ERR
|
The GetSection request could not retrieve the defined section tag. This internal error was generated because a required section is missing in the CDF. Verify the content of your code and try again. (Obsolete fromv2.0.)
|
10017
|
FP_TAG_NOT_FOUND_ERR
|
The referenced tag could not be found in the CDF. This internal error was generated because information is missing from the description section in the CDF. Verify the content of your code and try again.
|
10018
|
FP_ATTR_NOT_FOUND_ERR
|
Could not find an attribute with that name. If FPTag_GetXXXAttribute() returned this error, then the attribute was not found in the tag. If FPTag_GetIndexAttribute() returned this error, then the index parameter is larger than the number of attributes in the tag.
|
10019
|
FP_WRONG_REFERENCE_ERR
|
The reference that you have used is invalid. The reference was not opened, already closed, or not of the correct type.
|
10020
|
FP_NO_POOL_ERR
|
It was not possible to establish a connection with a cluster. The server could not be located. This means that none of the IP addresses could be used to open a connection to the server or that no cluster could be found that has the required capability. Verify your LAN connections, server settings, and try again.
|
10021
|
FP_CLIP_NOT_FOUND_ERR
|
Could not find the referenced C-Clip in the cluster. Returned by FPClip_Open(), it means the CDF could not be found on the server. Verify that the original data was correctly stored and try again.
|
10022
|
FP_TAGTREE_ERR
|
An error exists in the tag tree. Verify the content of your code and try again.
|
10023
|
FP_ISNOT_DIRECTORY_ERR
|
A path to a file has been given but a path to a directory is expected. Verify the path to the data and try again.
|
10024
|
FP_UNEXPECTEDTAG_ERR
|
Either a "file" or "folder" tag was expected but not given. An unexpected tag was found when retrieving the CDF. The CDF is probably corrupt.
|
10025
|
FP_TAG_READONLY_ERR
|
The tag cannot be changed or deleted (it is probably a top tag). Verify your program logic.
|
10026
|
FP_OUT_OF_BOUNDS_ERR
|
The options parameter is out of bounds. One of the function parameters exceeds its preset limits. Verify each parameter in your code.
|
10027
|
FP_FILESYS_ERR
|
A file system error occurred, for example an incorrect path was given, or you are trying to open an unknown file or a file in the wrong mode. Verify the path and try again.
|
10029
|
FP_STACK_DEPTH_ERR
|
You have exceeded the nested tag limit. Review the structure of your content description and try again. Deprecated.
|
10030
|
FP_TAG_HAS_NO_DATA_ERR
|
You are trying to access blob data of a tag that does not contain blob data.
|
10031
|
FP_VERSION_ERR
|
The C-Clip has been created using a more recent version of the client software than you are using. Upgrade to the latest version.
|
10032
|
FP_MULTI_BLOB_ERR
|
The tag already has data associated with it. You need to create a new tag to store the new data or delete this tag and recreate it and try again.
|
10033
|
FP_PROTOCOL_ERR
|
You have used an unknown protocol option (Only HPP is supported). Verify the parameters in your code. It is also possible that an internal communication error occurred between the server and client. If you have verified your code and the problem persists then you need to upgrade to the latest client and server versions.
|
10034
|
FP_NO_SOCKET_AVAIL_ERR
|
No new network socket is available for the transaction. Reduce the number of open transactions between the client and the server or use the function FPPool_SetGlobalOption() to increase the number of available sockets with FP_OPTION_MAXCONNECTIONS.
|
10035
|
FP_BLOBIDFIELD_ERR
|
A BlobID field (the Content Address) was expected but not given. Upgrade to the latest client and server versions. (Obsolete fromv2.0.)
|
10036
|
FP_BLOBIDMISMATCH_ERR
|
The blob is corrupt: a BlobID mismatch occurred between the client and server. The Content Address calculation on the client and the server has returned different results. The blob is corrupt. If FPClip_Open() returns this error, it means the blob data or metadata of the C-Clip is corrupt and cannot be decoded.
|
10037
|
FP_PROBEPACKET_ERR
|
The probe packet does not contain valid server addresses. Upgrade to the latest client and server versions. (Obsolete fromv2.0.)
|
10038
|
FP_CLIPCLOSED_ERR
|
(Javaonly.) You tried to perform an operation on a closed C-Clip. This operation requires access to an open C-Clip. Verify your code and try again.
|
10039
|
FP_POOLCLOSED_ERR
|
(Javaonly.) You tried to perform an operation on a closed pool. This operation requires access to an open pool. Verify your code and LAN connections and try again.
|
10040
|
FP_BLOBBUSY_ERR
|
The blob on the cluster is busy and cannot be read from or written to. You tried to read from or write to a blob that is currently busy with another read/write operation. Try again.
|
10041
|
FP_SERVER_NOTREADY_ERR
|
The server is not ready yet. This error can occur when a client tries to connect to the server to execute an operation and the nodes with the access role are running but the nodes with the storage role have not been initialized yet. This error can also occur when not enough mirror groups are found on the server. Allow the SDK to perform the automatic number of configured retries.
|
10042
|
FP_SERVER_NO_CAPACITY_ERR
|
The server has no capacity to store data. Enlarge the server's capacity and try again.
|
10043
|
FP_DUPLICATE_ID_ERR
|
The application passed in a sequence ID that was previously used.
|
10044
|
FP_STREAM_VALIDATION_ERR
|
A generic stream validation error occurred.
|
10045
|
FP_STREAM_BYTECOUNT_MISMATCH_ ERR
|
A generic stream byte count mismatch was detected.
|
10101
|
FP_SOCKET_ERR
|
An error on the network socket occurred. Verify the network.
|
10102
|
FP_PACKETDATA_ERR
|
The data packet contains wrong data. Verify the network, the version of the server or try again later.
|
10103
|
FP_ACCESSNODE_ERR
|
No node with the access role can be found. Verify the IP addresses provided with FPPool_Open().
|
10151
|
FP_OPCODE_FIELD_ERR
|
The Query Opcode field is missing from the packet.
|
10152
|
FP_PACKET_FIELD_MISSING_ERR
|
The packet field is missing.
|
10153
|
FP_AUTHENTICATION_FAILED_ERR
|
Authentication to get access to the server failed. Check the profile name and secret.
|
10154
|
FP_UNKNOWN_AUTH_SCHEME_ERR
|
An unknown authentication scheme has been used.
|
10155
|
FP_UNKNOWN_AUTH_PROTOCOL_ERR
|
An unknown authentication protocol has been used.
|
10156
|
FP_TRANSACTION_FAILED_ERR
|
Transaction on the server failed.
|
10157
|
FP_PROFILECLIPID_NOTFOUND_ERR
|
No profile clip was found.
|
10158
|
FP_ADVANCED_RETENTION_DISABLED_ ERR
|
The Advanced Retention Management feature is not licensed or enabled for event-based retention (EBR) and retention hold.
|
10159
|
FP_NON_EBR_CLIP_ERR
|
An attempt was made to trigger an EBRevent on a C-Clip that is not eligible to receive an event.
|
10160
|
FP_EBR_OVERRIDE_ERR
|
An attempt was made to trigger or enable the event-based retention period/class of a C-Clip a second time. You can set EBR information only once.
|
10161
|
FP_NO_EBR_EVENT_ERR
|
The C-Clip is under event-based retention protection and cannot be deleted.
|
10162
|
FP_RETENTION_OUT_OF_BOUNDS_ERR
|
The event-based retention period being set does not meet the minimum/maximum rule.
|
10163
|
FP_RETENTION_HOLD_COUNT_ERR
|
The number of retention holds exceeds the limit of 100.
|
10164
|
FP_METADATA_MISMATCH_ERR
|
Mutable metadata mismatch found.
|
10201
|
FP_OPERATION_REQUIRES_MARK
|
The application requires marker support but the stream does not provide that.
|
10202
|
FP_QUERYCLOSED_ERR
|
The FP Query for this object is already closed. (Java only).
|
10203
|
FP_WRONG_STREAM_ERR
|
The function expects an input stream and gets an output stream or vice-versa.
|
10204
|
FP_OPERATION_NOT_ALLOWED
|
The use of this operation is restricted or this operation is not allowed because the server capability is false.
|
10205
|
FP_SDK_INTERNAL_ERR
|
An SDK internal programming error has been detected.
|
10206
|
FP_OUT_OF_MEMORY_ERR
|
The system ran out of memory. Check the system's capacity.
|
10207
|
FP_OBJECTINUSE_ERR
|
Cannot close the object because it is in use. Check your code.
|
10208
|
FP_NOTYET_OPEN_ERR
|
The object is not yet opened. Check your code.
|
10209
|
FP_STREAM_ERR
|
An error occurred in the generic stream. Check your code.
|
10210
|
FP_TAG_CLOSED_ERR
|
The FP Tag for this object is already closed. (Java only.)
|
10211
|
FP_THREAD_ERR
|
An error occurred while creating a background thread.
|
10212
|
FP_PROBE_TIME_EXPIRED_ERR
|
The probe limit time was reached.
|
10213
|
FP_PROFILECLIPID_WRITE_ERR
|
There was an error while storing the profile clip ID.
|
10214
|
FP_INVALID_XML_ERR
|
The specified string is not valid XML.
|
10215
|
FP_UNABLE_TO_GET_LAST_ERROR
|
The call to FPPool_GetLastError() or FPPool_GetLastErrorInfo() failed. The error status of the previous function call is unknown; the previous call may have succeeded.
|
10216
|
FP_LOGGING_CALLBACK_ERR
|
An error occurred in the application-defined FP Logging callback.
|