Cause: A directory that did not exist was chosen for the top-level directory of the directory map.

Cause: An existing file which was not a directory was provided as top-level directory.

Cause: The file was not found in the file system.

Cause: The link destination was not found in the file system.

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.

Cause: The directory existed already in the directory map.

Cause: The file existed already in the directory map.

Cause: The link existed already in the directory map.

Cause: The parent directory of the content (directory, file or symbolic link) that was being processed did not exist.

Cause: The indicated object was expected to be a directory, but it was not.

Cause: The content (i.e., directory, file or symbolic link) could not be removed from the directory map as it did not exist there.

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).

Cause: The user tried to acquire information about an empty 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.

Cause: The content to add to the directory map was not found in the file system.

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.

Cause: The content to remove from the directory map was not found in the file system.

Cause: An unexpected error condition was detected during reading the exclude-list or include-list file.

Cause: The user was running on Windows OS.

Cause: The content that was expected to be a file which turned out not to be a file.

Cause: The content that was expected to be a valid pathname which turned out to be an invalid one.

Cause: The specified pathname does not exist in the file system.

Cause: An existing symbolic link that resolves to a pathname that does not exist.

Cause: An existing symbolic link that resolves to a non-directory pathname was provided as top-level directory.

Cause: An I/O error occurred while trying to open the file for reading.

Cause: An I/O error occurred while reading or closing the file.

Cause: An I/O error occurred while trying to create the file for writing.

Cause: An I/O error occurred while writing or closing the file.

Cause: An error occurred while trying to create the directory.

Cause: This is an internal error. The value for the specified parameter was null.

Cause: This is an internal error. The value for the specified array element was null.

Cause: This is an internal error. The value for the specified list element was null.

Cause: A node name appeared more than once in the input list.

Cause: Could not establish connection to the provided host/IP address using the port number reported.

Cause: The connection to the remote node with the specific node ID was lost.

Cause: The command was not executed successfully. The local node received a reply from the remote node that was different from the expected one.

Cause: While trying to save the directory listing to a file, the operation could not be completed successfully.

Cause: An internal error caused a a mismatch between the number of remote nodes and the number of remote node ports.

Cause: An empty list of remote nodes was passed as argument.

Cause: The port number for the remote node was either not a number at all or not an integer number.

Cause: The port number for the remote node was indeed an integer number but either less than 1 or greater than 65535.

Cause: The user either provided an empty list of remote nodes or each remote node of the list had invalid format.

Cause: All the attempts to connect to the remote nodes that had valid format failed.

Cause: The file existed in the file system but could not be read successfully.

Cause: The top-level directory was not found in the file system.

Cause: The CRS Home did not exist or 'oui' was not a directory under the CRS Home.

Cause: The command ('mkdir', 'mkfile', 'mklink' or 'wrfile') failed while executing on the remote node.

Cause: At least one of the commands 'mkdir', 'mkfile', 'mklink' or 'wrfile' failed while executing on one or more remote nodes.

Cause: The binary file was not found under the expected location.

Cause: Misbehavior of the transfer binary on the provided node.

Cause: Unsuccessful execution of the transfer binary.

Cause: No IP address for the local host could be found.

Cause: No IP address for the node host could be found.

Cause: An internal error caused a a mismatch between the number of remote nodes and the number of remote destination directories.

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.

Cause: The file permissions for the listed contents did not allow the requested operation.

Cause: The file permissions of the listed directory did not allow the requested operation.

Cause: An internal error occurred. The included value is an internal identifier.

Cause: An internal error occurred.

Cause: An internal error occurred.

Cause: An attempt to get system information failed

Cause: The operation failed to transfer all of the contents to one or more nodes.

Cause: The source and destination directory on the node where Java is installed were the same.

Cause: An error occurred while distributing the transfer workload to multiple threads.

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.

Cause: The copy operation failed to copy the file or directory to the remote nodes.

Cause: An I/O error occurred while opening the socket.

Cause: All nodes failed to receive the data due to critical errors.

Cause: An attempt to execute a command was rejected because the command syntax was invalid.

Cause: The attempted operation was unable to complete because insufficient system memory was available.

Cause: An internal error occurred. The value displayed is an internal identifier.

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.

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.

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.

Cause: An internal error occurred. The included value is an internal identifier.

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.

Cause: The requested operation could not be completed because an error occurred while trying to modify permissions.

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.

Cause: The requested operation could not be completed because an error occurred while trying to unlink the indicated path.

Cause: The requested operation could not be completed because an error occurred while reading data from the socket.

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.

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.

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.

Cause: An error occurred while copying the file from the specified path to the indicated destination path.

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.

Cause: The requested operation could not be completed within the time limit. Specific failure data is displayed following the message.

Cause: An error occurred while executing the transfer binary. Specific failure data is displayed following the message.

Cause: A user authenticated transfer was attempted between the local and more than one remote node.

Cause: A user authenticated remote execution attempt failed.

Cause: An attempted file transfer operation failed because the connection to the indicated remote node was lost.

Cause: An attempted file transfer operation failed because the connection to the indicated remote node was lost.

Cause: An attempted file transfer operation failed because an error occurred while sending the indicated command.

Cause: An attempted file transfer operation failed because an error occurred while sending the indicated file.

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.

Cause: An attempt to run the specified command failed on the indicated nodes.

Cause: An attempt to run the specified command failed.

Cause: An attempt to invoke the copy method failed.

Cause: An attempt to copy the file failed.

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.

Cause: The copy operation could not be completed because the connection was lost.

Cause: The copy operation could not be completed because it encountered the indicated errors.

Cause: The copy operation could not be completed because it encountered too many errors.

Cause: The source directory for the copy operation on the local node was the same as the destination directory.

Cause: The copy operation could not be completed because it encountered the indicated errors.

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.

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.