Terminal connection to AS 400 is support only via windows legacy project and not through windows projects. How to handle it?

Terminal connection to AS 400 is support only via windows legacy project and not through windows projects. How to handle it?
When we try to configure terminal with direct connection in windows project, on clicking Start recording,
we are getting below error. Kindly suggest what can be done, as legacy will be phased out in next enterprises release.

‘{DependencyProperty.UnsetValue}’ is not a valid value for property ‘BorderBrush’.

Error: System.Exception: ‘{DependencyProperty.UnsetValue}’ is not a valid value for property ‘BorderBrush’.
at System.Windows.DependencyObject.GetEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, RequestFlags requests)
at System.Windows.DependencyObject.GetValueEntry(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, RequestFlags requests)
at System.Windows.DependencyObject.GetValue(DependencyProperty dp)
at System.Windows.Controls.Border.get_BorderBrush()
at System.Windows.Controls.Border.ArrangeOverride(Size finalSize)
at System.Windows.FrameworkElement.ArrangeCore(Rect finalRect)
at System.Windows.UIElement.Arrange(Rect finalRect)
at System.Windows.ContextLayoutManager.UpdateLayout()
at System.Windows.ContextLayoutManager.UpdateLayoutCallback(Object arg)
at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler), HResult -2146233079

1 Like

Hi @Rgopalsamy ,
The error message you received indicates that there is an issue with the BorderBrush property of the control being used to display the terminal connection in the Windows project. This error message is not related to the fact that AS400 terminal connection is only supported via Windows legacy project.

Here are some things you can try to resolve the issue:

  1. Update the Windows project to the latest version: The error message you received indicates that you are using a beta version of the Windows project. It is possible that this issue has been fixed in a later version of the project. Try updating the project to the latest stable version and see if the issue persists.
  2. Check the value of the BorderBrush property: The error message suggests that there is an issue with the value of the BorderBrush property. Check to make sure that the value being used is valid. You can also try setting the BorderBrush property to a specific color value and see if that resolves the issue.
  3. Contact the vendor support: If the above solutions don’t work, you can contact the vendor support for the Windows project to report the issue and get assistance in resolving it. They may be able to provide you with more detailed information or a workaround for the issue.

Regarding the AS400 terminal connection support only via Windows legacy project, you may want to explore other options like using a third-party terminal emulator or scripting the terminal interaction using a programming language that supports AS400 connectivity. This can help you future-proof your solution in case the legacy project is phased out in the next enterprise release.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.