109 PRCF-01001 to PRCF-02082
- PRCF-01001: The directory "{0}" does not exist
-
Cause: A directory that did not exist was chosen for the top-level directory of the directory map.
- PRCF-01002: Source directory "{0}" is not a directory
-
Cause: An existing file which was not a directory was provided as top-level directory.
- PRCF-01003: The file "{0}" does not exist
-
Cause: The file was not found in the file system.
- PRCF-01004: The link destination "{0}" does not exist
-
Cause: The link destination was not found in the file system.
- PRCF-01005: "{0}" conflicts with the exclude-list
-
Cause: The pathname (directory, file or symbolic link pathname) to add to the directory map could not be added as it conflicted with the exclude list.
- PRCF-01006: The directory "{0}" exists already in the directory map
-
Cause: The directory existed already in the directory map.
- PRCF-01007: The file "{0}" exists already in the directory map
-
Cause: The file existed already in the directory map.
- PRCF-01008: The link "{0}" exists already in the directory map
-
Cause: The link existed already in the directory map.
- PRCF-01009: The parent of "{0}" does not exist
-
Cause: The parent directory of the content (directory, file or symbolic link) that was being processed did not exist.
- PRCF-01010: "{0}" is not a directory
-
Cause: The indicated object was expected to be a directory, but it was not.
- PRCF-01011: Cannot remove "{0}" as the directory map does not contain it
-
Cause: The content (i.e., directory, file or symbolic link) could not be removed from the directory map as it did not exist there.
- PRCF-01012: The following contents (directories, files or symbolic links) cannot be included to to the list of contents to add to the directory map: {0}
-
Cause: The contents that could not be included to the add-list were those which conflicted with the exclude-list (see the accompanying PRCF-1005 message).
- PRCF-01013: The directory map has no entry
-
Cause: The user tried to acquire information about an empty directory map.
- PRCF-01014: Cannot add "{0}" as there is no directory map
-
Cause: The user tried to add a content (i.e., directory, file or symbolic link) to an empty directory map. This operation is allowed only if there is a directory map.
- PRCF-01015: Cannot add "{0}" to the directory map as "{0}" does not exist
-
Cause: The content to add to the directory map was not found in the file system.
- PRCF-01016: Cannot remove "{0}" as there is no directory map
-
Cause: The user tried to remove a content (i.e., directory, file or symbolic link) from an empty directory map. This operation is allowed only if there is a directory map.
- PRCF-01017: Cannot remove "{0}" from the directory map as "{0}" does not exist
-
Cause: The content to remove from the directory map was not found in the file system.
- PRCF-01018: Exception encountered. Details: {0}
-
Cause: An unexpected error condition was detected during reading the exclude-list or include-list file.
- PRCF-01019: The API supports only Unix OS
-
Cause: The user was running on Windows OS.
- PRCF-01020: "{0}" is not a file
-
Cause: The content that was expected to be a file which turned out not to be a file.
- PRCF-01021: "{0}" is not a valid pathname
-
Cause: The content that was expected to be a valid pathname which turned out to be an invalid one.
- PRCF-01022: "{0}" does not exist
-
Cause: The specified pathname does not exist in the file system.
- PRCF-01023: Symbolic link "{0}" points to "{1}" which does not exist
-
Cause: An existing symbolic link that resolves to a pathname that does not exist.
- PRCF-01024: Symbolic link "{0}" points to "{1}" which is is not a directory
-
Cause: An existing symbolic link that resolves to a non-directory pathname was provided as top-level directory.
- PRCF-01025: Error while trying to open file "{0}" for reading. Details: {1}
-
Cause: An I/O error occurred while trying to open the file for reading.
- PRCF-01026: Error while reading file "{0}". Details: {1}
-
Cause: An I/O error occurred while reading or closing the file.
- PRCF-01027: Error while trying to create file "{0}" for writing. Details: {1}
-
Cause: An I/O error occurred while trying to create the file for writing.
- PRCF-01028: Error while writing file "{0}". Details: {1}
-
Cause: An I/O error occurred while writing or closing the file.
- PRCF-01029: Cannot create directory "{0}"
-
Cause: An error occurred while trying to create the directory.
- PRCF-01030: Input argument "{0}" value is not valid.
-
Cause: This is an internal error. The value for the specified parameter was null.
- PRCF-01031: Input array element "{0}" is not valid.
-
Cause: This is an internal error. The value for the specified array element was null.
- PRCF-01032: Input list element "{0}" is not valid.
-
Cause: This is an internal error. The value for the specified list element was null.
- PRCF-01033: The node "{0}" is duplicated in the input list.
-
Cause: A node name appeared more than once in the input list.
- PRCF-02001: Connection to host/IP address: {0} -- port: {1} refused
-
Cause: Could not establish connection to the provided host/IP address using the port number reported.
- PRCF-02002: Connection to node "{0}" is lost
-
Cause: The connection to the remote node with the specific node ID was lost.
- PRCF-02003: Expected "{0}" but received "{1}"
-
Cause: The command was not executed successfully. The local node received a reply from the remote node that was different from the expected one.
- PRCF-02004: Problem encountered while saving the directory listing to file "{0}". Details : {1}
-
Cause: While trying to save the directory listing to a file, the operation could not be completed successfully.
- PRCF-02005: File transfer cannot proceed because the remote node names do not match the remote node ports
-
Cause: An internal error caused a a mismatch between the number of remote nodes and the number of remote node ports.
- PRCF-02006: File transfer cannot proceed because the list of remote nodes is empty
-
Cause: An empty list of remote nodes was passed as argument.
- PRCF-02007: Invalid selection for the remote node port. "{0}" is not an integer number as expected.
-
Cause: The port number for the remote node was either not a number at all or not an integer number.
- PRCF-02008: The remote node port number "{0}" is out of the expected range [1, 65535]
-
Cause: The port number for the remote node was indeed an integer number but either less than 1 or greater than 65535.
- PRCF-02009: Cannot proceed with the file transfer. There has to be at least one remote node to send the installer files!
-
Cause: The user either provided an empty list of remote nodes or each remote node of the list had invalid format.
- PRCF-02010: All connections to the remote nodes got refused. Cannot proceed with the file transfer. There has to be at least one remote node to send the installer files!
-
Cause: All the attempts to connect to the remote nodes that had valid format failed.
- PRCF-02011: The file "{0}" cannot be read successfully
-
Cause: The file existed in the file system but could not be read successfully.
- PRCF-02012: The top-level directory "{0}" does not exist
-
Cause: The top-level directory was not found in the file system.
- PRCF-02013: Cannot find the CRS Home
-
Cause: The CRS Home did not exist or 'oui' was not a directory under the CRS Home.
- PRCF-02014: Executing command "{0}" on "{1}" failed on node "{2}".\n{3}
-
Cause: The command ('mkdir', 'mkfile', 'mklink' or 'wrfile') failed while executing on the remote node.
- PRCF-02015: One or more commands were not executed successfully on one or more nodes
-
Cause: At least one of the commands 'mkdir', 'mkfile', 'mklink' or 'wrfile' failed while executing on one or more remote nodes.
- PRCF-02016: Required binary file "{0}" not found
-
Cause: The binary file was not found under the expected location.
- PRCF-02017: Node "{0}": The transfer binary was not executed successfully as it returned a wrong port number
-
Cause: Misbehavior of the transfer binary on the provided node.
- PRCF-02018: Node "{0}": The transfer binary was not executed successfully
-
Cause: Unsuccessful execution of the transfer binary.
- PRCF-02019: Cannot retrieve the name for the local node
-
Cause: No IP address for the local host could be found.
- PRCF-02020: Cannot retrieve the host for node "{0}"
-
Cause: No IP address for the node host could be found.
- PRCF-02021: There is a mismatch between the number of node names ({0}) and the number of node destination directories ({1})
-
Cause: An internal error caused a a mismatch between the number of remote nodes and the number of remote destination directories.
- PRCF-02022: The file "{0}" became smaller while being transferred
-
Cause: The indicated source file was smaller following the transfer than when it was initiated. As a result, the resulting file includes contents no longer present in the source.
- PRCF-02023: The following contents cannot be transferred as they are non-readable. \nDirectories:\n {0} \nFiles:\n {1}
-
Cause: The file permissions for the listed contents did not allow the requested operation.
- PRCF-02024: The directory "{0}" is not transferred as it is non-readable
-
Cause: The file permissions of the listed directory did not allow the requested operation.
- PRCF-02025: Internal error: {0}
-
Cause: An internal error occurred. The included value is an internal identifier.
- PRCF-02026: File name is too long: {0}
-
Cause: An internal error occurred.
- PRCF-02027: Link path is too long: {0}
-
Cause: An internal error occurred.
- PRCF-02028: Failed to get system information for {0}: {1}
-
Cause: An attempt to get system information failed
- PRCF-02029: The transfer operation completed with partial failures.
-
Cause: The operation failed to transfer all of the contents to one or more nodes.
- PRCF-02030: The source and destination directories ({0}) on node {1} are the same.
-
Cause: The source and destination directory on the node where Java is installed were the same.
- PRCF-02031: Parallel transfer workload distribution error.
-
Cause: An error occurred while distributing the transfer workload to multiple threads.
- PRCF-02035: The copy operation failed on the following nodes: {0}.
-
Cause: The copy operation failed to copy the file or directory to the remote nodes due to an error in the supplied credentials for the remote node connection or because the user did not have sufficient privileges.
- PRCF-02036: The copy operation failed.
-
Cause: The copy operation failed to copy the file or directory to the remote nodes.
- PRCF-02040: Error while opening socket. Details:\n{0}
-
Cause: An I/O error occurred while opening the socket.
- PRCF-02041: The transfer failed for all nodes. Details:\n{0}
-
Cause: All nodes failed to receive the data due to critical errors.
- PRCF-02042: invalid command line syntax, correct syntax:"{0}"
-
Cause: An attempt to execute a command was rejected because the command syntax was invalid.
- PRCF-02043: failed to allocate memory.
-
Cause: The attempted operation was unable to complete because insufficient system memory was available.
- PRCF-02044: Failed to parse node plan details. Internal error occured: {0}
-
Cause: An internal error occurred. The value displayed is an internal identifier.
- PRCF-02045: Error while binding socket for node "{0}" and port {1}. OS error string: {2}
-
Cause: The requested operation could not be completed because an I/O error occurred while attempting to bind the socket to establish the necessary communication channel.
- PRCF-02046: Listen socket could not be created for node "{0}" and port {1}. OS error string: {0}
-
Cause: The requested operation could not be completed because an I/O error occurred while attempting to perform a 'listen' the socket to establish the necessary communication channel.
- PRCF-02047: Failed to accept socket connection. OS error string: {0}
-
Cause: The requested operation could not be completed because an I/O error occurred while attempting to accept the socket connection to establish the necessary communication channel.
- PRCF-02048: Invalid command identified. Details: {0}
-
Cause: An internal error occurred. The included value is an internal identifier.
- PRCF-02049: Error while trying to create directory "{0}" on node {1}. Details: {2}
-
Cause: The requested operation could not be completed because an error occurred while attempting to create the indicated destination directory. Either there was already a file or symbolic link with the indicated path that was not a directory, or the directory could not be created. Specific failure data is displayed following the message.
- PRCF-02050: Error while trying to modify permissions for "{0}" on node {1}. Details: {2}
-
Cause: The requested operation could not be completed because an error occurred while trying to modify permissions.
- PRCF-02051: Failed to create link from source path "{0}" to destination path "{1}" on node {2}. Details: {3}
-
Cause: The requested operation could not be completed because an error occurred while trying to create a link from the indicated source path to the indicated destination.
- PRCF-02052: Failed to unlink path "{0}" on node {1}. Details: {2}
-
Cause: The requested operation could not be completed because an error occurred while trying to unlink the indicated path.
- PRCF-02053: Failed to read data from socket while writing to file "{0}" on node {1}. Details: {2}
-
Cause: The requested operation could not be completed because an error occurred while reading data from the socket.
- PRCF-02054: The source file "{0}" became larger during the transfer.
-
Cause: The indicated source file continued to grow after the transfer was initiated. Because the transfer size was determined at the start of the operation, the resulting file was not a complete copy of the source.
- PRCF-02055: The transferred binary was not executed successfully on node: "{0}". Details: {1}
-
Cause: The requested operation could not be completed because an error occurred while executing the transferred binary on the indicated node. Specific failure data is displayed following the message.
- PRCF-02056: The copy operation failed on node: "{0}". Details:\n{1}
-
Cause: The requested operation could not be completed because an error occurred while copying the file or directory to the indicated node. Either the user did not have credentials for connecting to the node or the user did not have sufficient privileges. Specific failure data is displayed following the message.
- PRCF-02057: failed to copy file "{0}" to "{1}"
-
Cause: An error occurred while copying the file from the specified path to the indicated destination path.
- PRCF-02058: Timeout occurred while executing transferred binary on node: "{0}". Details: {1}
-
Cause: The requested operation could not be completed within the time limit while executing the transferred binary on the indicated node. Specific failure data is displayed following the message.
- PRCF-02059: Timeout occurred during copy operation on node: "{0}". Details: {1}
-
Cause: The requested operation could not be completed within the time limit. Specific failure data is displayed following the message.
- PRCF-02060: Error executing the transfer binary. Details: {0}
-
Cause: An error occurred while executing the transfer binary. Specific failure data is displayed following the message.
- PRCF-02061: Invalid request for user authenticated transfer to multiple nodes.
-
Cause: A user authenticated transfer was attempted between the local and more than one remote node.
- PRCF-02062: remote command execution error on node "{0}":\n{1}
-
Cause: A user authenticated remote execution attempt failed.
- PRCF-02063: Connection to node "{0}" was lost while receiving data.
-
Cause: An attempted file transfer operation failed because the connection to the indicated remote node was lost.
- PRCF-02064: Connection to node "{0}" was lost while sending data.
-
Cause: An attempted file transfer operation failed because the connection to the indicated remote node was lost.
- PRCF-02065: Error sending command "{0}". Details:\n{1}
-
Cause: An attempted file transfer operation failed because an error occurred while sending the indicated command.
- PRCF-02066: Error sending file "{0}". Details:\n{1}
-
Cause: An attempted file transfer operation failed because an error occurred while sending the indicated file.
- PRCF-02067: Reply mismatch: Expected "{0}", but received "{1}" from node "{2}"
-
Cause: An attempted file transfer operation failed because an error occurred on the indicated node while creating a directory or symbolic links or writing to a file.
- PRCF-02071: The command "{0}" failed on the following nodes: {1}.
-
Cause: An attempt to run the specified command failed on the indicated nodes.
- PRCF-02072: The command "{0}" failed.
-
Cause: An attempt to run the specified command failed.
- PRCF-02073: Invoking copy method failed. Details:\n{0}
-
Cause: An attempt to invoke the copy method failed.
- PRCF-02074: failed to copy file {0} to remote nodes {1}
-
Cause: An attempt to copy the file failed.
- PRCF-02075: File transfer error from node {0} to node {1}. Unable to retrieve error details.
-
Cause: An error occurred during a file transfer between the indicated nodes, but due to an unexpected protocol error, the error details could not be retrieved.
- PRCF-02076: Copy operation failed on node "{0}" because the connection is lost.
-
Cause: The copy operation could not be completed because the connection was lost.
- PRCF-02077: Copy operation failed on node "{0}" with the following errors:\n{1}
-
Cause: The copy operation could not be completed because it encountered the indicated errors.
- PRCF-02078: Copy operation failed on node "{0}" with too many errors such as the following:\n
-
Cause: The copy operation could not be completed because it encountered too many errors.
- PRCF-02079: Source directory "{0}" is the same as the destination directory in the copy operation.
-
Cause: The source directory for the copy operation on the local node was the same as the destination directory.
- PRCF-02080: The copy operation on the local node failed with the following errors: {0}
-
Cause: The copy operation could not be completed because it encountered the indicated errors.
- PRCF-02081: unable to detect whether the user can write to directory '{0}' on the following nodes: {1}
-
Cause: An attempt to copy the files under the indicated directory failed because an error occurred while determining whether the directory was writable by the user on all nodes.
- PRCF-02082: Directory '{0}' is not writable on the following nodes: {1}
-
Cause: An attempt to copy the files under the indicated directory failed, because write permissions were not granted to its path on the specified nodes.