Tag Info

New answers tagged

0

I was facing the same error. Make sure the solution you have deployed must have called the profile service internally. Deactivation and then activation of the custom features worked for me.


0

SharePoint Web Services use WCF which runs "side-by-side" with ASP.NET within IIS and thus do not get logged within the HTTP pipeline. https://msdn.microsoft.com/en-us/library/aa702682.aspx I tried setting <serviceHostingEnvironment aspNetCompatibilityEnabled="true" /> in the web.config, but it didn't seem to help. I successfully enabled WCF tracing ...



Top 50 recent answers are included