Agent deployment is not completed before the TIMEOUT expires

When running agent deployment, TIMEOUT might occur because of slow network connections or slow hardware. The agent deployment can be completed if you increase the TIMEOUT value.

About this task

Table 1. Resolutions for agent deployment that TIMEOUT
Problem	Resolution
KDY0014E message	Increase the Tivoli® Enterprise Monitoring Server timeout value to 3600 seconds (TIMEOUT=3600). The default is 600 seconds. On Windows® systems:`installation_dir\CMS\KBBENV`. On UNIX-based systems: `installation_dir\host_name_ms_Tivoli Enterprise Monitoring Server_ID.config`. If the problem persists after modifying the timeout value, cancel the agent deployment and deploy the agent again.
KDY1009E KDY1017E KDY1018E KDY1022E KDY1025E KDY1030E KDY1033E	Increase the OS agent timeout value to 600 seconds (TIMEOUT=600). The default is 300 seconds. On Windows systems: `installation_dir\TMAITM6\KNTENV`. On UNIX-based systems: `installation_dir\ux.ini`. On Linux® systems, set it in `installation_dir\lz.ini`. The value must be set in seconds.
A system error occurs when running a tacmd command.	Increase value for the TACMD_TIMEOUT environment variable to 30 minutes. (TIMEOUT=30). The default is five minutes. On Windows systems: Enter the following command: `set TACMD_TIMEOUT=30` On UNIX-based systems: Enter the following command: `export TACMD_TIMEOUT=30`
A failure occurs when deploying an agent from the Tivoli Enterprise Portal.	The Tivoli Enterprise Portal Server times out waiting for deployment action to complete. The default timeout is 600 seconds. You can change the timeout setting to KFW_SQL1_ASYNC_NOTIFY_MAX_WAIT in kfwenv: `KFW_SQL1_ASYNC_NOTIFY_MAX_WAIT=1000`
KUICCN068E error when running tacmd createnode.	Increase the timeout value in seconds by adding "`-o TIMEOUT=3600`" to the createnode command.