MICROS 3700 Reports Printing Jibberish 1

[themicrosman]

I have a Micros 3700 system that is printing jibberish when I try to print one of our 40 Col custom reports from the workstation. All that comes out on the printer is something like this. ÐÏࡱ (That's what prints exactly in the journal file also). These reports have worked forever and never had a problem. I even took a copy of the report and tried it on another 3700 system and it works. Has anyone ever seen that or have any idea what I could try to correct it? Thanks

 

[Wildbar]

I assume you have tried rebooting your system? What happened when you print the 40 column report from the server?

 

[themicrosman]

Yes a reboot was the first thing I tried. When I run the report from the server (in workstation mode) I get the same thing. I don't have a receipt printer attached to the server, but when I check the journal file it has the same jibberish.

 

[themicrosman]

I should also probably mention that the report prints fine when manually printed thru the server using autosequences and reports. It only seems to have an issue from the workstations.

 

[DJensen999]

Workstation type(s) and Res release at the location in question?

I think I saw a few caveats about report printing from WINCE-based workstations near the end of 4.x and into the 5.x releases, would need to dig.

 

[themicrosman]

Running Res 4.9. Server is Windows XP. Workstation types I am checking on.

 

[themicrosman]

Djensen- They are running Workstation 4LX

 

[DJensen999]

I've actually never touched a WS4LX... but my initial reaction would be to check for a WS4LX Platform update if available and do a CAL reload.

The 4.9 release notes I dug through show that reports might not print at all from WINCE-based units on earlier MR versions, but only when used with a SRM.

 

[pmegan]

Are you using a "print to pdf" autosequence anywhere? I've seen this happen when the u2ftext.dll isn't set back to the text library.

The print libraries are in C:\program files\common files\crystal decisions\2.0\binThere are a few dll's that you can swap around: u2ftext.dll (text), crxf_pdf.dll (pdf), crxf_xls (excel) and u2fsepv.dll (csv)
With a print to pdf, the following ususally happens:
[ol 1]
[li]u2ftext.dll is copied with a dummy name like u2ftext.org and the original deleted[/li]
[li]crxf_pdf.dll is copied as u2ftext.dll, effectively overriding the text printing[/li]
[li]reports are printing, and the overridden library prints them to pdf files[/li]
[li]the current u2ftext.dll is then deleted and the dummy is copied back in with that name, restoring text printing[/li]
[/ol]

The problem with this is that the workstations also use u2ftext.dll to print reports, so if the pdf version isn't deleted and the text version restored, you get gibberish at the report printers.

 

[themicrosman]

pmegan you were spot on with that one. The problem was definitely with that .dll file for whatever reason. Copying a new one in resolved the issue. I am grateful.

 

[pmegan]

Good deal. Glad I could help.