5.4 TCP Receiver Error Messages

251: The Upgrade Service has failed

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Explanation: The Upgrade service copies the ZENworks for Desktops 4.x residual files to specific directories and updates zeninvComponentStaus, the Inventory Service object's attribute. The residual files are then converted to the ZENworks 7 Desktop Management format by the TCP Receiver.
Possible Cause: The Upgrade service has not completed copying the residual files.
Action: Restart the Inventory service. For more information, see Starting and Stopping the Inventory Service in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

304: Unable to open the file filename

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Possible Cause: The disk on the Inventory server is full.
Action: Ensure that there is free disk space on the server
Possible Cause: The directory that contains the file does not exist.
Action: Ensure that the directory that contains the file exists on the server.
Possible Cause: There is no Read and Write access to the file in the directory.
Action: Ensure that the file has Read and Write access.
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

310: Input-output failure. Unable to close the file filename

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Warning
Explanation: This error occurs when the TCP Receiver tries to close the file while processing it.
Possible Cause: The input-output buffers are not closed.
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

312: Network connection lost or closed while writing the data to the network. Verify the network connections

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Warning
Action: Ensure that the network is up and running.

313: Network connection lost or closed while reading the data from the network. Verify the network connections

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Warning
Action: Ensure that the network is up and running.

315: Unable to accept connection from the Sender

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Warning
Possible Cause: The socket has not been created properly.
Action: Ensure that the network is up and running.

316: Unexpected data read from the network by the Sender/Receiver. Verify the network connections

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Warning
Possible Cause: The network connection was lost or closed while the TCP Receiver is reading the data from the network.
Action: Ensure that the network is up and running.

319: Unable to send the file filename from the Sender to the Receiver

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Explanation: This error occurs when the .zip file cannot be sent from the ZENworks for Desktops 4.x Sender to the TCP Receiver on the network.
Possible Cause: The network connection was lost or closed while the TCP Receiver was reading the data from the network.
Action: Ensure that the network is up and running.
Possible Cause: The disk on the Inventory server is full.
Action: Ensure that there is free disk space on the server.
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

322: Input-output error while closing the buffers

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Warning
Possible Cause: The input-output buffers are not closed properly.
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

324: Directory directory_name does not exist

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Explanation: The TCP Receiver accesses the files in the directory for processing the scan information.
Action: Ensure that the directory exists on the Inventory server.
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

325: The Receiver could not bind to accept connections from the Sender at Time in Milliseconds value

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Possible Cause: The default port numbers (between 1025 and 65432) are not available.
Action: Ensure that there are free port numbers in the range 1025 and 65432. If the port numbers are used by other applications, close the applications to free up the ports.

2651: Could not extract Property values because sanity check failed on ZIP_filename

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Informational
Explanation: The TCP Receiver processes the .zip files that are remaining after a ZENworks for Desktops 4.0.1 server has been upgraded to ZENworks 7 Desktop Management.

This error occurs if a .zip file is invalid. The TCP Receiver continues processing the remaining .zip files.

Action: None.

2652: Invalid zip file name ZIP_filename

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Informational
Explanation: The TCP Receiver processes the .zip files that are remaining after a ZENworks for Desktops 4.0.1 server has been upgraded to ZENworks 7 Desktop Management.

This error occurs if the name of the .zip file is invalid. The TCP Receiver continues processing the remaining .zip files.

Action: None.

2653: ZIP_filename could not be unzipped into the directory directory_filename

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Possible Cause: The disk on the Inventory server is full.
Action: Ensure that there is free disk space on the server.
Possible Cause: The directory that contains the file does not exist.
Action: Ensure that the directory that contains the file exists on the server.
Possible Cause: There is no Read and Write access to the file in the directory.
Action: Ensure that the file has Read and Write access.

2654: Error converting Property file old_filename to new_filename

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Informational
Explanation: The TCP Receiver processes the .zip files that are remaining after a ZENworks for Desktops 4.x server has been upgraded to ZENworks 7 Desktop Management.
Possible Cause: The property file is not in a valid ZENworks for Desktops 4.x format. The TCP Receiver continues processing the remaining .zip files.
Action: None.

2655: Unable to unzip the file ZIP_filename

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Possible Cause: The .zip file is corrupted.
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

2656: Unable to close the file ZIP_filename

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

2657: Invalid number of Property files found: number_of_property_files

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Informational
Possible Cause: There are some property files of the previous TCP Receiver execution in the directory or there is more than one property file present in the .zip file. The TCP Receiver continues processing the remaining files.
Action: None.

2658: An internal error occurred while trying to convert .str files

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.
Action: If the problem persists, contact Novell Support.

2659: Error converting .str files in directory_name

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Informational
Possible Cause: The .str files are not in a valid ZENworks 7 Desktop Management format.
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

2660: Unable to find .str files in directory_name for compression

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Explanation: To form a ZENworks 7 Desktop Management .zip file, str files in the directory are collected and compressed.
Possible Cause: There are no .str files for compression.
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.
Action: If the problem persists, contact Novell Support.

2661: Unable to delete file filename in directory directory_name

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Explanation: The ZENworks for Desktops 4.x .zip files are converted to ZENworks 7 Desktop Management format and moved to the appropriate directory for processing by ZENworks 7.
Possible Cause: The ZENworks for Desktops 4.x .zip file was not deleted from the directory.
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

2662: Unable to move file filename to directory directory_name

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Explanation: The ZENworks for Desktops 4.x .zip files are converted to ZENworks 7 Desktop Management format and moved to the appropriate directory for processing by ZENworks 7.
Possible Cause: The ZENworks for Desktops 4.x .zip file was not deleted from the directory.
Possible Cause: The disk on the Inventory server is full.
Action: Ensure that there is free disk space on the server.
Possible Cause: The file is locked by some other application.
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

2663: Fatal error: ZIP file processing exceeded retry

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Explanation: The ZENworks for Desktops 4.x .zip files are converted to ZENworks 7 Desktop Management format. During the processing, other Inventory components such as the Storer and the ZENworks 7 Receiver try to obtain a handle on the .zip file for further processing.
Possible Cause: The lock on the .zip file has not been released.
Action: Restart the Inventory service. For more information, see Starting and Stopping the Inventory Service in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

2664: Unable to create directory directory_name

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Explanation: The ZENworks for Desktops 4.x .zip files are converted into ZENworks 7 Desktop Management .zip files and are transferred to the appropriate directory for processing by ZENworks 7 Desktop Management components.
Possible Cause: The appropriate directory is not found on the Inventory server.
Action: Ensure that the directory exists on the Inventory server.
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

2665: Unable to find files with extension file_extension in directory_name

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Explanation: Files such as .str and .zip are converted from ZENworks for Desktops 4.x to ZENworks 7 Desktop Management format.
Possible Cause: The files are not found in the appropriate directories.
Action: Restart the TCP Receiver from the Service Manager. For more information, see Understanding the Inventory Service Manager in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.
Action: If the problem persists, contact Novell Support.

2666: Unable to obtain lock on filename with component_name

Source: ZENworks Desktop Management; Workstation Inventory; TCP Receiver
Severity: Critical
Explanation: The ZENworks for Desktops 4.x .zip files are converted to ZENworks 7 Desktop Management format. During the processing, other Inventory components such as the Storer and the ZENworks 7 Desktop Management Receiver tries to obtain a handle on the .zip file for further processing.
Possible Cause: The handle on the .zip file is not found.
Action: Restart the Inventory service. For more information, see Starting and Stopping the Inventory Service in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.