5.3 Sender and Receiver Error Messages

301: Unable to create the Property file filename

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: For each roll-up scheduled by the Sender, the .str files from the entmergedir directory are placed in the entpushdir directory and compressed to a .zip file. The .zip file is again compressed with a .prp file into a .zip file. The .prp file contains information about the .zip file.

This error occurs if the Sender fails to create the .prp file.

Possible Cause: The disk on the Inventory server is full.
Action: Ensure that there is free disk space on the Inventory server.
Possible Cause: The entpushdir directory is not found on the Inventory server.
Action: Ensure that the entpushdir directory exists on the Inventory server.
Possible Cause: There is no write access for the entpushdir directory.
Action: Ensure that the directory has write permission.

302: Unable to read the Property file filename

Source: ZENworks Desktop Management; Workstation Inventory; Sender and Receiver
Severity: Critical
Explanation: The Property file contains the roll-up information of the .zip file. For each roll-up scheduled by the Sender, the .str files from the entmergedir directory are placed in entpushdir directory and compressed to a .zip file. The .zip file is again compressed with a .prp file into a .zip file.

The Sender and the Receiver read the property file in the .zip file to verify if the compressed file is in .zip format and if the .zip file is an Inventory .zip file. The inventory components also read the file to get the roll-up information of the .zip file.

This error occurs if the Sender or the Receiver is unable to read the .prp file.

Possible Cause: The entpushdir directory is not found on the Inventory server.
Action: Ensure that the entpushdir directory exists on the Inventory server.
Possible Cause: There is no Read access for the files in the entpushdir directory.
Action: Ensure that the files have Read access.
Action: If the source of the problem is the Receiver component, restart the 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.

If the source of the problem is the Sender component, you do not need to restart the Sender because the roll-up time scheduled in the Roll-Up policy triggers the Sender.

303: Unable to unzip the file zip_filename

Source: ZENworks Desktop Management; Workstation Inventory; Receiver
Severity: Critical
Explanation: The Receiver internally decompresses the .zip file. If it fails to do so, it retries. If it does not succeed, the Receiver goes down.
Possible Cause: The disk on the Inventory server is full.
Action: Ensure that there is free disk space on the server.
Action: Restart the 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.

304: Unable to open the file path_name/filename

Source: ZENworks Desktop Management; Workstation Inventory; Receiver
Severity: Critical
Explanation: This error occurs when the Receiver is processing the .zip file. The Receiver internally decompresses the .zip file. If it fails to do so, it retries. If it does not succeed, the Receiver goes down.
Possible Cause: The disk on the Inventory server is full.
Action: Ensure that there is free disk space on the server.
Action: Restart the 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.

306: zip_filename is corrupted, probably during transmission

Source: ZENworks Desktop Management; Workstation Inventory; Receiver
Severity: Critical
Explanation: The Receiver internally decompresses the .zip file. If it fails to do so, it retries. If it does not succeed, the Receiver goes down.
Possible Cause: The disk on the Inventory server is full.
Action: Ensure that there is free disk space on the server.
Action: Restart the 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.

307: Unable to create the .zip file filename

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: The Sender creates a .zip file of all .str files. The .zip file is again compressed with a .prp file into a .zip file.

This error occurs if the Sender fails to create the .zip file.

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 containing the .str files does not exist.
Action: Ensure that the directory exists on the Inventory server.
Possible Cause: There is no Read and Write access to the files in the directory.
Action: Ensure that the directory has Read and Write access for the files in the directory.

308: Compression failure. filename.str is not compressed to a .zip file

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: The Sender compresses the .str files in the entpushdir directory of the server as a .zip file and also creates a Property file.
Possible Cause: There is an internal problem with the Java* utility for creating a .zip file of the .str files.
Action: If the problem persists, contact Novell Support.

