PDF XChange Forum

Could you please tell me the correct install procedure for PDF Xchange 4 Pro when run by thin clients running on a Windows 2008 Server (x64) with Terminal Services.

Currently our users each run the following command line:

PDFX4SA_sm.exe /VERYSILENT /NORESTART /COMPONENTS="pdfSaver,PDF-XChangedriver, Help,Languagess" /DIR="C:\Program Files\PDF-XChange 4 Pro\"

I question this because the server is showing two problems:

1. The server becomes unresponsive to the point where it has to be rebooted.

2. The print spooler will not start and an event 1000 is shown in the application event log:

Faulting application spoolsv.exe, version 6.0.6002.18005, time stamp 0x49e03626, faulting module pxc40pm.dll, version 4.0.161.0, time stamp 0x49f73748, exception code 0xc00000fd, fault offset 0x0000000000008d37, process id 0x2fc0, application start time 0x01ca2587cc7d4f05.

If we uninstall the PDF-Xchange 4 software the server runs without a problem. Fat clients installing the same software are also OK. We are currently using build 4.0.165.0.

Hi,

a couple of things -

1: a reboot would usually be required on first installing an update to PDF-XChange or the changes will not be effected until such a restart has occurred - this would not be required if this is a 'virgin' Server install.

2: On installing try also using the switch : /AutoUnload:nn - where 'nn' is a timing value in minutes to unload PDFSaver after the last job has completed and free the memory used. I would set this at 1 minute and see how/if this helps.

Hi steve,

just wondering why you have users installing on a terminals server. While I've not used 2008 in production, I have 2003 and typically Terminal Services applications are installed once by the administrator using the "change use /install" command. It seems from my cursory reading that 2008 employs the same methodology.

http://technet.microsoft.com/en-gb/libr ... S.10).aspx
http://www.techotopia.com/index.php/Ins ... l_Services

Have I missed something?

I found a way to use the version 3 driver on x64 so we have given up on the version 4 driver. Search the message boards for ExtEscape for more info.

Hi Steven,

pleased you got there - however we also have corrected some issues found on Windows Server(xxxx) installations with 64 bit installs in our latest releases for future reference.

What would those fixes be? There's nothing install related in the revision history.

There are Win 64 issues resolved which could be responsible and therefore I felt it might be useful to advise ...

Are you able to provide any details?

Version history info is provided here for the non Viewer products :

https://www.pdf-xchange.com/home/pr ... onHistory/

and for the Viewer here :

https://www.pdf-xchange.com/home/pr ... r/history/

I appreciate you're trying to help John but I'm looking for more detailed information. The only x64 fix listed doesn't give any details about what happened before so I've no idea if that will help with the problem I experienced. For example we tried to re-install version 4 (4.0.165.0) today onto a 2008 server with terminal services enabled and the print spooler kept crashing. I upgraded to 4.0.170.0 and so far that seems stable but it won't get any real use until tomorrow. Are there any specific fixes that affected the print spooler?

And honestly Steve - I dont know the specific answer either ...

The only way to check for sure is by downloading and installing the latest build and testing (as you are) - and if this is not resolved - then we need to investigate further and possibly provide you with a specail debug build - or ask you for a sample app (both source and compiled) to allow us to reproduce - as we believe we have all 64 bit issues resolved and if this is still a problem - we would very much like to get to the bottom of with you - but we will need assistance to do so.

Thanks for the info John, I'll carry on running the latest version and get back to you if we experience any further issues.

appreciate your patience and assistance Steve.

The driver has started acting up again in that the spooler service refused to start wiping out all printers on the server. We had to uninstall the driver before the spooler would start working again. The following error was reported in the Windows Application Event Log every time the spooler service tried to start:

Faulting application spoolsv.exe, version 6.0.6002.18005, time stamp 0x49e03626, faulting module pxc40pm.dll, version 4.0.170.0, time stamp 0x4af7f64c, exception code 0xc00000fd, fault offset 0x0000000000008d37, process id 0x6a00, application start time 0x01ca74eb96aee637.

All entries report the same fault offset.

Do you have any suggestions?

Hi Steve,

You have started a separate topic on your last issue: https://forum.pdf-xchange.com/ ... =39&t=7531
so lets keep the discussion there and leave this one to go down and eventually be used as reference for install procedures on WIN 2008 TS only

Regards,
Stefan