Color Access Group setting in GPD PCL6 V3.7.469.9.0 (5469.900.0.0) crash

[Fabio]

ah, i was told next spar was being released mid may

i also have an escalation about the nul: / nul port

will also be fixed in that spar :) 

[Joe Arseneau · Accepted solution]

Have you escalated this to 2nd level in Xerox yet?

I see one that is being worked by Xerox with spar ID CQGbl00875112.

I know that isn't likely to be you though as it is in the Philippines and is also for a re-branded printer (A Xerox sold via another company with custom badging)

I checked only minutes ago, the last spar was March 4 2016 version 5.469.10.5 and there isn't a fix, but a new spar is expected around the end of this month.

Try popping back on here around the first of May and I will check to see if I can get you a fixed copy. The next GPD release will likely have the fix applied, but that won't be until end of June to mid July.

And any time frame given is best guess type stuff, no guarantees.

[Andys]

Hi all.

Probably this is more like a bug report, but maybe anyone has a workaround...

I had two versions of GPD installed on my print servers - 5347.6 and latest 5469.9.

If I enable Color Access Group setting (Administration tab) in any print queue with newest driver (5469) and enter any group in Group field - then later opening this print queue's properties will always crash Print Management. The only way to get rid of setting is to delete the queue in question.

Event log shows this:

-------

Faulting application name: mmc.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc808 Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24 Exception code: 0xc0000374 Fault offset: 0x00000000000c4102 Faulting process id: 0xa90 Faulting application start time: 0x01d19491dc6de9bb Faulting application path: C:\Windows\system32\mmc.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: a8b890b7-07c7-11e6-8878-00155d021a0c

---------

With older driver version (5347.6) this does not happen, all settings work fine. Tested on a couple of another servers and on my workstation. Windows 2008r2, Windows 2012r2, Windows 7 x64 - on all of them crash was reproducible and unavoidable while using latest driver