*ERROR* Failed m_WaveList- Init(). hr=0x80040154 with Cisco TSP

Question

Cisco TSP 8.6(2.2).
I am trying to install Cisco TSP on a Windows 7 32bit workstation, but I am having issues.  We are using a management program called "Connectwise".  My boss wants to be able to dial a customer within the "Connectwise" program to log calls.  Our other office has a Shortel phone system and Shortel's TSP program works fine.  I've installed Cisco TSP, configured CTI ports, configured a CTI routepoint, enabled the user for CTI, and associated the user with the CTI ports/route point.  When I try to dial a number within Connectwise, nothing happens.  Within the Cisco TSP logs these errors are logged:
16:23:36.418 HDR|05/07/2012 CiscoTSP001.tsp,Error
16:23:36.418 |   CSelsiusTSPWaveList::Init() *ERROR* Failed to get ISelsiusNTWaveCtl interface.
16:23:36.419 |   SelsiusTSP::InitializeComObjects() *ERROR* Failed m_WaveList->Init(). hr=0x80040154
17:02:12.513 |   CSelsiusTSPLink::getMessage() *ERROR* Receive() failed with error 0.
I have tried to use the Windows "Dialer" program to test as well, but receive this error:
One or more telephone device drivers are incompatible with TAPI.DLL.  Install an updated version.
I have installed Cisco TSP with both the WAVE driver and the new MEDIA driver.  I receive the same error with either driver.  I've also tried this on multiple workstations, but get the same error.
Help

Answer 1

I engaged TAC and the engineer pinpointed following error from the CTI Logs:
Login User Id:platju Reason code.:-1932787595
This is the Cisco documentation on this error code:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/jtapi_dev/8_6_1/constantfieldvalues.html
The engineer suspected LDAP server is not able to authenticate CTI based connections correctly although HTTP based connections (CCMUSER Web Page access) or JTAPI based connections (UCCX) are working fine.
We created an application user in CUCM and the Dialer.exe showed Cisco Line as expected. The engineer did assign all CTI roles (Not only Standard CTI Enabled) except Secure CTI ones. The End User didn't work no matter what we try.
As of now, I've asked the AD team to look at their side or engage Microsoft to debug it at their end. Hopefull that'll resolve the issue.