unable to find some windows AD users in People Directory
Asked by Tom Sun:

unable to find some windows AD users in People Directory, not all of them, just a few of


Answers:
author: Shannon S
body: Hi Tom,

Have those users logged in personally to Confluence yet? A user won't show in People Directory unless they have a profile page yet, and that occurs once they've logged in for the first time.

Otherwise I would try these steps below:

* [Missing People in Confluence People Directory](https://confluence.atlassian.com/confkb/missing-people-in-confluence-people-directory-779166036.html)

You can also try by accessing their profile URL directly, such as:

```
https://CONFLUENCE_BASE_URL/display/~<username>
```

And then see if they start to appear for you.

Regards,

Shannon

comments: author: Tom Sun
body: Dear Shannon,

I have tried the "**Workaround 2**", but it didn't solve my problem, below are the error logs:

WARN \[Caesium-1-1\] \[search.lucene.queue.JournalIndexTaskQueue\] lambda$flushQueue$1 Failed to process index task for entry 'JournalEntry{id=80270, journalId=JournalIdentifier{journalName=main_index}, creationDate=2018-02-06 09:22:52.724, type=REINDEX_ALL_USERS, message=null}': Only the latest version of a searchable is supported.  
java.lang.UnsupportedOperationException: Only the latest version of a searchable is supported.

WARN \[Caesium-1-1\] \[confluence.impl.hibernate.ConfluenceHibernateTransactionManager\] doRollback Performing rollback. Transactions:  
-\>\[com.atlassian.confluence.search.lucene.LuceneIndexManager.flushQueue\]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT (Session #750538312)  
\[null\]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT (Session #503040205)  
\[null\]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT (Session #1144345528)  
2018-02-06 09:22:59,492 WARN \[Caesium-1-1\] \[confluence.impl.search.IndexFlushScheduler\] lambda$new$1 Failed to flush index queue LuceneIndexFlusher, retry in 10s  
org.springframework.transaction.UnexpectedRollbackException: Transaction rolled back because it has been marked as rollback-only


author: Shannon S
body: Hi Tom,

Thank you. Were you able to verify if the users had ever logged in and attempted to reach their profile directly? If they have not, once you access their profile directly it will propagate the entry in People Directory.

Otherwise, I would recommend that you try to [rebuild the index from scratch](https://confluence.atlassian.com/confkb/how-to-rebuild-the-content-indexes-from-scratch-on-confluence-server-110035351.html) and see if that helps your issue.

If none of this works, can you please let me know what database and version you're using? I can use this information to focus my search for you a bit more.

Regards,

Shannon


author: Tom Sun
body: Hi Shannon,

Let me try rebuild the index this weekend, I will post the result here once I have done it.

Thanks for your kindly help.


author: Tom Sun
body: All of our users had logged in the wiki already, I have tried accessing their profiles, but they didn't appear in the ppl directory.

So, let me rebuild the index first.


author: Shannon S
body: Okay, Tom! Thank you for confirming that.

Just follow-up with me after the weekend when you have a chance to reindex and if it doesn't help, we can continue to troubleshoot from there.

Regards,

Shannon


author: Tom Sun
body: Hi Shannon,

I have tried "rebuild the index" in the management console menu, it took about 12 hours, and it solved my problem.

Thank you for your help!

Tom


author: Shannon S
body: Hi Tom,

Thank you for coming back to confirm the resolution!

Reindexing can indeed take a while especially on larger instances which is why we recommend it during off-hours. At times I have seen indexing take even days so if you have to do it in the future perhaps it can be over a weekend or schedule some known downtime.

Do let me know if you have any further questions, otherwise, have a pleasant week!

Shannon