none
The people picker field contains unresolved or local entities, please correct this. RRS feed

  • Question

  • Hi,

    I created a second instance of Project Online and tried to synchronize Active Directory with the Enterprise resource pool.

    For this test I used an AD group which has been used for the sync of Project Server 2010 resources.

    I get the error above. What could be the reason?

    Thanks for any idea

    Sunday, January 19, 2014 10:59 PM

Answers

All replies

  • Check whether AD group is available on AD. while sync only give one value to people picker at a time then check . If after giving one value ( your test group) people picker is not able to fetch the group name from AD then problem could be domain or trust relation of group is not available in AD. 

    People Picker will only be able to return users, groups, and claims in the following topologies:
    1.The domain in which your SharePoint Server 2013/Project Server 2013 farm is currently installed.
    2.A domain that has a two-way trust relationship with the domain in which your SharePoint Server 2013/Project Server 2013 farm is currently installed.
    By default, People Picker only returns users, groups, and claims from the domain on which SharePoint Server 2013 is installed. If you want People Picker to return query results from more than one forest or domain, you can create a two-way trust between the forests or domains. For both these cases, People Picker functions automatically, and no additional configuration is necessary. When two-way trusts are established, the People Picker automatically returns results found in the trusted domains.

    The on-premises Active Directory forest must meet specific requirements. They include requirements for the schema master, global catalog servers, and domain controllers. It’s important to carefully read the latest requirements and ensure that your on-premises directory servers meet those requirements.

    please check in links:

    http://technet.microsoft.com/en-us/library/hh852469.aspx

    http://technet.microsoft.com/library/jj151831.aspx

    http://technet.microsoft.com/en-us/library/hh852533.aspx



    kirtesh



    • Edited by Kirteshtiw Monday, January 20, 2014 5:54 AM
    Monday, January 20, 2014 5:38 AM
  • Hi Kirtesh,

    Thanks a lot for these detailed explanations.

    In the French version of http://technet.microsoft.com/en-us/library/jj151831.aspx it is said:

    That means: "The computer cannot be a Domain Controller : the sync tool cannot be installed on AD Domain Controllers".

    This statement doesn't exist in the English version of the same document. Is it true ?

    For my test I'm using a domain with only one server which is also Domain Controller. Is it the cause of my issue?

    Thanks again


    • Edited by WLID1966 Monday, January 20, 2014 10:07 AM
    Monday, January 20, 2014 9:51 AM
  • As far as Project Server on premises is concerned, it is not giving any issue if domain controller is on same computer.

    I think as you are using project online facing issue. Issue is because of hybrid deployment. 

    http://technet.microsoft.com/en-us/library/jj151831.aspx    

    As per link :You can only install one computer running the Directory Sync tool between an on-premises Active Directory and an Office 365 tenant.

    As you mentioned you have created second instance could you please let us know if for 1st instance it is working 

    Also check for your global catalog server is configured properly or not


    kirtesh



    • Edited by Kirteshtiw Monday, January 20, 2014 10:10 AM
    Monday, January 20, 2014 10:08 AM
  • My first instance was created from another computer (Win 7) which is not a member of a domain. So I created all the resources manually.

    Why do you think "Issue is because of hybrid deployment"? I'm not using Exchange.

    Thanks for your help

    • Edited by WLID1966 Monday, January 20, 2014 11:01 AM Issue is because of hybrid deployment
    Monday, January 20, 2014 10:22 AM
  • Your need to separate your AD machine from the SharePoint farm.

    Gary Chefetz, MCITP, MCP, MVP msProjectExperts
    Project and Project ServerFAQs
    Project Server Help BLOG

    Wednesday, February 5, 2014 3:31 PM
    Moderator
  • Can someone please help in what exactly needs to be done to resolve this issue.

    We have Project Online which is working with On-Premise AD authentication.

    It worked for me once and now I am trying to sync after a week and it is giving error:

    • The People Picker field contains unresolved or local entities, please correct this.


    Abhijeet, MCTS | abhijeetm@outlook.com

    Thursday, May 15, 2014 7:35 AM