Wednesday, 3 August 2016

SharePoint 2013 People Picker error: “Sorry, we’re having trouble reaching the server"

Today, i created a new site collection as requested by one of my client.
Everything was working as expected and it was time to give Full control access to client.
Life is full of uncertainty so is SharePoint ;).

As i was in process to give the permissions was got hit by below error.


1. Tried to give user access on other site collection but same error.

2. Tried to give user access on other web application but found out that issue is occuring for one web application.

3. Check event Logs but no luck.

4. Created a new site collection and web application same problem still occurs.


Performed an IISRESET  and everything was back to normal.

Happy SharePointing :)


  1. This comment has been removed by a blog administrator.

  2. this is the error I get after re-installing .net 3.5 activator and restarting IIS:

    Server Error in '/' Application.

    Runtime Error

    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

    Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

    Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.

  3. I was able to recover the SharePoint site by re-installing .NET framework 4.5x (not sure if that helped or not), running SharePoint repair (via add/remove programs) but the SharePoint repair wizard hung-up, so had to force close it. I restarted the box and made sure to start all the application pools that the SharePoint wizard more than likely stopped - the site stared working again, but I'm still at square one.