I'm having an issue that is starting to stump me. Here's the run-down:
Two Windows Server 2008 R2 Terminal Servers (Farm configuration)
Printers are shared via Print Management on Print Server
When a user attempts to print to a Xerox Phaser 3300MFP printer, the print spooler will crash and generate the following error message under Application:
Faulting application name: spoolsv.exe, version: 6.1.7601.17777, time stamp: 0x4f35fc1d
Faulting module name: ssh1mdu.dll, version: 0.3.0.0, time stamp: 0x4a6d620c
Exception code: 0xc0000005
Fault offset: 0x000000000001f74c
Faulting process id: 0xb40
Faulting application start time: 0x01cda1121b54b499
Faulting application path: C:\Windows\System32\spoolsv.exe
Faulting module path: C:\Windows\system32\spool\DRIVERS\x64\3\ssh1mdu.dll
Report Id: 96b3cd8f0-0d61-11e2-b54c-0050569f3858
I have narrowed the problem down to the Xerox Phaser 3300MFP PCL 6 driver, but it is not affecting the other Terminal Server that we have. I also attempted to re-install the driver on the print server, but I have the most up-to-date one available. Removing the ssh1mdu.dll from the path specified in the error message and allowing it to rebuild itself does not help. When it does rebuild itself, I attempt to add the printer again using Add Printer, selecting Add a network, wireless, or Bluetooth printer it will then install the driver and give me another error message:
Connect to printer
Windows cannot connect to the printer.
Operation failed with error 0x000006be.
This will cause the print spooler to crash again.
Chris Roberts IT Professional CompTIA A+, MCTS: Windows 7, Configuration