I have seen this issue occurring due to some group policies, if the server is part of a domain try to unjoin it from the domain and do the installation again. This happens because the opends service does not start for some reason and it makes the "Installing LDAP" part of the TMS installation take quite some time before it gives you this error.
The opends will be corrupted (since the server is not started and the installer is unable to launch the configuration script) but the TMS installation will be fine. It is fixable post installation as well, TAC can help you with this. BUT If you are planning to setup provisioning I would set up the provisioning extension instead of using the legacy TMSAgent (assuming you are installing TMS 13.2.x). If you are not planning to setup provisioning at all (Jabber / Movi) there is nothing to worry about this this error unless you want to / need to set up provisioning using the old provisioning model.
It's an issue we have seen around and the reasons are sometimes different. It also might be that the next installation attempt will be successful.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...