Users showing up in corporate directory that were deleted from LDAP/AD still

[Erick Bergquist]

Has anyone seen this before?

CUCM 9.1.1a (9.1.1.20000) LDAP integrated with one directory.

There are a few users not listed in the end user directory anymore in CUCM, but on the phone corp directory and in Jabber you see these users still. The directory URL is pointing to the CUCM server and we have tried both servers in the cluster.  They are not in the User Management -> End user list in CUCM at all any longer. 

If we add a test user, they show up in the directory and when we delete the test user they go inactive and go away after 2-3 days when garbage collection job clears them out and the test user is no longer in the directory.

The users are no longer in LDAP anymore either.  Is there a way to purge/refresh the CUCM directory?  Not finding much in bug search tool yet.

If we remove the LDAP Directory and add it back think that may clear up something? 

[Brian Meade]

Have you checked for a potential dbreplication problem?

Try running "utils dbreplication status" and then run "utils dbreplication runtimestate" over and over until you see all of the tables completed checking and it should show you if it found any errors.

[Erick Bergquist]

Yes, we have double checked DB replication and all that is fine. Will check it again. 

I was going to work on a SQL query to look into it also. 

[Niraj Rathod]

We are also facing same issue, is there any solution available.

Thanks.

[thawthorne_6]

Same here...I found this solution for older version, but haven't had a chance to try it yet

Problem

A user is deleted from Active Directory but still appears in Cisco Unified Communications Manger as inactive and stays there in a delete pending state. This issue occurs in a Cisco Unified Communications Manager cluster synchronized with the Active Directory .

Solution

Complete these steps in order to resolve this issue.

1. Choose Cisco Unified Serviceability> Tools> Control Centre - Feature Services

2. Choose the IP Address of the publisher.

3. Restart the Cisco DirSync service.

If this procedure does not resolve the issue, complete these steps:

1. Garbage Collection can cause this issue, so check the logs to determine if it is invoked.

2. Make sure that the Dirsync service is active.

3. Check the DirectoryPluginConfig table in the Cisco Unified Communications Manager database to see if there is an entry with pkid 54c43f99-a561-4f3a-868d-26a5547445d9.

   Note: The output of the run sql select * from DirectoryPluginConfig command confirms whether the Garbage Collector pkid is present in the DirectoryPluginConfig table when the DirSync service starts.

4. If the pkid is not present, open a case with the TAC Service Request Tool (registered customers only) and provide a remote support account so that TAC can update the DirectoryPluginConfig table to fix the Garbage Collection row.

5. Restart the DirSync service.