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.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...