I've noticed a strange behaviour in one of our installations.
The setup is as follows:
- MS Windows Server 2003
- J2EE Application under JBoss 4.2.3 running as a Windows Service
- PDF-XChange Viewer installed under Windows.
The command line is something like "<path-2-pdfviewer-folder>/PDFXCViewer/PDFXCview.exe" /printto "printer name" "pdf-file"
The result is that a PDF-XChange Viewer process is created and the pdf file is blocked, probaly by the PDF-XChange Viewer process.
Unfortunately the file is never printed and the PDF-XChange Viewer never terminates until killing the process e.g. using the Windows Taskmanager.
Really strange is, that the same setup is running without any problems at other locations.
I know, this setup is probaly at little bit unsual for using PDF-XChange Viewer, but it is working very well for us except this single installation.
It would be really fantastic, if someone could point me in the right direction for solving this problem.
Thanks in advance, Torsten