web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Retail POS Receipt Printer Issue

(0) ShareShare
ReportReport
Posted on by

Hello, we are setting up Dynamics AX Retail POS. We have our registers and hardware profiles setup. When we pull up a sale under show journal, hit receipt the receipt comes up. When we hit print it comes up with a message that "No printer type has been defined". We have the printer driver set to Windows, have the receipt profile set and the print behavior to always print. We have an Epson TM-88IV USB printer, we can print a test page to it from the Windows 10 machine. So I am wondering if anyone has run into this issue or has an idea of what it might be (configuration issue, not setup correctly, etc.)? I have attached some screenshots, any help is appreciated. Thank you. 

BuffaloScreenShot.JPG

NoPrinterError.JPG

*This post is locked for comments

I have the same question (0)
  • adam260 Profile Picture
    1,871 on at

    I've used the same printer but have the printer defined as OPOS with the settings below . I've also found out that if the device name does not match what is in windows it will not work correctly. 

    Printer: OPOS

    Device name: TM-T88V

    Make: Epson

    Model: TM-T88V M244A

    Description: Receipt printer

    We also found some issues when printing the x/z reports from within pos client getting cut off until we checked the "print binary conversion" checkbox on the screen you posted with this model of receipt printer

  • Community Member Profile Picture
    on at

    Thanks for the reply Adam. We have defined the printer by it's name in the OS and by device driver name in POS but neither seems to work. We are using the Windows Driver under the Printer drop down and have started looking at the OPOS driver. We are running Citrix XenDesktop from thin clients so I will have to try and figure out how we can map OPOS with our setup. Thanks again and will let you know if it works for us.

  • Suggested answer
    Community Member Profile Picture
    on at

    If you ever see this error message, it's do to a POS.Config.exe not being configured correctly. In our case we had a register defined in AX that was named Register 3, so it was assumed that the TerminalID in the config file was 000003. Register 3 was actually set to TerminalID 000004 so when it tried to print, we had set nothing up for 000003 hence the error we got.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans