subscriber login failed

howct7231 · ‎02-23-2008

Hi,

Have encountered after patch 5.1.2b, the subscriber Call Manager unable to login and have "login failed" prompted if publisher server is down. The subscriber only able to login successfully when the publisher server is running.

Any solutions or suggestion for that ?

Thanks

hadbou · ‎02-28-2008

In order to resolve this issue, complete these steps:

Run Adminutility in order to check the password synchronization for SQLSvc, CCMServiceRW, CCMService, CCMCDR and CCMUser in the Cisco CallManager cluster.

Refer to Check Password Synchronization with the Admin Utility in the Cisco CallManager Cluster for more information about Adminutility.

Run the CCMPwdchanger tool to synchronize passwords.

Refer to Change Passwords in Cisco CallManager and Cisco Unity Configuration Example for more information.

Check the Database status through DBL Helper.

Refer to Using DBLHelper to Reestablish a Broken Cisco CallManager Cluster SQL Subscription for more information.

Restart IIS & WWW services.

Check registry settings as indicated in Cisco bug ID CSCeg00750, and make sure they are same on both Publisher & Subscriber.

This issue also occurs when SQLSvc password is not sync with MLA and system. In order to correct this, look for synchpwd.dll in the c:\winnt\system32\synchpwd.dll . If this DLL is there, then the publisher uses this file instead of the c:\program files\cisco\bin\synchpwd.dll. Hence, the password in the publisher is never in sync with the Subscriber.

12/01/2006 00:31:51.924 | Authfilt::enablePowerUser() LogonUser(SQLSvc,*****)

12/01/2006 00:31:52.127 | Authfilt::enablePowerUser() *ERROR* LogonUser() failed, enum=1326

Remove this file from c:\winnt\system32\synchpwd.dll and then copy the synchpwd.dll file from the Subscriber to Publisher. This is the file that it uses to sychronize the password with the Subscriber. Reset the password again or otherwise the same error shows up again.

You can check the synchpwd.log in the MLA trace folder in order to see if the new phrase password is set.

howct7231 · ‎02-28-2008

Hi Hadbou,

This will be good help if the CCM is used in Windows OS.

I have experiencing the problem lies on the CCM which used in Linux OS platform.

john.l.georgiou · ‎03-03-2008

Hi,

if your talking about users logging in via extension mobility then the patch that you have applied has nothing to do with your problem.

Extension Mobility relies on the Publisher database being online and working. If the publisher database is unavailable then auxillary servers are unable to change database values on the publisher.

Just remember that a login change of state with extension mobility requires a write operation on the publisher. If the publisher is unavailable then no database alterations can take place. That is because the publisher server is the only server in a cluster that stores a read/ write copy of the database. All other servers have a read only copy that is synced to the publisher's database. This applies to CCM 4,5 and 6.

Thanks