drivers api on windows 2003 server

[gjw31]

I have developed an application that generates invoices and uses the pdf-xchange driver api to 'print' files to disk.

The application is written in C# in .NET 2.0. I have attached a class that encapsulates the api / printing process. This class is instantiated once per invoice run amd is closed at the end of the run.

The development environment is windows xp pro.

When I execute the app on the development machine it works perfectly (100's of invoices).

When executed on a windows 2003 server the print to disk process regularly 'hangs'. (The runtime distribution has been installed).
Occasionally the invoice print run completes successfuly; other times it hangs at different points in the invocing process.

Any advice on what might be happening and/or suggestions to debug this?

gjw

[Ivan - Tracker Software]

1. Which build of the driver do you use?
2. Please try to turn off option 'AutoUnload' into the driver (run pdfSaver4.exe with command line parameter /Show, and on Setting page uncheck "Auto Unload" option).

[gjw31]

as per pdfSaver the build is 0149.

Unfortunately I cannot use pdfsaver on the windows 2003 server until tomorrow (7:30pm here now).

Do pdfsaver settings affect use of the api in code? that is, does this establish default behaviour that may be overridden in code?

What is the expected result of changing the autounload setting?

gjw

[Ivan - Tracker Software]

pdfSaver is a part of PDF-XChange driver. Its task is to produce PDF files from the data generated by the driver.
Also, pdfSaver is a COM server for driver's ActiveX control.
Sometimes, when AutoUnload is turned on, it is possible that pdfSaver will unload itself when it should not do this.
We are working on fixing this, and turning off the AutoUnload feature is a workarround for now.