Broken references cause communication error when debugging

Broken references cause communication error when debugging

  

Symptom:


When trying to debug your eSpace you receive the following error:


1-Click Publish required

Cannot debug your eSpace due to communication problems. Please verify that this eSpace is published and try to start the debugger again.


looking at the platform error logs you see errors similar to the following (picture below taken from the exported excel file):



The error stacks in the logs look like:


[1] Exception of type 'System.Web.HttpUnhandledException' was thrown.

  at System.Web.UI.Page.HandleError(Exception e)

  at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

  at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

  at System.Web.UI.Page.ProcessRequest()

  at System.Web.UI.Page.ProcessRequest(HttpContext context)

  at ASP._ping_aspx.ProcessRequest(HttpContext context)

  at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

  at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

(Continues in %ERR7d32895c-697a-4009-9f71-d3b64b999a31%END)



[2] Exception has been thrown by the target of an invocation.

(Inner Exception of %ERR4c853c70-542a-46fe-bd6c-e07e73552017%END)

  at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)

  at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)

  at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

  at OutSystems.HubEdition.RuntimePlatform.RunningInfo.InvokeRegister(IDbTransaction tran, String type)

  at ssCAN_ApolicesGIS._RunningInfo.RegisterInfo(IDbTransaction tran)

  at ssCAN_ApolicesGIS._RunningInfo.Register()

  at ASP._ping_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer)

  at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)

  at System.Web.UI.Page.Render(HtmlTextWriter writer)

  at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

(Continues in %ERReb0cf1d7-8823-41eb-ba1a-5fbb7bc0475d%END)



[3] Exception has been thrown by the target of an invocation.

(Inner Exception of %ERR7d32895c-697a-4009-9f71-d3b64b999a31%END)

  at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)

  at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)

  at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

  at OutSystems.HubEdition.RuntimePlatform.RunningInfo.InvokeRegister(IDbTransaction tran, String type)

  at ss<eSpace name>._RunningInfo.RegisterInfo(IDbTransaction tran)

(Continues in %ERR60b9f640-456d-4412-a9cf-959e74549abb%END)


Subsequent error stacks will be similar, most significant change will be the eSpace name at the bottom.


Cause:


There is a broken reference at a deeper level in your reference model (a reference of a reference of a...) causing the debugger initialization to fail. This is wrongly being reported as a communication error in Service Studio.


Resolution:

To fix this problem you need to fix the underlying cause - the broken reference. The innermost stack indicates which eSpace has the broken reference (look for the eSpace name as indicated in the example above).  Open the eSpace in Service Studio and refresh references, fixing any broken ones.


After you fix the broken reference, you should re-publish a solution containing all the involved eSpaces to assure that all references are updated.



This has been reported to R&D so that the message be more explicit. However, if you run into this, now you know how to fix it.

 
In this case only ss<eSpace name> should be updated and CAN_ApolicesGIS refreshed right? I am trying to fix my espaces but without luck
yes, you should open ss<eSpace name> in Service Studio and refresh references.

But afterwards you should republish ALL the consumers of this eSpace, not just the one that shows up above it in the stack. The easiest way to do this is to create a solution in Service Center and add the eSpace you fixed, then publish the current running version of this solution - this will cause all dependencies of the eSpace to be published as well.

If you're still having issues with the eSpace afterwards, you should open a support case for further investigation.