Call Back Error in SharePoint People Picker Control.

Most of the blog says its permission issue: - at least for us it was not.

http://blogs.msdn.com/b/sofocle/archive/2011/05/17/sharepoint-2010-people-picker-issue-quot-there-was-an-error-in-the-callback-quot.aspx

As per above article – I check all the permission and User Policy – Everything was properly set, UPSA was also working fine

Issue: - When I was checking for user in address book or people picker

When I was adding the user in SharePoint group – It was throwing the Unexpected error:-

Architecture Structure of Server:-

Why I am explaining the architecture server – It’s very important  because most of people doesn’t know how to check the logs in all server.If we have proper farm setup with multiple server – We should check the Logs in all server.

Here is Power shell command which give  consolidated result from all sharepoint server.

Merge-SPLogFile –Path “E:\SPLogs\MergedLogs.log” –Correlation 3ae2a6c0-da14-43a1-afda-5bb6bbff3d43

Resolution:-

Steps Followed:-

• Restart SharePoint Timer Services
• Remove the Attached DB from Web Application using Central Admin
• Created DB with same Name.
• After Configuring the DB – Unable to browse site. – It was showing “Page Not Found”.Scared what happen suddenly.
• Finally - Clear the SharePoint Configuration Cache. Location “Drive:\ProgramData\Microsoft\SharePoint\Config\GUID”
• Deleted all log files
• Modify the Cache.ini with any numeric value put like 1 and save.

It seems like some services stuck in between or some configuration cache issue. After following the above steps.

SharePoint Site was browsing fine and people picker was also working fine without any fail.

Happy Coding.