Problem with RMS and Office 2013 RRS feed

  • Question

  • I have an AD forest/domain and am joined to the domain, logged in as a domain user.

    I'm using RMS 1.0 with SP2 on a Windows Server 2003 server with SP1.

    I have been using Office 2010 with RMS fine, and this still works.

    I have now installed Office 2013, and RMS is not working. When I open a protected file I get the following error:

    "You do not have permission to open this document"

    When I open a new document and try to protect it by going to Protect Document -> Connect to Digital Rights Management Servers and get templates I get the following error:

    "To use content with restricted permission you must reinstall and repair the Windows Rights Management components. If the problem continues, contact your administrator"

    My client is Windows 8. I am running Office 2010 and Office 2013 together on the same client (I need Outlook 2010 as I have Exchange 2013, and I just installed the whole lot as my research suggested this would be OK and I thought I would have access to both versions during my learning transition).

    As I've said, RMS works fine with Office 2010.

    On the RMS server I am seeing the following events when I unsuccessfully try to open a protected document in Office 2013:

    A client request contains secure data that is not trusted and that cannot be processed. The following information was reported: Microsoft.DigitalRightsManagement.Licensing.UntrustedPersonaCertException: The account certificate supplied by the requestor was not issued by a trusted user domain server.
       at Microsoft.DigitalRightsManagement.Core.ComponentBase.ValidatePersonaCert(PersonaCertificate oPersonaCert)
       at Microsoft.DigitalRightsManagement.Licensing.LicensePipeline.GenerateEUL(PersonaCertificate oPersonaCert, SignedRightsLabelDocument signedRightsLabel, String Ticket, IDrmsPropertyBag propertyBag)
       at Microsoft.DigitalRightsManagement.Licensing.LicensePipeline.PipelineAcquireLicense(AcquireLicenseParams[] RequestParams, HttpRequest request, IIdentity userIdentity)

    For more information, see Help and Support Center


    Tuesday, June 11, 2013 7:55 PM

All replies

  • Anyone?!
    Wednesday, June 12, 2013 7:31 PM
  • I'm very disappointed that nobody seems able to help. Does anybody have any guidance on this at all?
    Friday, June 14, 2013 8:35 PM
  • I am having the exact same problem only my clients are Windows 7 64 and 32 bit.  I originally posted in a different forum and was given several links which I had already read many times and was told to post here as the techs here were more informed in IRM.  Here's hoping someone replies with an answer.
    Monday, June 17, 2013 2:32 PM
  • I don't think Office 2013 is supported with Windows RMS 1.0. Given that Windows RMS is getting close to the end of its support lifecycle you should consider upgrading it to AD RMS or moving to AAD RM.

    In the meantime, make sure to update your server's SLC since the ones in existing Windows RMS servers have intermediate certificates in the chain that will be expiring in November.

    Enrique Saggese - Sr. Program Manager - Information Protection - Microsoft Corporation

    Tuesday, June 18, 2013 6:15 PM
  • I am having the same problem between RMS 1.0 SP2 and Office 2013. Office 2007 and 2010 has no any problem in our environment, but Office 2013 cannot open IRM document.

    Does Office 2013 support Window Server 2003 RMS 1.0 SP2?

    Client is Window 7 32 bit and office 2013 small business version.

    • Edited by Ben Wong.KS Friday, November 1, 2013 8:53 AM
    Friday, November 1, 2013 7:01 AM
  • Has any reference about Office 2013 and RMS 1.0 SP2?
    Wednesday, November 6, 2013 3:41 AM
  • The Office 2013 client uses the MSIPC client (RMSv2) and it relies on the Template Web Service to download templates.
    That service did not exist in RMS.

    You might can try this.

    If there is anything in


    the RMS Client 2x will not download any templates from your server and will instead use the templates you have
    placed in this directory. 

    For anyone running RMS 1.x be aware that you should update your SLC now while you still can.  The backend service will be retired soon.

    Tuesday, November 12, 2013 6:05 PM