Re: CUCM 11.5 LDAP Sync failed

Slavi · ‎11-12-2017

Hey Guys,

I have a LDAP sync problem at our customer and i can´t find the Problem.

Can you please tell me what the logs mean?

Thanks a lot!

I´ve added the Errorlog output:

2017-11-10 03:15:00,009 ERROR [DSLDAPMain] dirsync.DSLDAPMain (DSLDAPMain.java:124) - DSLDAPMain[handleIncomingReq] Sync agreement 54c43f99-a561-4f3a-868d-26a5547445d9 is not available in database....exit
2017-11-11 00:00:00,026 ERROR [DSLDAPMain] dirsync.DSLDAPMain (DSLDAPMain.java:320) - DSLDAPMain[handleIncomingReq] Directory type is null
2017-11-11 00:00:00,027 ERROR [DSLDAPMain] dirsync.DSLDAPMain (DSLDAPMain.java:331) - DSLDAPMain[handleIncomingReq] Parameter validation failed on sync agreement-dd5ec04b-4890-c76c-fc4c-285b76212582
2017-11-11 03:15:00,009 ERROR [DSLDAPMain] dirsync.DSLDAPMain (DSLDAPMain.java:124) - DSLDAPMain[handleIncomingReq] Sync agreement 54c43f99-a561-4f3a-868d-26a5547445d9 is not available in database....exit
2017-11-12 03:15:00,021 ERROR [DSLDAPMain] dirsync.DSLDAPMain (DSLDAPMain.java:124) - DSLDAPMain[handleIncomingReq] Sync agreement 54c43f99-a561-4f3a-868d-26a5547445d9 is not available in database....exit
2017-11-13 03:15:00,008 ERROR [DSLDAPMain] dirsync.DSLDAPMain (DSLDAPMain.java:124) - DSLDAPMain[handleIncomingReq] Sync agreement 54c43f99-a561-4f3a-868d-26a5547445d9 is not available in database....exit
2017-11-13 08:14:25,808 ERROR [DSLDAPMain] dirsync.DSLDAPMain (DSLDAPMain.java:320) - DSLDAPMain[handleIncomingReq] Directory type is null
2017-11-13 08:14:25,808 ERROR [DSLDAPMain] dirsync.DSLDAPMain (DSLDAPMain.java:331) - DSLDAPMain[handleIncomingReq] Parameter validation failed on sync agreement-dd5ec04b-4890-c76c-fc4c-285b76212582
2017-11-13 08:15:22,699 ERROR [DSLDAPMain] dirsync.DSLDAPMain (DSLDAPMain.java:320) - DSLDAPMain[handleIncomingReq] Directory type is null
2017-11-13 08:15:22,699 ERROR [DSLDAPMain] dirsync.DSLDAPMain (DSLDAPMain.java:331) - DSLDAPMain[handleIncomingReq] Parameter validation failed on sync agreement-dd5ec04b-4890-c76c-fc4c-285b76212582

Mohammed al Baqari · ‎11-13-2017

Seems that there is a change in the LDAP configuration either at cucm or ad
server which is causing the problem. Look an re-validate.

Slavi · ‎11-13-2017

Hi Mohammed,

thanks for your reply.

It is ja complete new Callmanager Installation and its the first LDAP Sync that fails.

It is never been synced before.

Greetings

RAustin70 · ‎08-21-2020

Silly question, where are the LDAP related logs found? I am having LDAPS issues right now and trying to verify it is a firewall issue.

Marco Lin · ‎03-19-2018

Hi, I fall in same issue, any idea for fix ? thanks a lot.

Marco

Slavi · ‎03-20-2018

Hello Marco,

the Problem is fixed.

It was a wrong Path of the Distingushed Name...

Greetings

Marco Lin · ‎03-20-2018

Hi, Slavi,

Thanks for your reply, can I know what's version with your openldap integrate with cucm?

Marco