I could not resist to solve the issue. You brought me too close to the solution. ;-) Actually it has been a permission issue of Windows 10's "Temp" folder. I had changed the system environment variables from the standard path to "C:\Temp" that I had manually created. However, this folder "C:\Temp" was missing "full control" permissions for the "Creator Owner" group. By adding those permissions the XPS printer queue now works.
I have no idea, best to contact Microsoft.
If it were me I would just ignore it though, V4 still isn't ready, it has more limitations than V3 requires additional apps to function properly and has literally no benefits unless you simply like the way they look. They are slower to spool and spool larger, they use more client resources, they tend to open slower due to relying on an app, they can't be used on older OS's, they are not consistent in design so people have to re-learn everything.
I see. You mentioned XPS, I was not aware of that. Speaking of XPS I tried the "Microsoft XPS Document Writer" for the first time - I had never used it before - and it failed. Actually with the same symptoms. So now I strongly suspect XPS to be the root cause of this as it is chained - as you described - to Type 4 drivers and causes them to fail.
I already tried to "Run the troubleshooter". Of course with no success, that would have been too easy. I also checked all the printer properties but nothing seems to be unusual.
You mentioned that I might have something unsupported. I use the printer in a small office environment with around 5 clients to access it. There is a Windows 2012 Server based AD, an Exchange Server 2013 that have not been significantly tinkered with in years. Same with group policies: all standard. There is no printer accounting used.
Do you have any more hints to narrow down this XPS issue?
The driver doesn't decide if data gets to the printer, it can only decide what gets there.
The port is the only thing needed to get something to the printer, you could use an HP Lazerjet 4 driver, the job will get there, albeit in BW and certainly won't work properly, but it will get there.
Since you have 2 PC's with the same issue, and are using the same driver everyone else is who has downloaded it since July when it was posted, it is pretty apparent that the issue is either in some way environmental, or you have something unsupported by the V4 print driver models, some examples of which are....
V4 drivers are always XPS based, they may output PS or PCL, but they begin in XPS, if something on the PC doesn't allow XPS in some way, they will not function.
Accounting is not supported, so if the printer has XSA/Auditron/Network accounting etc, they simply will not print.
Hi Joe, it is hard for me to debug the spooler/driver with just the event log entries I already posted. The printer does not support it either as it does not receive any data from the spooler. Maybe a “dev” driver could dump debug data...
You would have to call it in to Xerox, I would escalate it up internally if I could in some way replicate the issue, but it works fine on the 3 PC's I have with Windows 10
As this is obviously a driver issue, at least for the Type 4 ones, I am wondering where to address this? Are there any Xerox officials monitoring the forum?
In the print driver, at the ''Printer properties'', on ''Ports'' tab click on "Configure port" and change from RAW to LPR, at the Queue name write "lp" and be sure to unchecked "LPR Byte Counting Enable" and "SNMP Status Enabled".