10-19-2007 09:42 AM - edited 03-15-2019 12:04 AM
Hello!
We are running Callmanager 4.1(3)sr3c. We are also running Informacast Berbee and we have everything integrated in Active directory as well as Unity 4.0(5)
The application event log shows:
Error: kCtiProviderOpenFailure - CTI application failed to open provider
CTIconnectionId: 21647
Login User Id: CCMSysUser
Reason code.: -1932787617
IPAddress:
App ID: Cisco CTIManager
Cluster ID: StandAloneCluster
Node ID: 192.168.210.10
Explanation: Application is unable to open provider.
Recommended Action: Check the reason code and correct the problem. Restart CTIManager if problem persists..
About every 3 seconds.
I can not find anything about the reason code not in Decimal nor in Hex.
Anybody having and idea.
Berbee actually hung up a couple of times which could be corrected the first time by rebooting the Berbee server, the second time we had to reboot CallManager.
Restarting the CTI service didn't solve the problem.
10-19-2007 01:27 PM
The problem is that the CCMSysUser is not getting authenticated. You need to reset the password using the adminutility, just keep in mind that this will stop the CCM services so you need to do this during a maintainance window or afterhours.
HTH
//Jorge
10-22-2007 11:42 AM
Copy & paste the reason code in a scientific calculator:
-1932787617
then transform the number to Hexadecimal you will get FFFFFFFF8CCC005F, just take the second part: 8CCC005F and take a look to the attached document, and you can see this:
const unsigned long int CTIERR_DIRECTORY_LOGIN_NOT_ALLOWED= 0x8CCC005F
So again the problem is that the CCMSysUser is not authenticating.
//J
12-07-2007 06:49 AM
Haack,
1) Delete users (CCMSysUser / CCMAdministrator / IPMASysUser) with (OU=CISCO) in AD.
2) Creating the Schema Update Allowed Registry for AD 2003:
2a) Make sure that the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters\Schema Update
Allowed is set on the Microsoft Active Directory server to 1. This allows write access to the schema on that server.
3) run plugin (Cisco Unified CallManager Customer Directory Plugin) no CCM > Application > Install Plugins.
4) Integration password:
4a) Publisher database server, choose Start > Run and enter cmd
4b) Enter the command, CCMPWDChanger.
4c) In the Administrator Password field, enter the password of the user that was created to enable
Cisco CallManager to access the directory and next.
4d) The Cisco CallManager Password Changer window displays. The User ID drop-down list box provides
the following options: Directory Manager, CCMAdministrator, CCMSysUser, and IPMASysUser.
4e) You must change the passwords for the CCMAdministrator, CCMSysUser, and IPMASysUser accounts.
4f) In the New Password field, enter the new password.
4g) In the Confirm New Password field, enter the password again.
5) open htts://CCM/manager/list and stop the services.
6) open https://CCM/CCMService/main.asp go tools > Control Center > Servers > Stop the services (Cisco CTIManager/Cisco TFTP/Cisco Extension Mobility).
7) Boot the Server.
Good Luck!
Rafael Cardoso.
03-06-2008 04:54 AM
hi,
i also encountered the same error.
but now its not accepting the password of dcdadmin.
do i have to run this admin utility again.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide