Sync Log page and Last Sync information not updating for the AD profile in VMware Identity Manager

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Access the administrative interface and observe that the synchronization logs and last synchronization timestamps remain stagnant during sync attempts.
• Confirm that newly created Active Directory accounts are not being imported in the vIDM.
• There are no errors when syncing the Active Directory.
• Review the analytics-service.log file and identify errors related to the service experiencing failures when attempting to remove document files. 

<DATE> <TIME> GMT INFO  <HOSTNAME>:analytics (ForkJoinPool-1-worker-7) [-;<ID>;<IP_ADDRESS>;<ID>;-] com.vmware.idm.analytics.ConsumerService - Received 4 audit documents to store
<DATE> <TIME> GMT INFO  <HOSTNAME>:analytics (ForkJoinPool-1-worker-9) [-;<ID>;<IP_ADDRESS>;<ID>;-] com.vmware.idm.analytics.elasticsearch.ElasticSearchHelper - Created index: v4_<DATE>_syncalert
<DATE> <TIME> GMT INFO  <HOSTNAME>:analytics (ForkJoinPool-1-worker-9) [-;<ID>;<IP_ADDRESS>;<ID>;-] com.vmware.idm.analytics.elasticsearch.ElasticSearchHelper - Created index: v4_<DATE>_audit
<DATE> <TIME> GMT INFO  <HOSTNAME>:analytics (ForkJoinPool-1-worker-9) [-;<ID>;<IP_ADDRESS>;<ID>;-] com.vmware.idm.analytics.elasticsearch.ElasticSearchHelper - Created index: v4_<DATE>_syncresult
<DATE> <TIME> GMT INFO  <HOSTNAME>:analytics (I/O dispatcher 20) [;;;;] com.vmware.idm.analytics.elasticsearch.JestBulkAddResultHandler - Stored 4 documents
<DATE> <TIME> GMT INFO  <HOSTNAME>:analytics (ForkJoinPool-1-worker-9) [-;<ID>;<IP_ADDRESS>;<ID>;-] com.vmware.idm.analytics.ConsumerService - Received 2 search documents to delete
<DATE> <TIME> GMT WARN  <HOSTNAME>:analytics (I/O dispatcher 20) [;;;;] com.vmware.idm.analytics.elasticsearch.JestBulkDeleteResultHandler - Unable to bulk delete 2 out of 2 documents: One or more of the items in the Bulk request failed, check BulkResult.getItems() for more information.
Group-410 404 {"type":"index_not_found_exception","reason":"no such index [v2_searchentities_groupsearchdocument]","index":"v2_searchentities_groupsearchdocument","resource.id":"v2_searchen
tities_groupsearchdocument","resource.type":"index_expression","index_uuid":"_na_"}
Group-411 404 {"type":"index_not_found_exception","reason":"no such index [v2_searchentities_groupsearchdocument]","index":"v2_searchentities_groupsearchdocument","resource.id":"v2_searchen
tities_groupsearchdocument","resource.type":"index_expression","index_uuid":"_na_"}
<DATE> <TIME> GMT WARN  <HOSTNAME>:analytics (I/O dispatcher 20) [;;;;] com.vmware.vidm.common.vertx.exception.handler.DefaultExceptionHandler - Unexpected Exception: com.vmware.vidm.common.vertx.exceptions.WebApplicationException: INTERNAL_SERVER_ERROR

Environment

VMware Identity Manager 3.3.7 (vIDM)

Cause

Corrupted or incompatible Active Directory profile configuration state resulting from a product upgrade, which blocks the analytics service from processing or clearing synchronization document files.

Resolution

NOTE: Create a snapshot without memory for all nodes before proceeding.

1. Export or document all current Active Directory profile configuration details (including hostname, port, Base DN, Bind DN, and sync mappings (groups and users)).

2. Delete the problematic Active Directory profile configuration from the system.

3. Create a new Active Directory profile utilizing the documented settings.

4. Run a manual sync operation to confirm user ingestion and log updates function correctly.