Product Documentation

Installation Manager Messages Reference

Oct 09, 2015
Installation Manager may report the following messages.

Generally, a positive value indicates a successful condition or provides general information. A negative value usually indicates an error condition.

The numbers in the following tables are organized by the absolute value of the initial digit, then by remaining digits.

Administration Messages

Number String Trigger or Condition
0 SUCCESS The task ran successfully.
1 SCHEDULED The task is scheduled in the Task Scheduler.
-1 FAILURE The task failed to register or execute.
-100 A connection to the server could not be established. The server may not be physically connected.
-101 Invalid farm argument. Specify a valid server address. The specified farm name may either be syntactically wrong or may not exist.
103 This Citrix XenApp PowerShell snap-in contains cmdlets used to perform remote management operations in your XenApp environments.  
-104 Invalid arguments. Specify either "match" or "like" arguments, not both. Specify either Match or Like for filtering servers.
-105 XenApp SDK is not installed or Check DCOM Settings DCOM settings in the client computer are either missing or incorrect.
-106 The folder specified {0} does not exist. Specify a valid folder name in the format Servers/folder1/folder2.  
-107 Access denied while enumerating Servers/Folders in farm. The administrator is not a Citrix Administrator.
2 EXECUTING The task is running.
-205 Server is unreachable. Check network connections. The task cannot register itself with the Task Scheduler.
-207 You do not have permission to access the target server. You must be a local Administrator on that server. The application cannot register a task because the logon credentials are not valid.
-211 Invalid Task XML format. Document contains invalid tags. The task XML document does not comply with the Task Scheduler 2.0 standard schema.
-212 Unable to write Log file {0}. check that the path exists and that you have write permissions to it. The application cannot create the log file because it does not have write permission for the specified path.
-214 Unable to read Task file {0} check that the file exists and that you have read permissions to it. The task file is not at the specified location or cannot be accessed due to incorrect permissions.
-216 Specify the interval time in seconds for the Retry parameter. A negative value was specified for the retry interval time.
-219 This task name already exists on the target server. Enter a unique task name. The specified task name already exists.
-220 Network path {0} is unreachable. Check network connections. The servers are physically disconnected.
-221 Invalid Task XML format. Cannot find "action" tag. The task XML file does not contain the mandatory <actions> tag.
-222 You do not have permission to schedule a task. You must be a local Administrator on the target server. Insufficient permissions exist to access the target task scheduler.
-223 Invalid Task XML format. The "command" tag contains invalid data. The task XML file does not contain the mandatory <command> tag.
-224 Invalid Task XML format. The "command" tag is not well-formed. The task XML <command> tag formation is not valid.
-226 The filename, directory name, or volume label syntax is incorrect for path {0} The specified task name is in an invalid format.
-229 Invalid Task XML format. The Task Scheduler cannot recognize the XML format.
230 Task successfully registered. The task registered successfully in the Task Scheduler.
-233 Invalid task name. The specified task name does not start with an alphabetical character.
-234 Invalid target argument. Specify a valid server address. The specified server IP address is not valid.
239 Task successfully updated. The existing task in the Task Scheduler updated successfully.
-241 Missing retrytime argument. It is mandatory if retryinterval is provided. A retry interval value was specified without a retry time value.
-242 Missing retryinterval argument. It is mandatory if retrytime is provided. A retry time value was specified without a retry interval value.
3 SCHEDULE_PENDING The task is not yet registered in the Task Scheduler.
-300 Use the following date and 24-hour time format: DD/MM/YYYY HH:MM:SS. The time and date specified for the schedule option are not in the required format.
-301 Unable to prepare UNC path {0}. Check your credentials. Access was denied to the PrepareUNC path due to insufficient permission.
-302 Invalid command argument. Specify a valid command-line operation. A cmdlet option was incorrectly specified.
-303 Failed to assign read permissions of computer {0} to the path {1}. Ensure the path and computer name are correct, and that you have sufficient access rights to the path.  
4 CANCELLED The running task was stopped.
-400 Specify a reboot timeout period in minutes for the Reboot-Timeout parameter. The timeout value specified is not an integer.
-404 Unable to read MSI file {0}. Check that the file exists and that you have read permissions to it. Access was denied to the MSI file due to insufficient permission.
-405 Unable to read MST file {0}. Check that the file exists and that you have read permissions to it. Access was denied to the transform (MST) file due to insufficient permission.
5 CANCEL_PENDING The task running is being stopped.
501 Task successfully removed. The task was successfully removed from the Task Scheduler.
6 REMOVED The task was removed from the Task Scheduler.
-600 Unable to connect to Event Log of the target server. You must be a member of "Event Log Readers" group in the target server.  
-601 Task not found. The task is not found in the target server's Task Scheduler.
605 Task was scheduled. The task is scheduled to run on the target server.
606 Task is running... The task is running on the target server.
607 Scheduling... The task is not yet registered.
608 Task was cancelled. The running task has been stopped.
609 Canceling task... The task running is being stopped.
-610 Task failed. The task failed to execute.
-611 Task Failed. Verify if IM Utilities is installed at target server. The Utilities package is not installed on the target server.
-801 COM error while scheduling task in target system : {0} A COM exception occurred while schedule a task in the Task Scheduler on the target server.
-802 Generic error while scheduling task in target system :{0} An exception occurred while scheduling a task in the Task Scheduler on the target server.
-803 COM error while retrieving task information from target system :{0} A COM exception occurred while retrieving task information from the Task Schedule on the target server.
-804 COM error while removing task form target system :{0} A COM exception occurred while removing a task form the Task Scheduler on the target server.
-805 Generic error while removing task from target system :{0} An exception occurred while removing a task from the Task Scheduler on the target server.
-901 MFCOM is not registered on the system. Use the MFREG tool to register the server.  

Utilities Messages

The following messages may be generated if you installed the Utilities package on the target servers, which is required if you are scheduling MSI or MSP packages for installation on the target servers.
Number String Trigger or Condition
-105 XenApp SDK is not installed or Check DCOM Settings DCOM settings in the client computer are either missing or incorrect.
-226 The filename, directory name, or volume label syntax is incorrect for path {0}  
-700 Installation failed: {0} MSIEXEC failed to run.
-701 Unable to read Installation files using system credentials. Ensure "Everyone" has read permission to the share and "Advanced:Shared Folder" parameter contains the UNC path where the file is located. Unable to access MSI log file.
-702 Unable to connect to the XenApp farm. Specify only XenApp servers when using publish-app or disable-logon parameters. XenApp farm initialization failed.
-703 Unable to add server to published application. The installation was successful, use Delivery Services Console to add the server to the published application object. The server may not exist.
705 Published Application name is already existed.  
-709 Terminal Server role is not enabled. Reboot and logoff parameters are only available for Terminal Server targets. Target server does not have Terminal Services enabled.
-710 Unable to send message to connected sessions. Operation was canceled. Error sending Terminal Services messages.
-711 Unable to reboot server. The installation was successful otherwise, reboot the server manually to complete the operation. Error restarting Terminal Services target.
712 This Citrix XenApp PowerShell snap-in contains cmdlets used to perform installations on XenApp servers.  
-715 Incorrect number of parameters to MSIScriptlet.ps1 Not all parameters were passed to scriplet file.
-716 Missing MSI file path argument. The MSI file option is required.
718 Success. The MSI installed successfully.
-720 Missing task name argument. The task name option is required.
723 Success. System will reboot. The task ran successfully and the server will restart to complete the installation.
-724 Unable to write event to Windows Event Log. An error occurred when writing to Event Logger.