thestig@, could you ptal?
pchalla@, could you please try to repro this.

thestig@ is OOO for this week.

pchalla@ is trying to repro the bug.

+ GCP leads to see if this is a blocker for M53 stable release that govind@  trying do stable release today

+Wei Li

Verified this issue in 53.0.2785.101, 53.0.2785.113 and 53.0.2785.116 & unable to replicate, it is printing fine.

Used: Windows 10 64 bit OS
Printer: HP LaserJet Pro 400.

Thank you pchalla@.

As pchalla@ is unable to repro the bug per comment #8, I'm planning to move forward with Desktop M53 Stable release today. pwestbro@/royans@, please let me know ASAP if there is any concern here. 

I've tried in the same exact release (53.0.2785.101) yesterday and couldn't repro. I've noticed one issue today where the service was running alongside Chrome 52, after updating to v53.0.2785.101 issue persisted. By restarting the service, and killing all chrome.exe processes, the issue went away. Though you mentioned that you've performed a freshly install and issue persists, so I can say that can be discarded.

Please get GCP debug logs and an output of an affected print job by going to www.google.com/cloudprint/simulate.html, then look for job lookup API, paste the print job ID, click get job, and post the output here (you need to be signed in with the printer owner account for this). If there's anything registered in the Windows Event viewer for the Windows Print Service regarding that print job, please get the info as well.

Also, please try checking the Windows TEMP folder; if it's full get rid of unnecessary files, and see if the local Windows user has writing permissions to that folder. I'll go ahead and try to repro later on today in Win10 and 7 pro 64 bit.

Mark: Can you create an enterprise support ticket for us to work with you through a support case and wee whats going on. Based on our investigations we don't think there is an issue here.

@govind: Due to lack of repro, I don't believe we have enough to block a 53 update.

Thank you royans@, per our chat and comment #11, I'm moving forward with M53 Desktop Stable release.

hernandezma@, Thank you for providing additional info in comment #10, I will follow these steps and check back in. 

royans@, If issue persists and is not resolved by following Comment 10 steps I will open a case.

I will follow up in about an hour and either open a ticket or explain what I missed the first time around. 

Thanks to all involved for taking the time to attempt to reproduce the problem on your end. Based on the info here and my troubleshooting collectively, I am getting that this is isolated to my environment and have clearly missed something. Thanks again!

-Mark

Version 53.0.2785.116 m (64-bit) - Works. I am a bit bummed that I am unable to locate installer for 53.0.2785.101 and I don't seem to have the enterprise installer stored.

For kicks, I did retrieve the debug log and any windows print service events from one the old print jobs). The windows print service event 823 is said to be normal and is logged regardless of job success or failure.

 Thank you all for investigating.

-Mark

Deleted: Microsoft-Windows-PrintService.txt 1.6 KB

Microsoft-Windows-PrintService.txt 1.6 KB View Download

Deleted: GCPdebuglog.txt 1.3 KB

GCPdebuglog.txt 1.3 KB View Download

Mark: Thanks for the confirmation.