Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Supply chain | Supply Chain Management, Commerce
Unanswered

POS Printer & Cash Drawer Setup for SureMark 4610 using MPOS & OPOS drivers

(0) ShareShare
ReportReport
Posted on by

hello experts,

could you please provide a detailed instruction on how to setup the POS SureMark 4610 printer for MPOS using OPOS drivers?

I have installed the opos drivers and am able to perform test prints from the OPOS utility. Also printing the X report from POS is working fine, but the receipt just wont print. Instead the printer is only printing a small barcode in the middle without any meaning.

Furthermore I am not able to open the cash drawer using the POS. The cash drawer opens fine using the "Demo" in the OPOS setup utility but wont open from POS. When clicking on "open drawer" i just get the spinning wheel for a second and nothing happens (no error message).

Any advise on how to set that up properly?

Thank you very much! Your advise is highly appreciated!

  • Juergen Kretschek Profile Picture
    on at
    RE: POS Printer & Cash Drawer Setup for SureMark 4610 using MPOS & OPOS drivers

    Hi Michael,

    Is this error message still thrown? If yes, do not hesitate to raise a support incident to Microsoft Support.

    Along with that, installing the Debug version of the OPOS CCO and collecting a trace could be insightful to troubleshoot this further.

    Thank you.

  • Michael_G. Profile Picture
    on at
    RE: POS Printer & Cash Drawer Setup for SureMark 4610 using MPOS & OPOS drivers

    In the peripheral simulator logs i get the following error message:

    The request was failed due to the following error: "Microsoft_Dynamics_Commerce_HardwareStation_Printer_Error: OPOS printer failed to execute 'PrintNormal' with error '106', extended error code - 0".

  • Michael_G. Profile Picture
    on at
    RE: POS Printer & Cash Drawer Setup for SureMark 4610 using MPOS & OPOS drivers

    Hello and thank you for your feedback! I have installed the peripheral simulator and tested it there. The setup is not working from the peripheral simulator, even though my test from the drivers OPOS utility was successful (so the device is connected and has no hardware failure).

    Here is the error log from the peripheral simulator:

    ‚An unhandled exception occurred, and the application is terminating.\n{O]System.InvalidOperationException: The calling thread cannot access this

    Object because a different thread owns it,

    at System. Windows. Threading.Dispatcher.VerifyAccess0

    at System. Windows. Threading.Dispatcher.DisableProcessingQ

    at System Windows.Documents.TextContainer.BeginChangelBoolean undo)

    at System Windows. Documents.TextElementCollection’1.Ada(fextElementIype item)

    at Microsoft.Dynamics.Commerce.VirtualPeripherals.Modules.TestLog.OnColledionChanged(Object sender, NotifyCollectionChangedEventArgs

    eventargs)

    at System.Collections.ObjectModel.ObservableCallection'1.OnCollectionChangediNotityCollectionChangedEventargs e)

    at System.Collections.ObjectModel.ObservableCollection 1.insertitem{int32 index, T item)

    at Microsoft.Dynamics.Commerce.VirtualPeripherals.Modules.TestOperationContext.<StartTest> d_34.MoveNiext(

    End of stack trace from previous location where exception was thrawn

    at System.Runtime.ExceptionServices.ExceptionDispatchinfo.Throwü

    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessandDebuggerNotificationffask task)

    at Prism.Commands.DelegateCommandBase.<Execute> d_14.MoveNext

    End of stack trace from previous location where exception was thrawn

    at System.Runtime,ExceptionServices.ExceptionDispatchinfo.Throwü

    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessandDebuggerNotificationffask task)

    at Prism.Commands.DelegateCommandBase.<System-Windows-Input-ICommand-Execute>d_12.MoveNext(

    End of stack trace from previous location where exception was thrawn

    at System.Runtime.ExceptionServices.ExceptionDispatchinfo.Throwü

    at System.Windows. Threading.Exception\Vrapper.internalRealCall(Delegate caliback, Object args, Int32 numargs)

    at System. Windows. Threading.Exception\Vrapper.TryCatch\When(Object source, Delegate callback, Object args, Int32 numArgs, Delegate

    eatehHandler)

    at System. Windows. Threading.DispatcherOperation.invokelmpiQ

    at MS.internal.CulturePreservingExecutionContext.Callback\Wrapper(Object obj)

    at System.Threading.ExecutionContext.RuninternallExecutionContext executionContext, ContextCallback callback, Object state, Boolean

    Preservesyncche)

    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContestCallback callback, Object state, Boolean preservesyncc)

    at $ystem.Threading.ExecutionContext.Run[ExecutionContext executionContext, ContestCallback callback, Object state)

    at MS.Internal.CulturePreservingExecutionContext.Run[CulturePreservingExecutionContext executionContext, ContextCallback callback, Object

    state)

    at System. Windows. Threading.DispatcherOperation.invoke)

    at System. Windows. Threading.Dispatcher.ProcessQueue()

    at System. Windows. Threading.Dispatcher. WndProcHook{intPtr hwnd, Int32 msg, IntPtr wParam, IntPtr IParam, Booleanät handled)

    at MS.Win32.Hwnd\Wrapper. WndProcintßtr hwnd, Int32 msg, IntPtr wParam, IntPtr IParam, Booleanä handled)

    at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object 0)

    at System. Windows. Threading.Exception\Vrapper.internalRealCall(Delegate caliback, Object args, Int32 numargs)

    at System. Windows. Threading.Exception\Vrapper.TryCatch\When(Object source, Delegate callback, Object args, Int32 numArgs, Delegate

    eatehHandler)

    at System. Windows. Threading.Dispatcher.LegagyInvokelmp![DispatcherPrioritypriority, TimeSpan timeout, Delegate method, Object args, Int32

    numargs)

    at MS.Win32.HwndSubclass.SubclassWndProcfintPtr hwund, Int32 msg, IntPtr wParam, IntPtr IParam)

    at MS.Win32.UnsafeNativeMethods.DispatchMlessage(MSGA msg)

    at System. Windows. Threading.Dispatcher.PushFramelmpI(DispatcherFrame frame)

    at System. Windows.Application.RunDispatcher(Object ignore)

    at System. Windows. Application.Runinternal(Window window)

    at Microsoft.Dynamics.Commerce.VirtualPeripherals.Client.App.Main

    Any ideas what could be the issue?

    Thank you!

  • Juergen Kretschek Profile Picture
    on at
    RE: POS Printer & Cash Drawer Setup for SureMark 4610 using MPOS & OPOS drivers

    Hi Michael,

    Did you check if your scenario is working with Peripheral Simulator?

    Peripheral simulator for Commerce - Commerce | Dynamics 365 | Microsoft Docs

    Kind regards,

    Juergen [MSFT]

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > Supply chain | Supply Chain Management, Commerce

#1
Zain Mehmood Profile Picture

Zain Mehmood 462 Moderator

#2
Danny Bilodeau Profile Picture

Danny Bilodeau 156 Moderator

#3
Laurens vd Tang Profile Picture

Laurens vd Tang 120 Super User 2025 Season 1

Featured topics

Product updates

Dynamics 365 release plans