The issue of people and group fields on document infomation panel and InfoPath forms

Posted: June 5, 2014 in Errors, InfoPath, SharePoint, SharePoint Designer
Tags: , , , , ,

Hello everyone

After investigating for about a week on an issue, I’m here to summerize and give you information about it.

Our platfrom is SharePoint 2013 and using office 2013 client applications. We have a root site collection and couple of host named site collections also.

If you need to use people and group fields in Document Infomation Panel or as people picker in InfoPath forms, maybe you have seen that your InfoPath form or Word document stops working and it may hang or carsh.

By searching internet you will come up with some ideas that you should modify the web.config file and set attribute MultipleSiteBindingEnabled to True.

Something like this:


<system.serviceModel>
<serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />
</system.serviceModel>

However I found that this modification could have lots of annoying side effects and is not working properly. Although depends on your configuration. I recommend don’t do it!Β  It can cause the drag and drop functionality on document libraries stop working, it can cause the internal people and group fields (for example for lists) stop searching the directory and it can cause SharePoint designer to not be able to connect to your sites.

What I found instead was quite simple suprisingly. We had used manully binding into IIS which I found is not correct. To summerize and cut a long story short, I found:

  1. There is no need to modify the web.config file for adding multiple site bindings attribute
  2. And more importantly never ever manually add site binding into the IIS console

 

Just following this two instructions everything works like a charm in our farm.

Hope this helps.

Navid πŸ™‚

 

 

 

Comments
  1. Joe Balberde says:

    Perhaps I’ve missed what you’ve done here. What are the steps to correct this?

    Thanks

  2. Zgembo says:

    Yes, please do share, we are running into the same problem.

  3. Tim says:

    Awesome thanks, i’d done exactly the same so this sorted my issue πŸ™‚

  4. MaximusBeredius says:

    worked like a charm, exactly as you’d said… THanks so much for the pointer in the right direction!!

  5. Hamed says:

    I can’t believe this! I have been googling for hours with no luck, this was so easy to fix and yet no body else is talking about it:)
    Thank you so much. You are awesome.

  6. Darcie Neibert says:

    Hi. Can you share solution? Thanks!

  7. Ben says:

    what is the solution? I have running into a similar issue where the people picker in DIP no longer works properly… I can select a person but once I hit OK, the field kind of dies on me and nothing really get stored in it.

  8. Denis says:

    If you need to have multiple bindings on the web app in IIS you can apply the following fix

    Create a backup of web.config before applying it!
    In the web.config of the web app where the people picker issue is add this lines:

    NOTE: on the web app URL don’t use HTTPS because is not working. add the web app url with HTTP
    good luck! πŸ™‚

    • Denis says:

      *system.serviceModel*
      *serviceHostingEnvironment aspNetCompatibilityEnabled=”true”*
      *baseAddressPrefixFilters*
      *add prefix=”web app URL” /*
      */baseAddressPrefixFilters*
      */serviceHostingEnvironment*
      */system.serviceModel*

      Instead of the * add this sign >
      Looks like i can’t post the lines properly in the comment with this sign “>” πŸ™‚

  9. Denis says:

    ok so at the beginning of the lines use the LESS symbol and at the end of the lines use the GREATER symbol
    I hope everyone understands πŸ˜€
    good luck!

  10. Mark Taylor says:

    How do you fix this? multiple site bindings seemed to work. It has been reset to false now (monthly updates or another tech reset) now I have the people picker not working.

Leave a comment