Sage Reports Won't Print to the Sage PDF Printer and Faults with an Exception

We see this quite regularly on our hosted platform with Windows 2008 R2 and Sage Accounts software. We are called by customers saying the Sage PDF printer provided by Sage continually crashes. Normally with a single user system a restart of the PC fixes this however in a multi-user environment this would affect everyone else. The issue we get reported is similar to

Faulting application name: splwow64.exe, version: 6.1.7600.16385, time stamp: 0x4a5bd3ca
Faulting module name: ntdll.dll, version: 6.1.7600.16915, time stamp: 0x4ec4b137
Exception code: 0xc0000374
Fault offset: 0x00000000000c6ae2
Faulting process id: 0x700
Faulting application start time: 0x01cd3994d897a813
Faulting application path: C:\Windows\splwow64.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

We advise the customer that they should install CUTEPDF as their PDF printer and use this rather than the Sage version. Search Google for CUTEPDF to find the latest version. If this is installed on the local PC this will be brought through to our remote terminal server remote desktop session that is running the Sage application. This can then be chosen as the printer to create the PDF file.

Cardium offer services including Cloud Computing using Microsoft Remote Desktop Services paid for monthly and per user, installation, consultancy and virtualisation best practises.