Office Web Apps 2013 – SharePoint 2013 Information Rights Management (IRM) Protected document libraries preview error


We have been seeing some issues with SharePoint IRM policies applied to a SharePoint document library where users are able to view documents with Office Web Apps 2013, but not edit them.  This is expected behavior:

The issue is that when users attempt to preview the documents using Office Web Apps Server 2013, users will be presented with an error:

"Sorry, Word Web App can't display this embedded document because it's protected by Information Rights Management (IRM)"

As of this time, no further investigation is being conducted into this behavior.

Comments (18)

  1. Anonymous says:

    Office Web Apps 2013 – SharePoint 2013 Information Rights Management (IRM) Protected document libraries preview broken
    thanks

  2. Anonymous says:

    Hi – as of this time, the issue has not been fixed. I will post an update if the issue is addressed. Thanks!

  3. ramy ghazal says:

    any updates regarding the related topic

  4. Any further updates?

  5. Tirthankar says:

    Is there any further updates on this issue?

  6. Tirthankar says:

    Is there any further updates on this issue?

  7. Is this issue resolved ?

  8. Lucas Cavalcante says:

    Hello, just had the same problem. Any news in this regard?

  9. sridhar says:

    Bump…. any updates on this

  10. sharad patil says:

    Still have any updates?

  11. Mark says:

    Any update on this?

  12. Phil says:

    We have the same too. Cant believe this has been going on so long without a fix. It even states on the Office site that RMS documents can be opened in Read-only mode!

  13. nick says:

    How can there not be a resolution after 19 months?!

  14. B.K says:

    Please, Give me a patch~! ^^

  15. 1) Whats the protocol of calling URL https or http like
    https://contaso.xyz.com
    2) Remove IRM setting and test, once successful reapply the IRM settings

    1. James Bennett says:

      2) Remove IRM setting and test, once successful reapply the IRM settings

      worked for me today – just removed and reapplied; not a fix but a decent workaround

  16. Anon says:

    I am having this issue, is their a resolution as yet or an eta?

  17. James Bennett says:

    2) Remove IRM setting and test, once successful reapply the IRM settings

    worked for me today – just removed and reapplied; not a fix but a decent workaround

Skip to main content