|
Home > Archive > Voice over IP Cisco > February 2007 > Ideas for troubleshooting CCMSysUser
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Ideas for troubleshooting CCMSysUser
|
|
| Jason Aarons \(US\) 2007-02-06, 7:12 pm |
| In ADSIEdit should CCMSysUser have attributes for ciscoatUserProfile,
ciscoatuserProfileString, and ciscoatGUID? I had a few regular users in
Global Directory whom I could not associate a Device (Phone) to them
until I removed any attribute for ciscoatX via ADSIEdit on the Domain
Controller.
Here is what I have done so far, CallManager 4.1(3)SR4d, Active
Directory integrated, ran CCMPwdChanger after AD integration, rebooted
everything multiple times, can login to Windows Workstations using
CCMSysUser, reverse decrypted the registry value for Password, ran
sniffer traces they shows LDAP success for CCMSysUser, Domain Controller
Security Log shows plenty of Successful Logins (event 548,547) for
CCMSysUser.
I am unable to login to https://server/ccmuser with CCMSysUser is my
only clue. Previous forum posts from Ryan/Wes indicate this should work,
but doesn't the CCMSysUser have CiscoPrivateUser making ccmuser not able
to login right?
Event Type: Error
Event Source: cisco CTIManager
Event Category: None
Event ID: 3
Date:2/6/2007
Time: 3:27:34 PM
User: N/A
Computer: NEMCCM01
Description:
Error: kCtiProviderOpenFailure -CTI application failed to open provider
CTIconnectionId: 15502
Login User Id: CCMSysUser
Reason code.: -1932787616
IPAddress:
App ID: cisco CTIManager
Cluster ID: StandAloneCluster
Node ID: 10.20.28.10
Explanation: Application is unable to open provider.
Recommended Action: Check the reason code and correct the problem.
Restart CTIManager if problem persists..
-----------------------------------------
Disclaimer:
This e-mail communication and any attachments maycontain
confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful. If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
| |
| Jason Aarons \(US\) 2007-02-06, 7:12 pm |
| Once I removed CiscoPrivateUser I could login with CCMSysUser on
CCMUser.
Via ADSIEdit none of my values are populated for ciscoatUserProfile,
ciscoatuserProfileString, and ciscoatGUID, should they be?
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Jason Aarons
(US)
Sent: Tuesday, February 06, 2007 3:32 PM
To:cisco-voip@puck.nether.net
Subject: [cisco-voip] Ideas for troubleshooting CCMSysUser
In ADSIEdit should CCMSysUser have attributes for ciscoatUserProfile,
ciscoatuserProfileString, and ciscoatGUID? I had a few regular users in
Global Directory whom I could not associate a Device (Phone) to them
until I removed any attributefor ciscoatX via ADSIEdit on the Domain
Controller.
Here is what I have done so far, CallManager 4.1(3)SR4d, Active
Directory integrated, ran CCMPwdChanger after AD integration, rebooted
everything multiple times, can login to Windows Workstations using
CCMSysUser, reverse decrypted the registry value for Password, ran
sniffer traces they shows LDAP success for CCMSysUser, Domain Controller
Security Log shows plenty of Successful Logins (event 548,547) for
CCMSysUser.
I am unable to login to https://server/ccmuser with CCMSysUser is my
only clue. Previous forum posts from Ryan/Wes indicate this should work,
but doesn't the CCMSysUser have CiscoPrivateUser making ccmuser not able
to login right?
Event Type: Error
Event Source:Cisco CTIManager
Event Category: None
Event ID: 3
Date: 2/6/2007
Time: 3:27:34 PM
User: N/A
Computer: NEMCCM01
Description:
Error: kCtiProviderOpenFailure - CTI application failed to open provider
CTIconnectionId: 15502
Login User Id: CCMSysUser
Reason code.: -1932787616
IPAddress:
App ID: cisco CTIManager
Cluster ID: StandAloneCluster
Node ID: 10.20.28.10
Explanation: Application is unable to open provider.
Recommended Action: Check the reason code and correct the problem.
Restart CTIManager if problem persists..
________________________________
Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee,
you are hereby notified that you have received this communication in
error and that any use or reproduction of this email or its contents is
strictly prohibited and may be unlawful.If you have received this
communication in error, please notify us immediately by replying to this
message and deleting it from your computer. Thank you.
-----------------------------------------
Disclaimer:
This e-mail communication and any attachments may contain
confidential and privileged information and isfor use by the
designated addressee(s) named above only. If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful. If you have received this communication in error, please
notify us immediatelyby replying to this message and deleting it
from your computer. Thank you.
| |
| Ryan Ratliff 2007-02-06, 7:12 pm |
| The error code in the event id you pasted below translates to =
8CCC0060 which corresponds to CTIERR_DIRECTORY_LOGIN_FAILED.
Is your ldap bind as CCMSysUser successful? Also check c:\dcdsrvr =
\directoryconfiguration.ini to verify the password there matches what =
you have in the registry (as well as other ldap info).
You are correct that you should not be able to login with CCMSysUser =
via CCMUser page.
I don't have an AD-integrated CM handy but I do see a CCMSysUser- =
profile and CCMSysUser-CCNProfile object in DCD so I suspect you =
should have those attributes set. In the sniffer capture you should =
see us grabbing the cisco attributes from the CCMSysUser account. If =
we do that then they are required.
You should be able to re-run the AD plugin to get them set.
-Ryan
On Feb 6, 2007, at 3:46 PM, Jason Aarons ((US)) wrote:
Once I removed CiscoPrivateUser I could login with CCMSysUser on =
CCMUser.
Via ADSIEdit none of my values are populated for ciscoatUserProfile, =
ciscoatuserProfileString, and ciscoatGUID, should they be?
From: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip- =
bounces@puck.nether.net] On Behalf Of Jason Aarons (US)
Sent: Tuesday, February 06, 2007 3:32 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Ideas for troubleshooting CCMSysUser
In ADSIEdit should CCMSysUser have attributes for ciscoatUserProfile, =
ciscoatuserProfileString, and ciscoatGUID? I had a few regular users =
in Global Directory whom I could not associate a Device (Phone) to =
them until I removed any attribute for ciscoatX via ADSIEdit on the =
Domain Controller.
Here is what I have done so far, CallManager 4.1(3)SR4d, Active =
Directory integrated, ran CCMPwdChanger after AD integration, =
rebooted everything multiple times, can login to Windows Workstations =
using CCMSysUser, reverse decrypted the registry value for Password, =
ran sniffer traces they shows LDAP success for CCMSysUser, Domain =
Controller Security Log shows plenty of Successful Logins (event =
548,547) for CCMSysUser.
I am unable to login to https://server/ccmuser with CCMSysUser is my =
only clue. Previous forum posts from Ryan/Wes indicate this should =
work, but doesn=92t the CCMSysUser have CiscoPrivateUser making ccmuser =
not able to login right?
Event Type: Error
Event Source: cisco CTIManager
Event Category: None
Event ID: 3
Date: 2/6/2007
Time: 3:27:34 PM
User: N/A
Computer: NEMCCM01
Description:
Error: kCtiProviderOpenFailure - CTI application failed to open provider
CTIconnectionId: 15502
Login User Id: CCMSysUser
Reason code.: -1932787616
IPAddress:
App ID: cisco CTIManager
Cluster ID: StandAloneCluster
Node ID: 10.20.28.10
Explanation: Application is unable to open provider.
Recommended Action: Check the reason code and correct the problem. =
Restart CTIManager if problem persists..
Disclaimer: This e-mail communication and any attachments may contain =
confidential and privileged information and is for use by the =
designated addressee(s) named above only. If you are not the intended =
addressee, you are hereby notified that you have received this =
communication in error and that any use or reproduction of this email =
or its contents is strictly prohibited and may be unlawful. If you =
have received this communication in error, please notify us =
immediately by replying to this message and deleting it from your =
computer. Thank you.
Disclaimer: This e-mail communication and any attachments may contain =
confidential and privileged information and is for use by the =
designated addressee(s) named above only. If you are not the intended =
addressee, you are hereby notified that you have received this =
communication in error and that any use or reproduction of this email =
or its contents is strictly prohibited and may be unlawful. If you =
have received this communication in error, please notify us =
immediately by replying to this message and deleting it from your =
computer. Thank you.
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|
|
|
|
|