I’ve encountered these limitations on my main development farm and was able to reproduce on one other… one March 2013 PU and one August 2013 CU. It may not be a widespread issue and I am looking for a solution – any help appreciated in the comments 🙂
Whilst host-named site collections have been around for a while, it’s only with the release of SharePoint 2013 that they are the “preferred method to deploy sites in SharePoint 2013”. I’m not sure how linked this is to Cloud First and Office 365 but I’d hazard a guess they are linked..
However, I stumbled across an annoying issue using Claims-based Authentication (as standard) when using the People Picker from Office (2010/2013) from the Document Information Panel accessing a content type in a host-named site collection:
Word 2013 just crashes (helpful!) and Word 2010 hangs for a while but at least doesn’t crash.
Using Fiddler highlights some web service calls – initially to /_vti_bin/people.asmx as you might expect to resolve the name of the Owner, but subsequently to
/_vti_bin/spclaimproviderwebservice.svc which results in this undesirable behaviour:
The main element being HTTP/1.1 500 System.ServiceModel.ServiceActivationException
It didn’t take long to discover that this was being caused by WCF bindings – in a normal non-SharePoint environment it might be easy to add in the following to the web.config:
Even in SharePoint 2013 this change WILL fix the above issue, however it also causes other issues…. such as
– Various other client-side functionality
The now familiar ServiceActivationException pops up…
I’m yet to find a proper workaround or configuration which will allows both People Picker and Drag/Drop etc to work on premises. Maybe I missed something simple…