As usual printing is still an issue with Remote Desktop Services and even the blue screens (BSOD) are back! So make sure you read the information here.
Possible blue screen when printing out of a 32bit application
With a bad printer driver you might end up with a blue screen when printing out of a 32bit application using Remote Desktop Services and Server 2008 R2 with or without SP1.
When printing from a 32bit application, then the print output must be "translated" in order to be printed out by the 64bit printer driver. The "translation" is done by a process called splwow64.exe. In case of a "bad" printer driver (happened so far with Xerox and HP) the driver corrupts the memory of the splwow64.exe process.
The user will get the following popup error message:
"Printer Driver Host for 32bit applications doesn't work anymore"
At this point the damage is done and it's just a matter of time that the RDS (also Citrix XenApp) server will get a blue screen with the stop message: 0x000000AB - SESSION_HAS_VALID_POOL_ON_EXIT. Actually, the blue screen will happen right after the user logs off and no dump will be created.
Workaround for the printer driver host issue Only map network printer as client printer through EasyPrint (EMF with Citrix) or replace the bad printer driver with a good one. No Hotfix available so far from Microsoft about the BSOD but happend before, see CTX107896 and KB946068
How to know which driver is bad? Check the application eventlog for error 1000 and you will find entries that point to a printer driver DLL. Use print server properties to find the printer with the used module (DLL) on the RDS server. Note that the module might be shared with other printers. If it's shared than you might have more then one printer with the issue.
Hotfixes, articles for printing
Print queue does not work if the queue is not one of the first 100 queues installed in a Windows Server 2008 or Windows Server 2008 R2 Terminal Services session http://support.microsoft.com/kb/2532459
Invalid redirected printers may be available in a Remote Desktop Services session that connects to a RD Session Host server that is running Windows Server 2008 R2 http://support.microsoft.com/kb/2620656
Written by Gast on 2012-04-03 15:36:46Wir haben kein Druckertreiber der dort hinterlegt ist aber: Fehlerhafte Anwendung splwow64.exe, Version 6.0.6002.22165, Zeitstempel 0x4a537169, fehlerhaftes Modul ntdll.dll, Version 6.0.6002.18541, Zeitstempel 0x4ec3e855, Ausnahmecode 0xc0000374, Fehleroffset 0x00000000000acb17, Prozess-ID 0x1b8c, Anwendungsstartzeit 01cd115d7e8d03f6.
ntdll.dll Written by Whiddon on 2012-04-03 15:44:12Hallo Herr Kötzing,
sind Sie auch schon auf diesen Fehler getroffen?
Fehlerhafte Anwendung splwow64.exe, Version 6.0.6002.22165, Zeitstempel 0x4a537169, fehlerhaftes Modul ntdll.dll, Version 6.0.6002.18541, Zeitstempel 0x4ec3e855, Ausnahmecode 0xc0000374, Fehleroffset 0x00000000000acb17, Prozess-ID 0x1b8c, Anwendungsstartzeit 01cd115d7e8d03f6.
Unter Windows Server 2008 SP2 ?
JBX Written by Guest on 2014-02-12 16:35:09Hotfix available: http://support.microsoft.com/kb/2585233/en-us