Error when editing WCF communicator following service restart
When attempting to edit the WCF communicator for SharePoint 2010 User Profile after a service restart, the following error appears on the edit screen where the WCF details would be:
System.ArgumentNullException: Value cannot be null.
Parameter name: source
at System.Linq.Enumerable.ToDictionaryTSource,TKey,TElement(IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)
at System.Linq.Enumerable.ToDictionaryTSource,TKey,TElement(IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector)
at ASP._Page_Views_Temp_PlugIns_ExtendedPartialPlugInAction_WCFCommunicatorWcfCommunicator_cshtml.Execute() in c:\Program Files\UNIFY Solutions\Identity Broker\Web\Views\Temp\PlugIns\ExtendedPartialPlugInAction\WCFCommunicatorWcfCommunicator.cshtml:line 48
at System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext, TextWriter writer, WebPageRenderingBase startPage)
at System.Web.Mvc.ViewResultBase.ExecuteResult(ControllerContext context)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilter(IResultFilter filter, ResultExecutingContext preContext, Func`1 continuation)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultWithFilters(ControllerContext controllerContext, IList`1 filters, ActionResult actionResult)
at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName)
I attempted it again after forcing a cache refresh (Ctrl + F5) on the connector details page, and the edit page was back to normal. Hence there is a workaround, but it may be unexpected for normal users.
Customer support service by UserEcho
Any idea what caused it to get into this state? Has it happened more than just this once?
This was only occurring for 2010 User Profile - 2010 Org Profile was fine. The session was correctly populated with the configuration values, but the WCF communicator view was attempting to retrieve values from the session using different keys, hence all the fields were being populated by nulls (even though the values were correctly retrieved and displayed for the Display view). This was fixed by moving the ClientAction attribute before the description and display name attributes on the Resources method. Unsure as to why this may have affected things following a restart, but this has prevented the issue from occurring locally.
Marked as resolved, could you please confirm in the next build Tony?
reopened for time.
closed following time.