03-19-2018 09:54 AM
Hello, I'm having a strange issue installing a printer and hoping someone can shed some light. Let me first set the stage:
1. Printer is a Color 560
2. Driver being used is PS Global Print Driver 5.585.13.0
3. Printer is setup on two Windows 2012 R2 servers and shared
The reason it's installed on the second server is due to the issue, which I will describe below.
When trying to install the printer from the first server, it will error out with a message saying "A policy is in effect on your computer which prevents you from connecting to this print queue." This is accompanied by event IDs 600 and 870. When installing the same printer from the second server, it will install without issues. We've been through the GPO's and there isn't anything there that is further reinforced by the fact that the printer can be installed from the other server without issues.
I examined the setupapi.dev.log and found something that could point to the issue and here's what I found:
- When installing from the first server, it seems to be importing the driver package from ntprint.inf. There is a line towards the end that says "Failed to verify file 'UNIRES.DLL' against catalog. Catalog did not contain file hash. File is likely corrupt or victim of tampering."
- When installing from the second server, it seems to be importing the driver package from x3univp.inf and completes without issues.
Any ideas why the difference?
Thank in advance!
03-19-2018 12:53 PM
Seems like the 2nd server is using the PCL instead of the PS, which in most cases is the correct choice for the 560.
The 560 doesn't natively support Postscript, it is built on PCL, but a purchasable upgrade can be obtained to add PS to the device. You can verify if it has the PS kit on the Configuration report.
Even when it does support PS, the PCL tends to perform better.
The Global Print driver is not recommended, the Native driver is much better in the case of any printer made by FujiXerox (The 560 is them). The GPD drivers will work, but they are not nearly as stable in day to day use in my experience.
As for the access rights stuff, no idea, but since it is a queue problem, simply bypass the driver installer and install it manually (Use Devices and Printers and not the Print Manager) and create the port manually (Standard TCP/IP>LPR and neither byte counting nor SNMP should be checked)
03-19-2018 01:31 PM
Hi Joe, thanks for the reply. Both servers have the PS driver and the same versions. I think the queue message is just a generic message. What I'm trying to determine is why it's looking at different inf files even though they have been setup identically on both servers?
03-19-2018 01:50 PM
If everything was actually the same, the same thing would happen on both.
Something is clearly different and it is impossible for me to state what it is (Just guess), because I have nothing to do with either server.
All I can do, and did, is give a few pointers of what to try.
If you want concrete troubleshooting, call Xerox and have a Analyst visit set up so someone will be onsite and can troubleshoot the issue on location.
03-19-2018 04:05 PM
That's exactly what I'm trying to find out...what's different. Was hoping someon would know why it would download a different driver in each case when the same version is installed on both server. I will reach out to Xerox.