309: Input-output failure. filename.str is not compressed to a .zip file

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: The Sender compresses the .str files in the entpushdir directory of the Inventory server as a .zip file and also creates a Property file.
Possible Cause: The directory that contains the files does not exist.
Action: Ensure that the directory exists on the Inventory server.
Possible Cause: There is no Read and Write access to the files in the directory.
Action: Ensure that the directory has Read and Write access for the files in the directory.
Possible Cause: The disk on the Inventory server is full.
Action: Ensure that there is free disk space on the Inventory server.

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

Source: ZENworks Desktop Management; Workstation Inventory; Sender and Receiver
Severity: Warning
Explanation: This error occurs when the inventory component closes the intermediate files after processing them.
Possible Cause: The input-output buffers are not closed.
Action: If the source of the problem is the Receiver component, restart the 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.

If the source of the problem is the Sender component, you do not need to restart the Sender because the roll-up time scheduled in the Roll-Up policy triggers the Sender.

311: Could not extract Cascading attributes because sanity check failed

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: The error occurs if the Sender is unable to write to the roll-up log.
Action: Contact Novell Support.

317: Unable to copy the file filename from the entpushdir directory to the dbdir directory

Source: ZENworks Desktop Management; Workstation Inventory; Receiver
Severity: Critical
Explanation: The Receiver on the Inventory server that has the database attached to it copies the files from the entpushdir to the dbdir directory after the .zip file is received from the lower-level Inventory server.
Possible Cause: The disk on the Inventory server is full.
Action: Ensure that there is free disk space on the Inventory server.
Possible Cause: The directory that contains the files does not exist.
Action: Ensure that the directory exists on the Inventory server.
Possible Cause: There is no Write access to the files in the directory.
Action: Ensure that the directory has Write access for the files in the directory.
Action: If the source of the problem is the Receiver component, restart the 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.

If the source of the problem is the Sender component, you do not need to restart the Sender because the roll-up time scheduled in the Roll-Up policy triggers the Sender.

320: Unable to reach the Receiver receiver_host_address

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: This error occurs when the Sender cannot establish the connection with the Receiver.
Possible Cause: The Receiver address in the eDirectory is not correct.
Action: Specify a valid address for the Receiver in the Roll-Up policy. For more information, see Configuring the Roll-Up Policy in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.
Possible Cause: The Receiver is down.
Action: Restart the Receiver. If the problem persists, restart the ZENworks 7 Desktop Management components.
Possible Cause: The address is not properly configured in eDirectory.
Action: Verify the Receiver address in eDirectory with the address of the Receiver that the Sender is establishing the connection with.
Possible Cause: The network is down.
Action: Ensure that the network is up and running and the network connections are active.

324: Directory directory_name does not exist

Source: ZENworks Desktop Management; Workstation Inventory; Sender and Receiver
Severity: Critical
Explanation: The Inventory component accesses the files in the directory for processing the scan information.
Action: Ensure that the directory exists on the Inventory server.
Action: If the source of the problem is the Receiver component, restart the 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.

If the source of the problem is the Sender component, you do not need to restart the Sender because the roll-up time scheduled in the Roll-Up policy triggers the Sender.

327: Sender establishes connection with Receiver after a previous attempt to connect failed

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Informational
Explanation: When the Sender is unable to connect with the Receiver, it logs an error message with the cause for the failure in the error log. After the Sender successfully establishes a connection with the Receiver, the status is logged in the error log.

328: Unable to read Security Directory from sender.properties

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: The Sender failed to read the SECURITYDIR value from the Inventory_server_installation_directory\zenworks\inv\server\wminv\properties\sender.properties file.
Possible Cause: The sender.properties file is corrupt.
Action: Reinstall the Inventory server. For more information, see Reinstalling Workstation Inventory in Uninstall/Reinstall in the Novell ZENworks 7 Desktop Management Installation Guide.
Possible Cause: The securitydir entry is missing from sender.properties.
Action: Add the following entry to sender.properties: 
security_directory=sys:\\public\\zenworks\\wminv\\
properties

NOTE:If the entry already exists, delete it, save the file, and add it again.

