Printer is not accepting job in Smart Client Servoy 5.1

Classic Servoy
1

Hi all,
I’m trying to print a form in smart client.
I do a print preview of the form, so far so good. Then get to printer popup to choose the printer and its configurations.
In the status lbl I get “Printer is not accepting job.”
If I try to print anyway, I get a exception in Servoy with the same message.
I find this very weird as I can use the printer for everything else.
I’ve been searching for some reference of this error in the web and found a hint it might be a java problem or a printer driver problem.

I already have the last version of java runtime and in the experience of other who had the same problem when running java apps, upgrading the priter drivers did not solve the problem.

I found some solutions to this problem, but they did not work in every case and implied almost hacking the java apps with some code, wich i’m not willing to do (or even sure it’s possible) in Servoy.

Does anyone please have a solution to this big problem??
At the moment it is imposible for my apps to print as web printing has a bug in Servoy 5.1 and does not work, and this problem for smart just showed up.
I’m really stuck with this.

I’m using Servoy 5.1 and Windows XP SP3. The printer is a OKI C3400 with network connection.

Thanks for the help.

2

I am also experiencing this problem with Servoy v5.0.1 and v5.1.
Would be grateful for any suggestion.

3

Are you using the system print dialog? (useSystemPrintDialog Servoy property set to true - or under edit/preferences)
If so, doesn’t the status show a more detailed reason for “Printer is not accepting job”? Like “out of paper” for example.

Here is a bug report that looks similar to your problem (maybe you already saw it):
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6525150

Did you also try deleting/recreating the printer in Windows and filling all trays of the printer (if applicable to your printer) to see if that fixes the problem?
I see the bug status is “fixed”, but other java users reported as well that the problem still exists.