Hi. We have several 2008R2 SP1 RDS servers with RD Easy Print enabled. We have issue printing some documents from some programs for example specific PDF files, but also from specific applications. What happens is the job gets actually spooled on the Terminal Server and is then spooled to the client. The client picks it up but while processing mstsc.exe crashes on ntdll.dll and stops working. The print is not finished. The error from eventlog: (this is from Windows 7 Pro x64, fully patched):
Faulting application name: mstsc.exe, version: 6.2.9200.16398, time stamp: 0x5036045e
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc00000fd
Fault offset: 0x0000000000026032
Faulting process id: 0xc60
Faulting application start time: 0x01ce32c83cc524a0
Faulting application path: C:\Windows\system32\mstsc.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: b8687a80-9ebb-11e2-a8c4-e10a19378402
Same happens from Windows 8 x64, also patched through Windows Updates:
Faulting package-relative application ID:
From Windows XP though everything works fine. I am not sure if it's the client OS or the server OS. What have I tried?
- Installed a fresh 2008R2SP1 server, without any patches / updates / hotfixes.
- Installed a fresh copy of Windows 7 x64 SP1, without any patches / updates / hotfixes.
- Installed several print related hotfixes from http://blogs.technet.com/b/yongrhee/archive/2011/10/29/list-of-print-related-hotfixes-post-service-pack-1-for-windows-server-2008-r2-service-pack-1.aspx
- Installed mstsc hotfix KB2648397.
- Tried with about 15 different printerdrivers, also PDF printers. Same problem with all of them.
- Also tried KB2545627 which addresses some ntdll.dll issues.
Problem has been the same with all combinations I tried, patched client vs fresh server, patched server vs fresh client, always mstsc.exe crash. As soon as I stop using Easy Print and install the printers own driver on the server, it works flawlessly, so it must be an EasyPrint issue, either client or serverside. We must use EasyPrint though, as we litteraly have over 200 different printers (we provide a shared RDS service to several customers) and it's unworkable to install all drivers. EasyPrint is a very good alternative for us.
What to do? I have a specific PDF now that crashes the system, I'll check with my customer if I am allowed to provide it here if someone wants to reproduce.