I created a custom list, and added a people picker control. When trying to submit the form, I am getting prompted for a username/password. After 3 attempts or clicking canceled I get a dialog box saying the page cannot be displayed.

If I submit the form from the server, It will submit with not problems. So, this leads me to believe it's a permissions issue within the site collection, but I am stumped as to where to correct this problem. All of the users are within the Site Collections Owners group.

  • When you do it 'from the server', what account are you using, and is it a different account to when you're getting the login prompts? Does anyone else also get this problem?
    – James Love
    Dec 2, 2012 at 20:01
  • I'm using the same credentials from both within the server, and from my desktop. Other users are having the same issue.
    – Jason
    Dec 2, 2012 at 20:05
  • Ok, and what authentication providers are in use?
    – James Love
    Dec 2, 2012 at 20:07
  • just claims based authentication
    – Jason
    Dec 2, 2012 at 20:11
  • Do you have ADFS, or a cross-domain trust on your organisation?
    – James Love
    Dec 2, 2012 at 20:13

2 Answers 2


Since the people picker resolves, I don't think there's any problem with your farm setup or how it talks to your domain (cross domain relationships, farm accounts, etc).

Since it seems to only fail when you save the item, I would inspect the ULS logs (c:\program files\common files\microsoft shared\web server extensions\14\logs) for clues.

Next is to systematically try to narrow down the problem.

Try this with new lists with people pickers, see if it works in other lists (indicates problem with permissions in the original list, Inherit all permissions in the original list to fix).

Find out if it works with lists in other subsites (problem with permissions in original subsite. Inherit permissions in the parent site to fix).

Find out if it works with lists in other site collections (problem with permissions in original site collection. Rebuild permissions in the top level site in the Site Collection as per your policies).

  • I will start from the logs, and see where it leads.
    – Jason
    Dec 2, 2012 at 20:48

We had a similar problem. In our case, it was the Black Ice and IBM Server Protection services. If these products are installed on your server, stop both of these services and see if that resolves the problem. If so, then you can modify the Black Ice rules so it doesn't block the particular traffic with PeoplePicker that it perceives as an attack.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.