329: The Receiver service on the server server_name is currently down

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: The Sender cannot roll up the scan information because the Receiver on the next-level Inventory server is down. The Sender retries connecting to the Receiver for approximately 23 hours before it discontinues trying.
Action: On the next-level Inventory server, start the 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 Sender fails to connect to the Receiver even after the retries, contact Novell Support

330: Unable to contact the receiver on the server server_name

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: The Sender failed to contact the Receiver on the next-level Inventory server. The Sender retries connecting to the Receiver for approximately 23 hours before it discontinues trying.
Action: On the next-level Inventory server, restart the 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 Sender fails to connect to the Receiver even after the retries, contact Novell Support.

332: An internal error occurred while getting the zeninvRollupTime

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: An internal error occurred while getting the zeninvRollupTime.
Action: Contact Novell Support.

333: Invalid URL for the CascadeBaseTime service

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: An internal error occurred while getting the CascadeBaseTime.
Action: Contact Novell Support.

334: An internal error occurred while starting the CascadeBaseTimeServer

Source: ZENworks Desktop Management; Workstation Inventory; Receiver
Severity: Critical
Explanation: An internal error occurred while starting the CascadeBaseTimeServer.
Action: Contact Novell Support.

335: Socket Input-Output error occurred while getting the zeninvRollupTime

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: An internal error occurred while getting the zeninvRollupTime. The Sender retries connecting to the Receiver for approximately 23 hours before it discontinues trying.
Possible Cause: The next-level Inventory server is not up and running.
Action: Ensure that the next-level Inventory serve is up and running.
Possible Cause: The next-level Inventory server is not reachable.
Action: Ensure that the next-level Inventory server is reachable.
Possible Cause: The ZENworks Web Server is not running on the next-level Inventory server.
Action: Ensure that the ZENworks Web Server and the Inventory services are running on the next-level Inventory server.
Possible Cause: This problem might occur on a NetWare Inventory server with Native File Access Pack installed. This NetWare server has one or more volumes exposed as CIFS shares and does not have a DNS name configured.

If the NetWare server does not have a DNS name configured, the CIFS service is given a NetBIOS name, and the Roll-up policy assigns the NetBIOS name as the host name.

This error occurs if the Sender on the NetWare server fails to resolve the NetBIOS name to an IP address.

Action: Choose an IP address instead of the NetBIOS name in the Roll-up policy. For more information, see Configuring the Roll-Up Policy in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.
Action: If the problem persists, contact Novell Support

338: An internal error occurred while transferring the zip file to the Receiver running on the server server_name

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: An internal error occurred while transferring the .zip file to the Receiver running on the next level Inventory server.
Action: Contact Novell Support.

339: Invalid URL for the Inventory File Service on the server server_name

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: An internal error occurred while transferring the .zip file to the Receiver running on the next-level Inventory server. The Sender retries connecting to the Receiver for approximately 23 hours before it discontinues trying.
Action: If the Sender fails to connect to the Receiver even after the retries, contact Novell Support.

340: The Receiver on server server_name is currently busy with other requests

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: The Receiver on the next-level Inventory server is currently busy with other requests. The Sender retries connecting to the Receiver for approximately 23 hours before it discontinues trying.
Action: If the Sender fails to connect to the Receiver even after the retries, contact Novell Support.

341: Input-Output error occurred at the Receiver running on server server_name while receiving the zip file

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: An input-output error occurred at the Receiver running on the next-level Inventory server while receiving the .zip file. The Sender retries connecting to the Receiver for approximately 23 hours before it discontinues trying.
Action: If the Sender fails to connect to the Receiver even after the retries, contact Novell Support.

