Unable to Add ESX Server to up.time 5.x

There are several possible reasons why you may be experiencing this issue.  To help identify the root cause, take the following steps:

• Try using Root credentials to add the ESX host by its hostname or IP address.
• Port 443 (SSL) needs to be open for communication between up.time and the ESX server you are trying to add.  To check this connectivity, open a command line prompt and run a telnet command using port 443 from the up.time monitoring station to the ESX host.  If the connection fails, this will need to be resolved before the host can be added.
• Ensure that Lockdown Mode is not enabled.
• Ensure that the Hostd service is running on the ESX host.
• Verify that the ESX host is not being managed by multiple, stale or non-existent vCenter / vSphere hosts and that all of the hosts are online.  Remove any offline host(s) from the ESX host management console.
• All ESX versions have a Managed Object Browser (MOB) that provides ESX server details and can be used to test user credentials.  Browse to https:///mob/ from up.time and log in using the appropriate credentials.  If you are able to navigate through the MOB, use the same credentials to log into up.time using the auto-discovery option under the My Infrastructure tab.
• If the system is an ESXi server, confirm that it is managed by vSphere/vCenter.

If you are still unable to add the ESX server to up.time after following the above steps, please contact [email protected] and provide the following information:

• Screen capture of the error message.
• ESX version and build number.
• up.time and monitoring station Operating System version.
• Send the uptime.log file from the uptime_install dir\Logs folder after completing the following steps:
• Change the logging level from INFO to DEBUG in the uptime.conf file, which is located in the up.time installation directory.
• Try adding the ESX server to up.time so the exception is captured in the uptime log.