We Get Blank Pages When Printing E-Mail From Office365

[6Foot2]

We have just moved our staff E-Mail from Exchange to Office365. We find now that we get at least 5 blank pages before the main body of the E-Mail is printed [blank except for headers and footers which is correctly numbered 1 of 11, 2 of 11,...]

 

This did not happen with Internet Explorer and Exchange but does with Internet Explorer and Office365 [nothing else has changed]

 

I have been told that the problem lies here:

 

http://i.snag.gy/djDNi.jpg

 

Apparently I should be selecting 'As laid out on screen' but that option is greyed out. I gave been given a Registry hack but it is no good because the sub-key I have been directed to does not exist on my station:

 

This is the supplied Registry location:

 

HKEY_CURRENT_USER\Software\Policies\Microsoft\Internet Explorer\Control Panel

 

This is a screenshot of my Registry close to where I should find that entry:

 

http://i.snag.gy/9QoRs.jpg

 

Has anyone else seen this or fixed it?

 

Internet Explorer version: 8

Client O/s: Windows 7 Pro: 64 Bit: SP1

 

This problem does not happen in Chrome but I cannot use that as a long term answer.

 

[i could probably solve this by deploying IE9 or IE10. However for numerous reasons that is not an option for me at this time]

 

Thanks.

[6Foot2]

Update: I have been in touch with Microsoft [via our LEA] and they have said that they have reproduced the problem in their offices and are now working toward a solution.

 

Estimated timeline for delivery of solution: Unknown.

[bodminman]

Update: I have been in touch with Microsoft [via our LEA] and they have said that they have reproduced the problem in their offices and are now working toward a solution.

 

Estimated timeline for delivery of solution: Unknown.

 

We too have the same issue and we are using IE9 and we also got the same response from MS!

 

I have just told staff to use the 'Print from page x to x' function in the Print dialogue box until there is a permanent solution to this.

[6Foot2]

...I have just told staff to use the 'Print from page x to x' function in the Print dialogue box until there is a permanent solution to this.

 

We have been experimenting while waiting for a fix from Microsoft.

 

We have found: Chrome [my browser of choice] does not suffer this issue.

IE10 does not suffer this issue. We cannot deploy IE10 until the Head/My Line Manager has given the all clear: No answer yet.

[kearton]

http://dilbert.com/dyn/str_strip/000000000/00000000/0000000/000000/00000/2000/400/2482/2482.strip.sunday.gif

[bodminman]

Chrome, Firefox and IE10 do not suffer with this issue.

[adhutton]

We had this issue a couple of weeks ago.

 

It was fixed by upgrading the printer driver(s) to the latest version.

 

Andrew

[6Foot2]

We had this issue a couple of weeks ago.

 

It was fixed by upgrading the printer driver(s) to the latest version.

 

Andrew

 

I don't think this will work for us: I only recently updated our printer drivers on our print server.

[bodminman]

Same here. The first thing I tried was to update the drivers.

[jamesbmarshall]

As well as posting in here, I'm assuming you're all being good and logging this as an issue with Microsoft Support too?

 

[6Foot2]

As well as posting in here, I'm assuming you're all being good and logging this as an issue with Microsoft Support too?

 

 

Yes. Currently waiting on Microsoft for a solution to this and another where there is problem with forwarded messages.

[bodminman]

As well as posting in here, I'm assuming you're all being good and logging this as an issue with Microsoft Support too?

 

 

Yep!

[bodminman]

LMAO - Just had Microsoft on the phone offering me a solution to the printing issue.

 

Install and use another browser for the time being! WTF

[Michael]

This wasn't a problem with Office 365, Exchange 2010 and IE9 but is a problem with Office 365, Exchange 2013 and IE9.

 

Are IE8 and IE10 immune from this bug? Do Microsoft have a date when this'll be fixed? Many thanks!

[6Foot2]

No estimated date for a fix but I do get E-Mails regularly confirming that they have been able to reproduce the problem and are actively working on a resolution.

[6Foot2]

As well as posting in here, I'm assuming you're all being good and logging this as an issue with Microsoft Support too?

 

I received an E-Mail from Microsoft [and a follow up telephone call today] saying that the problem had been resolved and could I test it. Tested it with a short E-Mail and it printed 6 blank pages and one with content so I guess 'no not fixed' is the answer here. Anyone else heard any more?

[Michael]

I ended up deploying IE10 with WSUS and everything's working perfectly now. There were a few LA websites in Birmingham which only worked with IE8 and Adobe Reader 9, but conveniently these have been addressed, so all users are now using IE10 and Adobe Reader 11.

[Michael]

I forgot to say, in my testing the problem is there with IE8 and IE9, on any supporting OS. The only solution is IE10, Firefox or Chrome.

 

It's unclear why Microsoft are taking so long to address the issue with IE9. You'd think they could take snippets of code from IE10, as the issue doesn't exist when this is installed.

[6Foot2]

We are virtualising our servers over the Summer break. Alongside this work we are also creating a new domain, migrating our staff and students to the new domain and rebuilding all of our workstations and laptops. The rebuilt workstations will have IE10. I guess we will have some website validations to do over the Summer too.

[6Foot2]

For information: I have received an update on this and another issue today. Paraphrasing the E-Mail I that came through today:

 

On the printing of blank pages: This will be fixed in a Microsoft update in the next 2 months. In the meantime the only recommendation is to use an alternative browser such as FireFox or Google Chrome or use the local outlook client. [so advice unchanged here]

 

On stripping out of original senders' E-Mail addresses in forwarded E-Mails: There will be a fix for this but Microsoft are unable to provide a time/date for this.