RDS 2012 weird printing problem

Question

Hello All,
We have a very strange issue with 1 of our users. She can crash the print spooler very frequently. The problems almost always occurs when she need to print an excel file. Due to the frequency we needed to make sure the print spooler would always restart
otherwise making all of our users unable to print. The excel file she's trying to print isn't that large (90kb) and contains data from column A - AB. It consist of 684 rows of data. She then goes to file --> Print selects a printer and *boom* the spooler
crashes. It than display a message. The message usually lists:
1) Cannot connect to the printer
2) No printers installed
This also makes the event viewer fill up with the following events:
Faulting application name: spoolsv.exe, version: 6.2.9200.16384, time stamp: 0x501080ef
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16864, time stamp: 0x531d34d8
Exception code: 0xc0000002
Fault offset: 0x0000000000047b8c
Faulting process id: 0x7364
Faulting application start time: 0x01d01e8436f79952
Faulting application path: C:\Windows\System32\spoolsv.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 4ed8a353-8aac-11e4-940c-005056b34020
Faulting package full name: 
Faulting package-relative application ID: 
Faulting application name: spoolsv.exe, version: 6.2.9200.16384, time stamp: 0x501080ef
Faulting module name: ntdll.dll, version: 6.2.9200.17046, time stamp: 0x53b4864c
Exception code: 0xc0000005
Fault offset: 0x0000000000001069
Faulting process id: 0xa9ac
Faulting application start time: 0x01d01eb914acc298
Faulting application path: C:\Windows\System32\spoolsv.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: dd68d8b8-8aad-11e4-940c-005056b34020
Faulting package full name: 
Faulting package-relative application ID: 
Faulting application name: spoolsv.exe, version: 6.2.9200.16384, time stamp: 0x501080ef
Faulting module name: win32spl.dll, version: 6.2.9200.17041, time stamp: 0x53aa2d39
Exception code: 0xc0000005
Fault offset: 0x000000000007c024
Faulting process id: 0xa23c
Faulting application start time: 0x01d01ebad13bc3be
Faulting application path: C:\Windows\System32\spoolsv.exe
Faulting module path: C:\Windows\System32\win32spl.dll
Report Id: 81db8d0f-8ab0-11e4-940c-005056b34020
Faulting package full name: 
Faulting package-relative application ID: 
While testing we came across a strange phenomena. When she logs onto a RDS server using RemoteApp we see that automatically a group of printers gets created. Those are not displayed in excel/word/outlook/etc. and are only visable trough Control Panel. If
we delete those and she relogs the automatically get recreated. Which printers are added differs from the server she is logged on by our load balancer.  
Background of our RDS
Our RDS environment consist of a connection broker and 2 application servers. All of which are running
Server 2012 (non R2). All applications are started as a remoteapp from a Windows 7 or 8(.1) update 1)) or axel zero client. User have Remote Roaming Profiles (RRP) and a User Profile Disk (UPD). These are cached onto the RDS server, so creating a new profile
is almost impossible by our knowledge. 
The odd part of all this is that we cannot reproduce this issue, and only this 1 user has this issue. Even removing all printers and leaving just the XPS and one note printer from Microsoft is enough to let the spooler crash. Because of this (and the fact
that no one else has this problem) makes me very certain this isn't an issue with our Print server;RDS server or Drivers. 
So my question basically come down to:
1) Can i easily give the user a new profile even though the profiles are cached? (since this is a production environment a reboot can only happen on maintenance periods)
2) Where are these extra printers coming from? And how do i get rid of them?
General troubleshooting tips on this issue are welcome. As i'd like to know how this started or how i can find more helpfull information.
Thanks guys and have a happy x-mas. 

Answer 1

Hello, Niek
Slenders.
Your problem very similar to us. We are using RDS on Windows Server 2012 R2 and RD Clients are Windows 7. Using Profile Disks too.
Main problems :
1). Print Spooler crashing. We enabled execution of Print Drivers in isolated process Group Policies. Learn
more.
2). Extra Printers, that cannot be deleted with user rights (Usually they looks transparent in Devices and Printers). This
update did not help. These printers are server specific and profile recreation does not help. If administrator log on server and delete these excess printers - they will disapper for
all users on this server. Therefore, they are store somewhere in HKLM. Temporary solution we use - clear
registry hive HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001(002)\Enum\SWD\PRINTENUM\ with Registrar Registry Manager and then reboot server;  
3). Cannot connect to the Network Printer via FQDN. Solution -  clear registry hive HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider\Servers
4). None printer set as default - profile recreation helps.
Hope this help.
Hello fapw,
Thanks for your response. It is very detailed and i'm sure it will help us.
1) Already enabled isolation mode in case it were bad drivers. But the spooler keeps chrashing.
2) Just as we are experiencing. Thanks for pointing out the registery location. This might a great shot during the next maintenance window.
3) We have not yet seen this issue. Might be because we use the internet printing role and the users connect trough the webpage.
4) Hasn't been an issue so far. But good to know. 
Will keep you updated. 
Regards,
Niek