342: Socket Input-Output error occurred while transferring the zip file to the Receiver running on server server_name

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Explanation: A socket input-output error occurred at the Receiver running on the next-level Inventory server while receiving the .zip file. The Sender retries connecting to the Receiver for approximately 23 hours before it discontinues trying.
Possible Cause: The next-level Inventory server is not up and running.
Action: Ensure that the next-level Inventory server is up and running.
Possible Cause: The next-level Inventory server is not reachable.
Action: Ensure that the next-level Inventory server is reachable.
Possible Cause: The ZEN Web Server is not running on the next-level Inventory server.
Action: Ensure that the ZEN Web Server and the Inventory services are running on the next-level Inventory server.
Possible Cause: This problem might occur on a NetWare Inventory server with Native File Access Pack installed. This NetWare server has one or more volumes exposed as CIFS shares and does not have a DNS name configured.

If the NetWare server does not have a DNS name configured, the CIFS service is given a NetBIOS name, and the Roll-up policy assigns the NetBIOS name as the host name.

This error occurs if the Sender on the NetWare server fails to resolve the NetBIOS name to an IP address.

Action: Choose an IP address instead of the NetBIOS name in the Roll-up policy. For more information, see Configuring the Roll-Up Policy in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.
Action: If the problem persists, contact Novell Support

343: Unable to obtain a lock on the target file

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Action: Contact Novell Support.

344: An internal error occurred while starting the Inventory File Service

Source: ZENworks Desktop Management; Workstation Inventory; Receiver
Severity: Critical
Action: Contact Novell Support.

345: The target directory on the server server_name, where the zip file is to be copied is invalid

Source: ZENworks Desktop Management; Workstation Inventory; Receiver
Severity: Critical
Action: Restart the 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.

346: The target directory on the server server_name, where the zip file is to be copied, does not have the required permission

Source: ZENworks Desktop Management; Workstation Inventory; Receiver
Severity: Critical
Action: Contact Novell Support.

347: Internal error while connecting to the Receiver on server server_name

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Action: Contact Novell Support.

348: An internal error occurred. Unable to start Receiver Service

Source: ZENworks Desktop Management; Workstation Inventory; Receiver
Severity: Critical
Action: Restart the 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.

349: Unable to change stored status for the file filename

Source: ZENworks Desktop Management; Workstation Inventory; Receiver
Severity: Critical
Explanation: The Receiver modifies the stored status for the .zip file. If there is a failure while doing this, the Receiver retries. If it does not succeed, the Receiver Service goes down.
Possible Cause: The disk on the Inventory server is full.
Action: Ensure that there is free disk space on the server.
Action: Restart the Receiver from the Service Manager.
Action: If the problem persists, contact Novell Support.

350: File filename in dbdir is locked

Source: ZENworks Desktop Management; Workstation Inventory; Receiver
Severity: Critical
Explanation: The Receiver processes the .zip file received from the lower-level Inventory servers and copies the file to dbdir. This error occurs if the Storer has locked the file and the Receiver is not able to access this file even after retrying. The Receiver service exits on getting this error.
Action: Do the following:

  1. Stop the Storer 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.

  2. Restart the Receiver and the Sender 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.

  3. Start the Storer. For more information, see Starting and Stopping the Inventory Service in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

351: Error in Sender on the server server_name. Invalid firewall proxy address

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Action: Ensure that the proxy address in the Roll-Up policy is correct. For more information, see Configuring the Roll-Up Policy in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

352: Error in Sender on the server server_name. Invalid firewall proxy port

Source: ZENworks Desktop Management; Workstation Inventory; Sender
Severity: Critical
Action: Ensure that the proxy port in the Roll-Up policy is correct. For more information, see Configuring the Roll-Up Policy in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

354: Unable to write the Inventory Service DN to the property file

Source: ZENworks Desktop Management; Workstation Inventory; Sender and Receiver
Severity: Critical
Possible Cause: The Sender or the Receiver fails to get the Inventory Service object DN.
Action: Contact Novell Support.

355: Unable to write the server name to the property file

Source: ZENworks Desktop Management; Workstation Inventory; Sender and Receiver
Severity: Critical
Possible Cause: The Sender or the Receiver fails to get the Inventory server name.
Action: Contact Novell Support.