Troubleshooting Agent installation
This section explains how to react when the Agent installation failed.
Output message and action
| Message | Error content | Supposed cause | Action |
|---|---|---|---|
| The 'huliotsetup' is not recognized as an internal command, an external command, a program that can be operated, or a batch file. | In the Windows environment, the 'huliotsetup' cannot start. | The selected Agent module does not match the Windows environment on which you are attempting to install Agent. |
Confirm the OS and the hardware information of the installation destination, and then select the appropriate Agent module. For details about the naming rules of the Agent module, see (6) Naming rules for Agent modules in Contents of installation modules. |
| huliotsetup: cannot execute binary file | In the Linux environment, the 'huliotsetup' cannot start. | The selected Agent module does not match the Linux environment on which you are attempting to install Agent. | |
|
Failed to create the installation directory. Restore to the pre-installation state, because an error occurred. Failed to new installation. |
Creation of the installation folder failed. | The user does not have an access privilege to the installation folder. | Confirm the privilege settings of the user who installs Agent, and then perform the installation by a user who has administrative privileges. |
|
Failed to copy the module. Restore to the pre-installation state, because an error occurred. Failed to new installation. |
Copying the Agent module failed. | Free space on the installation destination is not enough. | Acquire enough free disk space. |
|
already installed. Restore to the pre-installation state, because an error occurred. Failed to new installation. |
Agent has been installed. | Agent already has been installed. |
If you newly install Agent, uninstall the existing Agent in advance. See also Uninstallation from an agent environment. |
| File path is too long. Max pathsize is 200. FILENAME=??? Failed to new installation. | The installation directory path that is specified in the command parameter is too long. | The path is over 200 bytes in length. | Specify the directory whose path length is within 200 bytes. |
| Invalid HOST or PORT was specified. HOST:PORT=??? Failed to new installation. |
• The host name or the port number of Manager is incorrect. • The host name or the port number of the proxy is incorrect. |
• The host name is not specified. • The host name is too long. • The port number is out of range. • The port number includes one or more wrong characters. |
Specify the host name and the port number correctly. |
| Invalid ID or PASSWORD was specified. ID:PASSWORD=??? Failed to new installation. | The user name or the password for the proxy is incorrect. |
• The user name or password is not specified. • The user name is too long. • The password is too long. |
Confirm the settings of the proxy, and then specify the user name and the password correctly. |
| Invalid key was specified. KEY=??? Failed to new installation. | The activation key is incorrect. | The activation key is incorrect in length. |
Acquire the activation key from Manager, and then specify it correctly. See also Acquiring the activation key. |
| Devicename is too long. Max size is 68. DEVICENAME=??? Failed to new installation. | The device name is too long. | The device name is over 68 bytes in length. | Specify the name within 68 bytes in length. |
| Service name is too long. Max size is 256. SERVICENAME=??? Failed to new installation. | The service name is too long. | The service name is over 256 bytes in length. | Specify the name within 256 bytes in length. |
| Invalid interval was specified. INTERVAL=??? Failed to new installation. | When Agent fails to connect Manager for the first time, the value of the retry interval is incorrect. |
• The specified value is other than numerals. • The specified value is out of range. |
Specify the value from 1 to 5097600. |
| Invalid WORK_FILE_PATH was specified. WORK_FILE_PATH=??? Failed to new installation. |
The path of the output directory for the system files that Agent internally uses is too long. |
The path is over 216 bytes in length. | Specify the directory whose path is within 216 bytes in length. |
| Invalid REMARKS_FILE was specified. REMARKS_FILE=??? Failed to new installation. | The path for the remarks file is incorrect. | The path is over 256 bytes in length. | Specify the directory whose path is within 256 bytes in length. |
| Invalid LOG_FILE_PATH was specified. LOG_FILE_PATH=??? Failed to new installation. | The path of the temporary storage directory for the log files that Agent will send to Manager is too long. | The path is over 226 bytes in length. | Specify the directory whose path is within 226 bytes in length. |
| huliotsetup.ini is invalid. (invalid value. tag=install_path) Failed to new installation. | The path for the installation directory is too long, which is specified in the huliotsetup.ini file. | The path is over 200 bytes in length. | Specify the directory whose path is within 200 bytes in length. |
| huliotsetup.ini is invalid. (???) | The description of the huliotsetup.ini file is invalid. | The description of the huliotsetup.ini file is invalid. | Correct the huliotsetup.ini file. |
| The others | Other than above | Other than above | Contact our support department with a copy of the screen when the installation failed. |