cancel
Showing results for 
Search instead for 
Did you mean: 
GeneMMO New Member
New Member

xerox colorqube 9303 PCL errors

We are using GPD PCL driver  5.404.8  and getting frequent print file corruption problems.  Causing printer to reboot with PCL error.

I have to do a software reset to clear out the bad print jobs.  This happens every couple days.  User are on Windows 7.

Any ideas?

0 Kudos
3 Replies
Highlighted
Analyst Nation Moderator Joe053204-hcl
Analyst Nation Moderator

Re: xerox colorqube 9303 PCL errors

I would suggest the PS driver, but in any case, is this multiple PC's with standalone local driver installs? Seems like it would be either 1 PC or many using a shared driver. If a shared driver go to server, if a single PC go there and do a complete and total removal, then reinstall.

 

Removing the Xerox Print Driver from Standalone or Cluster Node

 

Recommendation: Backup Windows Server, System State, etc. along with the Registry before continuing.

 

Where to Start:

 

  1. Open Print Management (local) and delete Xerox from ALL Printers List
  2. Select ‘Drivers’ and delete all XEROX Drivers
  3. Select ‘Ports’ and delete all ports being used by Xerox Drivers/Printers
  4. Check ALL locations besides ‘Local’ and validate all Xerox data has been removed

 

The following steps are performed within Windows Explorer

 

  1. Within the \Windows\system32\spool\drivers\w32x86\ directory:
  • Remove all Xerox folders, if more than one exists.

 

  1. Within the \Windows\system32\spool\drivers\w32x86\3 directory:
  • Remove the Xerox folder
  • Remove the X2*, xuniv*, XLX*, and *.bud files

Note: Do not delete the xlibeay.dll file

 

  1. Within the \Windows\system32\spool\drivers\w32x86\3\temp directory:
  • Delete all x2* files

 

  1. Within the \Windows\system32\spool\drivers\w32x86\2 directory: (if location exists)
  • Remove all x2* and xuniv*

Note: Do not delete the xlibeay.dll file

 

  1. Within the \Windows\system32\spool\drivers\w32x86\2\temp directory: (if location exists)
  • Delete all x2* files

 

  1. Within the \Windows\system32\spool\drivers\x64\3 directory: (if location exists)
  • Remove the Xerox folder
  • Remove the X2*, xuniv*, XLX*, and *.bud files

Note: Do not delete the xlibeay.dll file

 

  1. Within the \Windows\system32\spool\drivers\x64\3\temp directory:
  • Delete all x2* files

 

  1. Within the \Windows\system32\spool\prtprocs\w32x86 directory:
  • Delete x* files (xprint5.dll, x5pp.dll, etc)

Note: If a file cannot be removed, continue to the next step and verify that the file has been removed after the end of this procedure.

 

  1. Within the \Windows\system32\spool\prtprocs\x64 directory:
  • Delete x* files (xprint5.dll, x5pp.dll, etc)

