PDF Converter debug & log for failed to send via SMTP

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
xenonsky
Posts: 2
Joined: Tue Nov 06 2007

PDF Converter debug & log for failed to send via SMTP

Post by xenonsky »

Greeting,

Does anyone know any advanced debugging or logging feature is available for the PDF converter? Don't see anything or this sort in the configuration. I'm running the latest demo version on Win2K3 TS server with Citrix installed.

Users suppose to use the PDF to SMTP feature but nothing got email out when test print from Notepad or WordPad. This only happens for users from one GEO region in Citrix session only. The same users can print PDF to SMTP in RDP session to the same SMTP server to email out. The same user can print PDF to SMTP just fine logging on from another GEO in both RDP and Citrix session without problem. So issue only limited to users logging on to Citrix session from one particular GEO only.

I've managed to narrowed via network trace and determined that when Amyuni PDF converter failed to send PDF via SMTP, my SMTP server log will stop short at the server not sending the SMTP "Data" command and just stop there, so the email never got sent and the PDF was never attached to email.

Nothing get logged in event log on Win2K3, and no visible error to users either.

Is there any advanced debugging or logging I can enable for the PDF converter so that I know exactly what the PDF converter is doing or not doing when communicating with my SMTP server?

I've tested with different SMTP server as well.

Appreciate any help or advice on this.

Thanks,

Bill
xenonsky
Posts: 2
Joined: Tue Nov 06 2007

Post by xenonsky »

Well I finally resolved this issue. For future reference the problem is due to a bug in the PDF Converter where the SMTP feature will fail to send email properly when the client or session time zone is GMT 0 (same problem in RDP or Citrix session).

Changed time zone to anything but GMT 0 worked around this bug.

Xenonsky
Post Reply