This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

When using Outlook.live.com, I can't open pdf files or word files. I get an OWA Error 500

  • 1 reply
  • 1 has this problem
  • 1 view
  • Last reply by Henry.M

Len Belanger
Len Belanger
more options

A week ago I started getting errors while reading emails and trying to open/download attachments like PDF's and Word files. I get an OWA 500 error.

I share my machine with my wife and if I go into her account, use the same version of FireFox and the same Outlook.live.com for email and try to open the same attachments for the same emails, I DO NOT get the same errors. Any help would be appreciated. Thanks

A week ago I started getting errors while reading emails and trying to open/download attachments like PDF's and Word files. I get an OWA 500 error. I share my machine with my wife and if I go into her account, use the same version of FireFox and the same Outlook.live.com for email and try to open the same attachments for the same emails, I DO NOT get the same errors. Any help would be appreciated. Thanks

All Replies (1)

Henry.M
Henry.M
more options

Hi, Len Belanger

Are you still getting this error message? Is it only occurring with PDF attachments?

To open a private browser window, right-click on the browser icon on the taskbar and choose the option for a new private or incognito window.

If yes, the problem is with your local cache - clear the browser cache. If no, You can use in-app support to bring it to the attention of Microsoft support.

Based on the error message, it seems to be server side -

Please take a look, please hope it helps ;

Thanks for reporting.