(If a file cannot be removed, continue to the next step and verify that the file has been removed after the end of this procedure.)

 

  1. Within the \Windows\system32\spool\drivers\BIDI directory:
  • Delete the Xerox directory, if it exists.

 

  1. Within the \Windows\system32\spool\drivers\Color directory:
  • Delete the Xerox directory, if it exists.
  1. Remove any ‘x2’ or ‘Xerox’ from the “DriverStore” directory on the Windows OS.
  2. Remove the *.if files from the c:\windows\INF Directory (oemsetup##.txt files. Delete the corresponding PNF file.
  3. Stop and restart the print spooler. This can be done by selecting Administrative Tools à Services à and selecting Print Spooler from the list of services. Proceed by stopping and restarting the service.
  4. Once Complete, PLEASE check the node directories as well to verify no Xerox data is stored within them.

 

  1. Again, please verify a BACKUP of the Windows Registry has been saved. If not, please do so now.
  2. Select the round Windows Start button and type ‘regedit’ in the ‘Search programs and files’ field and hit Enter.

NOTE: If any software packages like ‘Xerox Font Manager are installed – do not touch them!

  1. Within the registry go to the stated directories and perform the actions listed.

HKEY_CURRENT_USER\Printers

  • Look through each directory and delete all Xerox entries

 

HKEY_CURRENT_USER\Software\

  • Delete ‘Xerox’ folder

 

HKEY_LOCAL_MACHINE\SOFTWARE\

  • Delete the ‘Xerox’ directory

 

HKEY_LOCAL_MACHINE\SYSTEM

  • Under this folder there may be a number of ControlSet directories. Within each ControlSet directory, including the Current ControlSet folder, follow the paths listed below and delete the Xerox printer entries for all ControlSets including current ControlSets.

 

…\ControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-3

(also check for a Version-2 folder)

…\Control\Print\Environments\Windows NT x86\Print Processors

…\Control\Print\Environments\Windows x64\Drivers\Version-3

(also check for a Version-2 folder)

…\Control\Print\Environments\Windows x64\Print Processors

 

HKEY_USERS\.DEFAULT\Printer

  • Within each folder delete any Xerox entries that exist.

 

HKEY_USERS\.DEFAULT\Software

  • Delete the Xerox folder
  • In other “ S-1-*** ” folders look within the Software folder and delete the Xerox folders.

 

Special Note: The printer ports are recommended to be removed when cleaning the Xerox data completely from the REGISTRY.

HKEY_LOCAL_MACHINE\SYSTEM

  • Under this folder there may be a number of Control Set directories. Using the examples below, delete the ports for the Xerox printer entries for all Control Sets.

 

…\ControlSet001\Control\Print\Monitors\Standard TCP/IP Port\Ports

…\ControlSet001\Control\Print\Printers

…\ControlSet002\Control\Print\Monitors\Standard TCP/IP Port\Ports

…\ControlSet002\Control\Print\Printers

…\CurrentControl\Control\Print\Monitors\Standard TCP/IP Port\Ports

…\CurrentControl\Control\Print\Printers

…\CurrentControlSet\Control\Print\Monitors\Standard TCP/IP Port\Ports

…\CurrentControlSet\Control\Print\Printers                   

  1. Once complete, select ‘Computer’ and perform search for ‘Xerox’ and remove any related items. (fax phone book, printers, ports, driver files, etc.)
  2. Close the registry.
  3. Empty the Windows recycle bin
  4. Check any files you could not delete during the steps above. If you still can’t delete them reboot and try again.
  • Once you are able to delete the file empty the recycle bin again

 

  1. Stop and restart the print spooler
  2. Check in ‘Printer Properties’ under the Advanced tab and the ‘Print Processor’ button to see if the Xerox print processor is gone. Please do the same for Printers, Ports & Drivers within Print Management
Please be sure to select "Accept Solution" and or select the thumbs up icon to enter Kudos for posts that resolve your issues. Your feedback counts!

Joe
GeneMMO New Member
New Member

Re: xerox colorqube 9303 PCL errors

Joe,

Thanks for the feedback.  I should have mentioned that drivers are on a shared print server.  Most of our fleet is ColorQube 9203 devices.  We have a few 9303 models,  and are having lots of errors on a specific CQ9303 device.  So do I have the server guys remove and re-install just that print queue from the server?  Also, can we run PS and PCL drivers from the same print server?

Gene

0 Kudos
Analyst Nation Moderator Joe053204-hcl
Analyst Nation Moderator

Re: xerox colorqube 9303 PCL errors

Myself personally, I would wipe all drivers and queues in entirety that point at Xerox devices, especially when using the Global drivers.

My reasoning's for that are that the Global driver shares many components when installed on one PC but to many devices, it won't overwrite drivers and files that are already in use on another device. This gets tricky when 2 machines share some files, a modification to one may negatively affect the other. I'm no driver expert honestly, I have nothing to do with development, but I see a lot of issues that appear to be caused by that. You may get away with just removing the one install via right-click > remove device, you may not. But since we have no idea what has caused the issue, and since the IT guy already has to take down the queue, I would go all out and do it all.

 

Obviously its all up to you and the Server guy, and since I know nothing of your environment, there is a massive difference in justification for a kill all approach on a server running a home office and a cluster server running a Hospital.

 

 

Please be sure to select "Accept Solution" and or select the thumbs up icon to enter Kudos for posts that resolve your issues. Your feedback counts!

Joe
0 Kudos