![]() |
![]() |
![]() |
![]() |
Enterprise User Manual
Appendix A
Error Messages
Progress and Error Log Messages
Failed to write package defn. file [Package Definition].PD. Please check the Client is accessible
The Offline Area server may be inaccessible, or the access control settings could be wrong. This message may also be displayed if an online Client is inaccessible.
Skipping installation of [Package]. Package is already installed.
The Agent considers the package is already installed, based on the Check paths entered in the Package Distribution Definition. This message indicates that the specified Package is being removed from the Pending queue; the Package itself is not deleted.
Network load control is delaying installation of Package [Package]
Software distributions can impose a significant load on a network. The Enterprise Agent includes an algorithm, which allows you to spread installations across several days. You can control this with the Target Completion date setting when performing a Job.
Installing package: [Package]
The package installation is commencing.
Installed package [Package] successfully.
The package installation has successfully completed.
Reboot underway during installation of [Package]. Install confirmation or restart will happen on the next run
This Package is rebooting the Client PC. The Agent will perform the Check paths test when the PC restarts and will then report whether the Package installed successfully.
User refused installation of [Package] at this time. [Number] refusals left
If a Refusal Limit was specified for the installation, the user is given the opportunity to postpone the installation before it starts. When the refusals have been used, the installation becomes mandatory.
Reboot/shutdown request received when prompting for installation
The Client PC is being rebooted prior to the installation.
Reboot required for package installation
The package installation needs to reboot the Client PC before the installation can be completed. The user is prompted with a message.
Other application(s) have refused the reboot
An application running on the Client PC has refused an attempted reboot. This can happen when an application prompts a user to save their changes and the user cancels the close message.
User refused system reboot at this time
When prompted, the Client PC user chose not to perform a system reboot.
[Package] was installed successfully. Thank you
The Installation has completed successfully.
Skipping installation of package [Package].
This Client is not eligible for this installation - check the Operating Systems specified.
The Client PC is unable to install this Package.
The Client PC is running an operating system which is not supported by this installation.
Deleting package entry [Package] (beyond expiry date)
The expiry date for the distribution Job has been reached without the package being installed.
Failed to install package [Package]. Insufficient disk space to proceed with installation. This package is being put into Holding status
The Client PC failed the free disk space check as specified in the Package's Distribution Definition.
Failed to install package [Package]. Insufficient privilege to proceed with installation. This package is being put into Holding status
The Agent is not running with Admin-level privilege and this Package requires a privileged install.
A non-privileged user on Windows NT, 2000, XP or 2003 cannot perform an Admin install. The Software Distribution Agent can run as a Windows service, to give it access to the privileged environment that is required to install applications, such as Service Packs.
Failed to install package [Package]. No user account specified for this installation. The Agent Service always requires an account.
The Agent is not running under an appropriate User Account to install the Package.
Failed to install package [Package]. Installation of [Package] failed (Pre-Process command failure prevents installation from continuing). This package is being put into Holding status
The Pre-Process command specified in the Package's Distribution Definition failed to execute.
Failed to install package [Package]. Installation of [Package] failed (unable to connect to kit source [Kit path]). This package is being put into Holding status
The location of the installation kit cannot be accessed. This location is specified in the Package's Distribution Definition, although the kit path can be changed using the Software Distribution Wizard.
Failed to install package [Package]. Installation of [Package] failed (launch error).
This package is being put into Holding status
An error occurred when attempting to use the Installation command line. Check that the Kit location and the Installation command are both correct and that any user information is valid.
Failed to install package [Package]. Error triggering system reboot to complete package installation. This package is being put into Holding status
This error will occur if the Agent needs to reboot the Client PC but is unable to do so.
Failed to install package [Package]. Installation of [Package] failed (post-installation check failed). This package is being put into Holding status
The installation has been performed, but none of the Check paths specified in the Package Distribution Definition are being identified. Either the Check paths specified in the Package's Distribution Definition are incorrect, or the Package failed to install correctly.
Failed to install package [Package]. Installation of [Package] failed (failed to load package details). This package is being put into Holding status
The Agent failed to load the required Package Distribution Definition, or there is an error in the Package Definition.
Error loading context for package [Package]. This package is being put into Holding status
This error may occur if there is an inconsistency between the settings in the Package Definition and the additional distribution Job information.
Failed to install package [Package]. Agent Shutdown requested during package installation.
This error may occur if a Client PC reboot or shutdown was attempted during the Package installation.
Failed to install package [Package]. User launch setup error. Check account username and password.
This installation error will be generated if an incorrect username and password is being used. Try logging on as different user.
Failed to install package [Package]. Application launch failed (status = [Status])
Check the Kit Path, command line and target executables.
Failed to install package [Package]. Unable to connect to Pre-process path, Access denied.
Check the Package Definition's Pre-process settings.
Failed to install package [Package]. Unable to connect to Post-process path, Access denied.
Check the Package Definition's Post-process settings.
Error Messages on Client PCs
Unless you are performing a Totally Silent installation, error messages may be displayed on the Client PC. These error messages all begin with Installation of [Package] failed. The subsequent text will be one of the following messages:
Insufficient disk space to proceed with installation. This package is being put into Holding status
The Client PC failed the free disk space check specified in the Package's Distribution Definition.
Insufficient privilege to proceed with installation. This package is being put into Holding status
The Agent is not running with the Admin-level privileges required. The Software Distribution Agent can run as a Windows service, to give it access to the privileged environment that is required to install Service Packs and many other applications.
No user account specified for this installation. The Agent Service always requires an account.
No User Account was specified in the Software Distribution Wizard when the Job was queued.
Pre-Process command failure prevents installation from continuing. This package is being put into Holding status
The Pre-Process command specified in the Package's Distribution Definition failed to execute.
Unable to connect to kit source [Kit path]. This package is being put into Holding status
The location of the installation kit cannot be accessed. The location is specified in the Package's Distribution Definition, although the kit path can be changed using the Software Distribution Wizard.
Launch error. This package is being put into Holding status
An error occurred was found in the Installation command line. Check the Kit location, the Installation command, and the user information are correct.
Error triggering system reboot to complete package installation. This package is being put into Holding status
The Agent could not reboot the Client PC.
Failed to load package details. This package is being put into Holding status
The Agent failed to load the required Package Distribution Definition, or there is an error in the Package Definition.
Agent Shutdown requested during package installation.
A Client PC reboot or shutdown was attempted during the Package installation.
File not found.
A file required by the Package installation was missing. Check the install path and Kit location.
Installation of [Package] requires a system reboot. We recommend that you close all applications and select "Yes" to reboot now. If this is not possible, select "No" and reboot as soon as you can. Reboot Now?
The Client PC must be rebooted to complete the installation. Users can choose to reboot immediately or later.
User launch setup error. Check account username and password.
An incorrect username and password is being used. Log on as different user.
Application launch failed (status = [Status])
Check the Kit Path, command line and target executables.
Unable to connect to Pre-process path, Access denied.
Check the Package Definition's Pre-process settings.
Unable to connect to Post-process path, Access denied.
![]() Vector Networks http://www.vector-networks.com Voice: +44 (0) 1827 67333 Fax: +44 (0) 1827 67068 info@vector-networks.co.uk |
![]() |
![]() |
![]() |
![]() |