bb.donnay-software.com

Roger,

See below error. Happens now all the time, not sure why. Used to happen just once in a while.


-> VALTYPE: O CLASS: XbpFont
-> VALTYPE: O CLASS: XbpPresSpace oError:description : Parameter has a wrong data type
oError:filename :
oError:genCode : 2
oError:operation : :init
CALLSTACK:
Called from DC_FONTCONFIGURE(156)
Called from DC_PRINTER:SETFONT(2470)
Called from DC_PRINTER:INIT(836)
Called from DC_PRINTERON(3536)
Called from PRINTON(540)


Called from your standard prchoice. Last few have always been bullzip pdf file, but not sure if that is relative or not. Got 4 of these this morning. Asked a client the other day, she said it was bullzip and she rebooted and it worked fine. If I could figure out what causes it might be able to stop the errors.

Thanks.

Fred
Omni

This is a very difficult thing to try to debug.
I don't have any answers.

Fred,

This is an error I have received many times in the past.
It's happened while I was using win2pdf and it's happened while doing a straight print through express.

In other words, I can't pinpoint what causes it.
I tell the user(s) to reboot their computer and printer and the problem goes away.
In a week I'll get 5 to 10 errors and then a couple months will pass with nothing.

I agree with Roger that this is a very difficult problem to debug.

Bobby

SbDrakos wrote:This is an error I have received many times in the past.
Bobby

I'm shocked...

New york has bugs...
Bobby Drakos doesn't have bugs...

Ok, this one is even more weird. Same type of error.


ERROR OBJECT:
oError:args :
-> VALTYPE: O CLASS: XbpPrinter
oError:description : Numeric overflow
oError:filename :
oError:genCode : 10
oError:operation : :endDoc
CALLSTACK:
Called from DC_PRINTER:DESTROY(1469)
Called from DC_PRINTEROXX(1163)
Called from PRINTOFF(591)


How can you have a numeric overflow when killing a print job? This user received this message 3 times within 30 minutes on the same print job that was 4 pages. We connected and printed it fine.

have you replaced their printer driver ?

I have often suspected that there are flaws in the XbpPrinter() class because such errors cannot be blamed on eXpress++ code.