Huge Crystal Report print job halts after ENDDOCPRE

trumpetinc · Post by **trumpetinc** » Thu Oct 20 2005

We have a 20,000 page Crystal Report that we are printing to the Amyuni driver. Everything proceeds fine, until the very end of the job. We receive the ENDDOCPRE event message, but we never receive the ENDDOCPOST message.

The PDF file that is generated is valid PDF, and contains all pages, but the event is never fired.

If we run smaller jobs (i.e. the first 100 pages of this report), it works perfectly and we receive all messages.

Any ideas?

Thanks,

- K

Joan · Post by **Joan** » Mon Oct 24 2005

Hello,

Between EndDocPre and EndDocPost CDIntf doesn't do any processing it is mainly the OS and your application that do their own processing.

Please tell me what you are doing when catching the EndDocPre() Event.

Also please tell me which version of the PDF Converter you are using and wether you tried the latest version 2.50 (If not please try 250 and check if you will still get the same issue).

Thanks.

trumpetinc · Post by **trumpetinc** » Mon Oct 24 2005

On receipt of DOCUMENTEVENT_ENDDOCPRE, Our app sets a DWORD variable to 1, then returns DOCUMENTEVENT_SUCCESS (not much that can go wrong there - especially given that everything works flawlessly with smaller print jobs from CR).

I'll try this with the latest 2.5 and let you know if that fixes it.

Thanks,

- K

Joan wrote:Hello,

Between EndDocPre and EndDocPost CDIntf doesn't do any processing it is mainly the OS and your application that do their own processing.

Please tell me what you are doing when catching the EndDocPre() Event.

Also please tell me which version of the PDF Converter you are using and wether you tried the latest version 2.50 (If not please try 250 and check if you will still get the same issue).

Thanks.

trumpetinc · Post by **trumpetinc** » Mon Oct 24 2005

OK - no difference, even with the very latest 2.5 code.

This may be a CR issue - we've had problems with about half of the PDF print drivers we've tried... It would be nice if there was a workaround, though...

Any ideas on what exactly happens between ENDDOCPRE and ENDDOCPOST ? Is it just a call to close the printer context handle, or is there anything else going on that would actually interact with the print job source that could cause ENDDOCPOST to never get sent?

Thanks,

- K

trumpetinc wrote:On receipt of DOCUMENTEVENT_ENDDOCPRE, Our app sets a DWORD variable to 1, then returns DOCUMENTEVENT_SUCCESS (not much that can go wrong there - especially given that everything works flawlessly with smaller print jobs from CR).

I'll try this with the latest 2.5 and let you know if that fixes it.

Thanks,

- K

Joan wrote:Hello,

Between EndDocPre and EndDocPost CDIntf doesn't do any processing it is mainly the OS and your application that do their own processing.

Please tell me what you are doing when catching the EndDocPre() Event.

Also please tell me which version of the PDF Converter you are using and wether you tried the latest version 2.50 (If not please try 250 and check if you will still get the same issue).

Thanks.

Joan · Post by **Joan** » Wed Oct 26 2005

Hello

Well, there is not much going on in our EndDoc. We finalize the document. If you is saying that the document is good and viewable that means our EndDoc was successful. Here are the series of events:

1- The application (in this case CR) calls an end doc GDI api
2- EndDocPre event is fired
3- our EndDoc gets called by GDI, we finalize the document
4- EndDocPost event is fired

From what you are describing, I believe there is a crash somewhere. Might be in CR or in our EndDoc
To debug this issue we need a case where we can reproduce it. If you can please send us a sample where we can reproduce this issue to support@amyuni.com

trumpetinc · Post by **trumpetinc** » Wed Oct 26 2005

Source data for the print job is 180 MB, and contains highly sensitive information. Can we do anything with logging code to try to bracket the problem, or at least ensure that it is not happening in the amyuni code?

A log file, or OutputDebugString would work fine for us (we can run DebugView while the job is running).

Thanks,

- K

Joan wrote:Hello

Well, there is not much going on in our EndDoc. We finalize the document. If you is saying that the document is good and viewable that means our EndDoc was successful. Here are the series of events:

1- The application (in this case CR) calls an end doc GDI api
2- EndDocPre event is fired
3- our EndDoc gets called by GDI, we finalize the document
4- EndDocPost event is fired

From what you are describing, I believe there is a crash somewhere. Might be in CR or in our EndDoc
To debug this issue we need a case where we can reproduce it. If you can please send us a sample where we can reproduce this issue to support@amyuni.com

Joan · Post by **Joan** » Thu Oct 27 2005

Hello,

In this case please contact support@amyuni.com to check if our Technical Support Team can send you a debug version of the product that enables you to see when precisely the crash is occuring