I am an IT admin for an office of about 50 people. We run a mix of Windows 7 and a small number of Windows 8.1 machines, all running Windows x64. Some users are unable to print some documents, most times word files, sometimes excel - but other files print fine to network printers, and the only ones I have ever not seen print are ones that originated as Office 2013 files.

We have a Windows Print Server running 2012 R2 on a VM, with 4GB of memory. Our previous print server was a Server 2008 32-bit server, before we had Windows 8.1 clients.

We are trying to print to HP 2420dn and 2605dn printers, but it will not print to them. 

Our old print server ran vendor-made Type-3 drivers and client machines rendered the print job and we had few problems. Our new print server is running the Microsoft Type-4 class drivers which run almost all jobs fine but some Office 2013 documents do not work. It appears the server is rendering these print jobs, but I have render print jobs on the client checked. The event viewer shows the job was spooled and is being printed on the client side, but on the server the process for printing crashes out.

The event log I get when one of these jobs attempts to run is:

---824---

A fatal error occurred while printing job <timesheet>.xlsx, id 105 on the print queue <printername>. The print filter pipeline process was terminated. Error information: 0x8007003F.

-------

This is our only print server so diagnosing it is... difficult as we seem to do a lot of printing. I feel this is a bug in Microsoft's 2012 Server/Office 2013 because it didn't used to be a problem until those were both involved.  I have printed some of the documents to oxps and can print them, but sometimes I can't. Saving as PDF does not seem to fix the problem either. I have tried without background printing and with, no differences.

I am unsure where to go from here and need some help diagnosing or fixing this.

• Edited by Mgamerz 12 hours 38 minutes ago