We have problems with the the phasermatch software and our Phaser 7800GX.
Our clients are win7 x64 with Phaser 7800 PS (3) x64 drivers installed (v 5.239.5). They are connected via TCP/IP. Printing itself is without problems (office, test page etc.)
When we try to calibrate the printer we can not choose the printer - the drop down for the installed printers is empty.
if we install PCL drivers on top, they show in profile setting - not so the ps driver that's needed for calibration of the printer itself.
whats wrong? anyone has some ideas? that would be highly appreciated.
Solved! Go to Solution.
Any chance you locked down SNMP on the printer? or the LAN?
Is it the latest version?
Thank you for your reply!
SNMP was not configured for this printer. I've tried - but it does'nt make any difference.
I've tried both the supplied version of PhaserMatch and PS(3) drivers and the newest available from Xerox's website. 'Cause we're using UAC i even tried using the local administrator account instead of the domain user account. Printing itself works fine. It's only PhaserMatch giving me headaches.
It's kind of weird, that i dont even see the printer in profile settings, while i see the other printers configured on this system - even the PCL-driver versions of the very same Phaser7800. Offcourse they dont work for calibrating the printer.
I've tried using procmon to investigate further. There is a logfile "generallogger.txt". It shows:
[Di 5. Dez 08:54:53 2017] INFO 0 PrinterName: Phaser 7800DN DIN A3 PS
[Di 5. Dez 08:54:53 2017] INFO 0 DriverName: Xerox Phaser 7800GX PS
[Di 5. Dez 08:54:53 2017] INFO Printer: Phaser 7800DN DIN A3 PS -> IP address: xx.xx.xx.xx (insert real ip here ;) )
[Di 5. Dez 08:54:53 2017] INFO Phaser 7800DN DIN A3 PS is a cmyk printer but not using a postscript driver: Xerox Phaser 7800GX PS
[Di 5. Dez 08:54:53 2017] INFO 1 PrinterName: Microsoft XPS Document Writer
[Di 5. Dez 08:54:53 2017] INFO 1 DriverName: Microsoft XPS Document Writer
so the printer is found but PhaserMatch rejects the driver??
For anyone interested... I finally found out what happend. There was a problem with the devicelock-service on the computer. Without DL (or other settings) everything works fine.