MS Surface application errors

Epicor ERP 10
1

I have an issue on Microsoft Surface Pro 3’s where when the user tries to open certain screens (Preferences is an example), an error occurs:

Application Error

Exception caught in: PresentationCore

Error Detail

Message: ‘System.Windows.Documents.Hyperlink’ is not a Visual or Visual3D.
Program: PresentationCore.dll
Method: AsVisual

Client Stack Trace

at MS.Internal.Media.VisualTreeUtils.AsVisual(DependencyObject element, Visual& visual, Visual3D& visual3D)
at MS.Internal.Media.VisualTreeUtils.AsNonNullVisual(DependencyObject element, Visual& visual, Visual3D& visual3D)
at System.Windows.Media.VisualTreeHelper.GetParent(DependencyObject reference)
at IceShell.UIHelper.FindVisualParent[T](DependencyObject child, Boolean checkCurrent)
at IceShell.SettingsApp.Tap(Object sender, InputEventArgs e)
at IceShell.BaseApp.BaseApp_Tap(Object sender, InputEventArgs e)
at IceShell.Apps.Controls.Touch.GestureTrackerManager.GestureTracker_GestureFinished(TouchGesture gesture, StylusEventArgs args)
at IceShell.Apps.Controls.Touch.GestureTracker.ProcessUp(Point location, StylusEventArgs args)
at IceShell.Apps.Controls.Touch.GestureTrackerManager.Process_TouchUp(Object sender, StylusEventArgs args)
at System.Windows.Input.StylusEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.ContentElement.RaiseTrustedEvent(RoutedEventArgs args)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
at System.Windows.Input.StylusLogic.InputManagerProcessInput(Object oInput)
at System.Windows.Input.StylusLogic.PreProcessInput(Object sender, PreProcessInputEventArgs e)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at Ice.Lib.UI.ApplicationWatcher.StartApplication(ApplicationContext context)
at Ice.Lib.UI.App.IceShellLaunch.<>c__DisplayClass2.b__1()
at Ice.Lib.UI.App.IceShellLaunch.ShowMenuForm()
at Ice.Lib.UI.App.LaunchBase.ShowDialog(String[] args)

2

This one doesn’t run Windows RT Does it?

3

Well, from what I read, the surface pro 3’s are supposed to be full Windows.

I did check system settings and OS is listed as:
Windows 8.1 pro

4

What version of Epicor?

5

10.1.400

6

@Bart_Elia or @aidacra have any input or should I just open up a ticket?

7

FWIW, I run Epicor 10.1.400 daily on my Surface Pro 3, without any issues.

Thanks,

Norman Hutchins
System Administrator
Howell Laboratories, Inc.

1 Like
8

Please open a Support case and our team will review.

1 Like
9

Thanks Norman, is your running Windows Pro 8.1?

Also, can you verify you can open settings in Epicor?

10

No, currently running Windows 10 Pro. I had 8.1 for a bit, but it would
have been Epicor 10.0 at that point.

Thanks,

Norman Hutchins
System Administrator
Howell Laboratories, Inc.

1 Like
11

I am also using a surface pro 3 daily with E10.1.400.12 & windows 10 Pro. The surface products have had several firmware updates so might be worth making sure they are installed. I think you have to manaully run windows update to get them.

Brett

1 Like
12

Wow, that’s a new one on me. I saw the title and figured it was the high DPI issue with Infraguistics controls we had. I live 99% of the time on the server so don’t keep up with the client all the time but am always curious. Ticket please!

1 Like
13

It looks like its not so much related to Epicor as it is to .NET - Telerik even has similar reports just like Infragistics. BUG: Exception {"'System.Windows.Documents.Hyperlink' is not a Visual or Visual3D."} in UI for WPF | Telerik Forums

2 Likes
14

I wouldn’t disagree and it seems like there are workaround within .NET. I doubt Epicor is going to take that route because presumably I am the only one having this issue with all of my MS Surface Pro 3’s (From 8.1pro to 10pro)

15

Hi,

I opened a ticket for this a few months back. Epicor will crash when interacting with the old calendar control when the ONLY monitor/screen attached to computer is touch screen. You can see they have half fixed this by creating a new calendar widget in 10.1.500 that is their own WPF control and not an Infragistics wrapped control.

EDIT. This was on Win 10 Pro.

1 Like