Hi,
we have problems with splwow64.exe crashing on our 64-bit Terminalservers in some cases when printing.
Environment:
We are running several Terminalservers with Windows 2008 R2 on Citrix XenApp 6.5 R01. The servers are provisioned, means that they are in a defined status that comes back every time they are rebooted. Reboot takes place avery night.
All our printers are networkprinters and newly mapped to the user-sessions on the XenApp Terminalservers when logging on (as the Terminalservers are booted every night).
The printserver is also running Windows 2008 R2 with the latest drivers for all printer models.
The XenApp Terminalservers are provided with the printer drivers via FileRepository (pnputil.exe) from the printserver to make sure we have the same basement data. Furthermore we install/connect each printermodel out of this FileRepository so that all drivers are already installed when the user logs on.
Problem:
Some of our users that are using printers from Kyocera Mita have problems with a crashing splwow64.exe.
Error Message (German OS):
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 11.03.2013
Time: 11:57:55
User: N/A
Computer: mmwxa2000
Description:
Name der fehlerhaften Anwendung: splwow64.exe, Version: 6.1.7601.17777, Zeitstempel: 0x4f35fbfe
Name des fehlerhaften Moduls: KMUU60MC.DLL, Version: 6.0.22.12, Zeitstempel: 0x5078a4ed
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000011c11d
ID des fehlerhaften Prozesses: 0x5a14
Startzeit der fehlerhaften Anwendung: 0x01ce1e4718573b32
Pfad der fehlerhaften Anwendung: C:\Windows\splwow64.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\spool\DRIVERS\x64\3\KMUU60MC.DLL
Berichtskennung: 8698afbc-8a3a-11e2-abe4-56c665522b83
The error message tells me that the driver config-file that is loaded in the usersession (to show the user the driversettings in "printer->printersetting") causes the splwow64.exe to crash. This happens in different situations: printing a PDF,
just opening an Excel-file, opening a print-preview a.s.o.
Interessting to see is that in the printer->printersettings the definition that should be taken from the printserver is NOT taken at this moment!
What we did so far:
- We testet different driver Versions from Kyocera and also had a Kyocera technichan here. -> all the same result
- We checkt the way of installation the drivers on the terminalservers and optimized it.
- for quick solution we delete the causing printer in the usersession and reconnect it via dialog. Now the printersetting are again correctly taken from the printserver and printing is possible without failure.
I know this ist a very complex thread and most of you will tell me it is a problem of the printerdriver. But the case is that only few users have this problem. So it seams to be nothing general but something depending on the driverprovinding in the usersession.
What in hell do I not see????!?!?!?
Thanks in advance!
Nadine