0
Fixed

Exception thrown when attempting to Auto Configure FIM Agent

Richard Courtenay 9 years ago updated by anonymous 5 years ago 5

After creating a FIM agent (Server Name = localhost, Authentication = "Windows and all others are defaults) I attempt to click the "Auto Configure for FIM Agent" button. Upon accepting the prompt I get the following stack track

System.ArgumentException: The parameters dictionary contains a null entry for parameter 'id' of non-nullable type 'System.Guid' for method 'System.Web.Mvc.ActionResult AutoConfigureForFIMAgent(System.Guid)' in 'Unify.EventBroker.Web.AgentsController'. An optional parameter must be a reference type, a nullable type, or be declared as an optional parameter.
Parameter name: parameters
at System.Web.Mvc.ActionDescriptor.ExtractParameterFromDictionary(ParameterInfo parameterInfo, IDictionary`2 parameters, MethodInfo methodInfo)
at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
at System.Linq.Enumerable.ToArrayTSource(IEnumerable`1 source)
at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters)
at System.Web.Mvc.ControllerActionInvoker.<>c_DisplayClass15.<InvokeActionMethodWithFilters>b_12()
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodWithFilters(ControllerContext controllerContext, IList`1 filters, ActionDescriptor actionDescriptor, IDictionary`2 parameters)
at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName)

Did you download the second release of 3.0.0.1?

Patrick sent out a follow-up email stating that there was a problem with the first release.

If you are using the latest release, please assign back to Patrick.

Thanks.

I'll check, but I'm sure I have the newer one running. Downloaded both so I may have accidently run the older exe...I'll check

Reinstalled to be sure and its reproducable still

Not sure what happened here, but I can confirm this issue still exists in the v3.0.0.1 release on JIRA. It's already fixed in the latest build however, so it must have been an issue with the second installer we released. Can't do anything about it now I'm afraid, but it will be fine again in v3.0.0.2