“Printer not activated, error code -30” only when converting

The Amyuni PDF Converter is our Printer Driver that enables you to convert any documents to PDF format. If you have any questions about installing and using the Amyuni PDF Converter please post them here.
Post Reply
BenR
Posts: 1
Joined: Thu Apr 13 2006

“Printer not activated, error code -30” only when converting

Post by BenR »

We are receiving the “Printer not activated, error code -30” when using PDF Converter. We’ve been using version 2.50a for several months without issue and only started receiving this error when output started to grow significantly in size. I can’t be sure that’s what is causing it, but I can run reports that are smaller and it will work fine, but when generating large (>100 pages) output that takes a long time (>20 seconds) to produce I receive this error.

I am not using the developer version. I’ll try to describe how the driver is being called programmatically.

1. During our app's startup procedures we call CDIntEX.CDIntfEXCLass() then PDFDriverInit(…) and EnablePrinter(<our license info>)

2. Immediately before generating print output we call DriverInit(…), SetDefaultPrint(), FileNameOptionsEx = NO_PROMPT + USE_FILE_NAME + CONCATENATE, EnablePrinter(<our license info>)

3. After printing is complete we call FileNameOptionsEx = 0, DriverEnd()

I’ve tried upgrading to version 2.50g with no effect. I’m wondering if there is another way we should approach this, or if using the managed version of CDIntF would help at all (I’m not sure it currently supports everything we need, but it looks like it).

Any ideas?
Joan
Amyuni Team
Posts: 2799
Joined: Wed Sep 11 2002
Contact:

Post by Joan »

Hello,

This is not related to the version of the PDF Converter or CDIntf you are using.

The is related to the time printing takes.

I suggest that you try to call EnablePrinter() when catching the EnablePre() event fired by the driver.

If this didn't help, you need to contact our Support Team support@amyuni.com and check if you can get an activation code with a longer activation time.

I checked the steps you are following and i don't beleive you need to call DriverInit right before printing, it is advisable to call this function once when launching your application and not each time your print. This can apply to SetDefaultPrinter too.


Hope this helps.
Post Reply