SP 2013: RMS Configuration not working: The required Active Directory Rights Management Service Client (MSIPC.DLL) is present but could not be configured properly. IRM will not work until the client is configured


Problem: Every time customer tried to configure SharePoint to connect to the AD RMS server this error would appear

image

We verified that these two files had proper rights, at first they did not:

  1. https://rmsserver/_wmcs/certification/certification.asmx and
  2. https://rmsserver/_wmcs/certification/servercertification.asmx

 

  1. Log on to ADRMS server as an Administrator.
  2. Click Start, and then click Computer.
  3. Navigate to C:\Inetpub\wwwroot\_wmcs\Certification.
  4. Right-click ServerCertification.asmx, click Properties, and then click the Security tab.
  5. Click Advanced, click Edit, select the Include inheritable permissions from this object's parent check box, and then click OK two times.
  6. Click Edit, and then click Add.
  7. Click Object Types, select the Computers check box, and then click OK.
  8. Type YourSharePointServerName, and then click OK. (note: If your SharePoint service/application pool is a domain account you can, and should give it rights here as well. If you have multiple application pools, you might need to add them if they require RMS support)
  9. Click OK to close the ServerCertification.asmx Properties sheet.
    By default the Read & execute and the Read permissions are configured for the SharePoint server computer account object and all other accounts inherited from the parent folder. (make sure to set Allow Inheritable Permissions on ServerCertification.asmx).
    It's good practice to specifically give the SharePoint Application Pool accounts these rights as well.
  10. Click Start, and then click Command Prompt.
  11. Type iisreset, and then press ENTER.

We also verified that their User Profile Sync was actually syncing properly.

Still the same error.

Resolution: finally the customer manually configured their proxy settings on the WFE and Central Admin server using set proxy command

Comments (6)

  1. Qanna says:

    Hi,

    What do you mean by this? "finally the customer manually configured their proxy settings on the WFE and Central Admin server using set proxy command"

    I also experiencing this issue right now, and i cant fix it.

    Hope you can share what your customer did.

    Thanks

    1. Sal Rosales says:

      Sorry for the delay. My customer went to their SharePoint servers, in this case two of them, and set their proxies using the 'netsh winhttp set proxy MyProxyServer' command as indicated in this article: https://technet.microsoft.com/en-us/library/dd772586(v=ws.10).aspx

  2. John VanHoose says:

    Did you find a resolve for this issue, I am having the same issue.

  3. Emran says:

    hi,
    i have same problem wtih this and i cannot understand what do you mean about : "finally the customer manually configured their proxy settings on the WFE and Central Admin server using set proxy command"

    thanks

  4. SUbodh says:

    Helpful doc

  5. mahesh says:

    I have given all permission, it was working fine but suddenly we have started getting this error on production. nothing has been changed yet so far

Skip to main content