PDF XChange Forum

Basically Print driver never shows up under "Devices and Printers" after installing ProV6.x64.msi - 6.0.317.1. Neither with 6.0.318.1.

- Installing on a Windows 2008 R2 terminal server.
- Version 5.x was installed prior to me installing v6. Since then I've uninstalled both v5 and v6 and reinstalled v6 (including reboots).

msiexec.exe /i ProV6x64.msi /l c:\tmp\install.log
install.log attached.

Please advice.

EDIT: Added install.log in zipped format.

Regards
Ronny Andreassen

Um, I don't see the attachment. Is it me or does the board block the file?

Try zipping the attachment before uploading it.

Zipped file incoming... I hope.

By doing a mild hack I got the print driver up and running.

Based on this guide: https://imagescience.com.au/knowledge/r ... on-windows I copied the relevant keys and values from a working computer to the server having problems.

I also had to copy a few files from C:\Program Files\Tracker Software\PDF-XChange 6\Drivers\x64 to C:\Windows\System32\ (PXC60pm.dll) and C:\Windows\System32\spool\drivers\x64\3 (PXC60f.dll and PXC60uif.dll).

Restart the server and printing to PDF worked.

I still don't know why the msi didn't install the driver though. Thoughts on that would be appreciated.

Regards
Ronny Andreassen

Hi Ronny,

I'll have one of our devs look at the log file today and in the meanwhile I am setting up a test R2k8 R2 RDS test install.

I hope to have something for you later today or tomorrow.

hth

Hi Ronny,

well my install went as expected and the printer was installed. Server 2008 R2 with the role of RDS server. We're waiting to hear what was in the log file.

regards

Hi again Ronny,

well the information we want is not in that log file. Can you look in your temp folder (%TEMP%) should be the place, for a log file called prnInstaller.log. It may still be hanging around after your failed install.

Without this log we will not be able to dig any deeper and I suspect, given this is on a Terminal Server, that you would prefer not to roll back to the state in which the issue was present?

We could provide a transform that you could apply to the MSI to enable the verbose logging for the printer we need, but as I say, that does require reproducing the issue...

Unfortunately %TEMP% is empty.

A rollback is not possible but I have three more servers (same image) that needs this update. If the install behaves the same on those I should be able to get my hands on that file.

A transform would be nice to have at hand if I encounter the same symptoms on those.

That's is encouraging Ronny, we may find out what is happening yet!

The transform is attached. Apply it and the logging options will be modified include what we need.

Look then for prnInstaller.log in %TEMP%