0
Not a bug

Cannot create sub components within an operations list

Hayden Gray 4 years ago updated by Matthew Davis (Technical Product Manager) 4 years ago 1

Hello,


After a recent upgrade to UNIFYNow 3 days ago, after this the service was working fine for some time and confirmed last night still working as expected. Though this morning when attempting to create sub operations (i.e check operation/schedule/listen operation/operation) I get presented with the following error:

Unify.Framework.UnifyCommunicationException: The service client does not implement the IEventServiceClient type.
at Unify.Framework.Web.UnifyController.GetClient[TServiceClient]() in C:\agent\_work\69\s\Source\Web\Unify.Framework.Web\Extensions\UnifyController.cs:line 59
at Unify.EventBroker.Web.OperationController.<.ctor>b__103_1(UnifySiteMapNode node, UnifySiteNodeAttribute attribute, RequestContext context, IDictionary`2 dynamicValues, RouteData data, NameValueCollection postData, NameValueCollection queryString) in C:\agent\_work\86\s\Source\Unify.EventBroker.Web\Controllers\OperationController.cs:line 307
at Unify.Framework.Web.UnifySiteMapProvider`2.UpdateNodeForRequest(TNode node, TNodeAttribute nodeAttribute, RequestContext requestContext, IDictionary`2 dynamicValues, RouteData routeData, NameValueCollection postedData, NameValueCollection queryString) in C:\agent\_work\69\s\Source\Web\Unify.Framework.Web.SiteMap\UnifySiteMapProvider.cs:line 150
at Unify.Framework.Web.UnifySiteMapDynamicTree`2.UpdateParentForRequest(TNode parentNode, RequestContext globalRequestContext, IDictionary`2 dynamicValues, RouteData& childRouteData, NameValueCollection& childPostData, NameValueCollection& childQueryString, MethodInfo& childAction, UpdateNode`2 updateNode) in C:\agent\_work\69\s\Source\Web\Unify.Framework.Web.SiteMap\UnifySiteMapDynamicTree.cs:line 291
at Unify.Framework.Web.UnifySiteMapDynamicTree`2.FindNodeAndUpdateBranch(HttpRequest request, UpdateNode`2 updateNode) in C:\agent\_work\69\s\Source\Web\Unify.Framework.Web.SiteMap\UnifySiteMapDynamicTree.cs:line 222
at System.Web.SiteMapProvider.FindSiteMapNode(HttpContext context)
at System.Web.SiteMapProvider.get_CurrentNode()
at Unify.Framework.Web.UnifySiteMapExtensions.DecorateForm(HtmlHelper htmlHelper, Func`1 form, String submitText, String formId, String title, String name) in C:\agent\_work\69\s\Source\Web\Unify.Framework.Web.SiteMap\UnifySiteMapExtensions.cs:line 50
at ASP._Page_Views_Operation_CreatePlugInOperation_cshtml.Execute() in c:\Program Files\UNIFY Solutions\Event Broker\Web\Views\Operation\CreatePlugInOperation.cshtml:line 16
at System.Web.WebPages.WebPageBase.ExecutePageHierarchy()
at System.Web.Mvc.WebViewPage.ExecutePageHierarchy()
at System.Web.WebPages.StartPage.ExecutePageHierarchy()
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.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultWithFilters(ControllerContext controllerContext, IList`1 filters, ActionResult actionResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass1e.b__1b(IAsyncResult asyncResult)

There are no additional logs produced in the application log or the even viewer logs.

The version of UNIFYNow is v4.0.4. I have checked the other environments and they are not affected by the issues. Any help is greatly appreciated.

Thanks

Answer

Answer
Not a bug

IIS was likely caching the object or page, and causing issues. An IIS reset has solved the problem.

Answer
Not a bug

IIS was likely caching the object or page, and causing issues. An IIS reset has solved the problem.