micros autosequence reports failing

[jd11111]

been trying to figure this one out for a while...

In Micros (v 4.7) on ws4lx, the users lose the ability to print a report (using autosequences). The terminal reads "printing report..." but nothing happens. This seems to be limited to about half of the terminals and is temporarily resolved by rebooting the terminal or the printer.

The error in the 3700d Log is:

Wed Feb 02 08:30:40 2011 | DineB | PrintControllerCE | 0 | Thread [06637962]: Failed to open device printer [ DineB Ptr_Dten_18][00000010] |
Wed Feb 02 08:30:40 2011 | DineB | PrintControllerCE | 0 | Printer configuration failed - Job [MICROS Task 61566 Gen 0] Printer [ DineB Ptr_Dten_18] |

 

[DrZogg]

Hi,
just some troubleshooting places you have probably checked, but do anyway:

1. Check the Autosequence and check the parameters being sent (SRV period, RVC Num, that kind of thing and that they are legitimate). Make sure there is no "override printer" selected here.
2. In WORKSTATIONS check the report printer selected for the workstation (check the REPORTS printer selection)
3. In Device table, check the printer that is correct, and is correctly "attached" in the device table
4. Try setting the printer to one on another WS (reload DB to update the MDSPRINTERS.xml.
5. Read the MSDPRINTERS.xml and confirm the one in the WS4 ETC is correct and the same as the one on the host. Juct check (while on this) that there is no out of date copy held on the server in \CAL\WS4LX\ETC or similar, as contents of this get pushed out(and never updated as the current one is always in \COMMON\ETC

My guess is there is an out of date XML file in the \ETC on the WS

 

[jd11111]

thanks...I've already done 1,2 & 3.

I'll try 4 and 5, but I have already wiped the compact flash on all terminals and ran CAL again. This should have taken care of any issues with MDSPrinters.xml.

 

[DrZogg]

And also look in the NETWORK NODE table and check the NAME & IP.
Just check the NAME & IP that are actually configured on the client.

I read the log as the Workstation is called DineB , there is a printer attached that is # 18 in the Device Table (DTEN stands for Device Table Entry), and 00000010 will be something relevant to Printer type or maybe an IDN ID. Cant say that one, but it will make sense to you.