Cisco CUCM TSP on Windows 8 and Server 2012

In preparing our e911/e999 software, some testing revealed an issue installing the Cisco TSP on Windows 8 and Windows Server 2012.  The TSP comes with CUCM 8.x and runs fine on Windows 7 and Windows Server 2008.  During the installation of the TSP, the following error is thrown before installation completes: “Could not load the dll file EncryptPassword.dll”

This renders the TSP useless and unable to communicate with the CUCM servers.  The remedy the situation and get the TSP installed, run the installer again, selecting the “reinstall” option.  When installation completes, proceed to the Control Panel, Phone and Modem Options.  Select the “Advanced” tab and click “Add” to add the Cisco TSP that was just installed.  Next, with the Cisco TSP selected, click “Configure” and re-supply all the connection information.  Due to the initial error, none of the configuration information was saved during the first go-round of the TSP installation.

After the configuration information has been supplied, reboot your computer for the changes to take effect.

Watch the short video for a quick walk-thru of this procedure.  I hope this helps others who encounter the same situation.

Cheers,

-Beau



2 comments

  1. Great post and very appreciated. Sidebar is that depending on how rights are assigned in GP, an admin may or may not be able to see the required settings in Control Panel. This can be resolved by Start > Run > control telephon.cpl.

  2. Came across this issue when installing Cisco Unified Attendant Console Standard 12 on Windows 10. It ended up being caused by the computer having issues installing Microsoft Visual C++ 2005 redistributable that is packaged with the TSP installer.

    Initially the computer froze when installing this due to it installing other updates in the background (Win10, huh?) and when we attempted another install it didn’t try to reinstall C++.

    Uninstalling C++ 2005 and then uninstalling and reinstalling CUACS (and TSP) fixed this issue.

Leave a Reply to Mark VandeVere Cancel reply

Your email address will not be published. Required fields are marked *