I’ve seen a rash of these cases recently. It’s ranged from not being able to configure IRM integration on SharePoint (hence my earlier post) to just about any client interaction with RMS server symptom.
The client will report some error. The AD RMS server side is quiet. You have to dig into the IIS server logs on the AD RMS server to find the clue.
In my SharePoint specific post (link below) we have errors similar to the following.
GET /_wmcs/certification/servicelocator.asmx – 443 <snip> 500 0 64 453
So, I am linking to my own earlier blog post with the following caveat. Go to the “The Cause” section and see if the SSL settings on the RMS server are the cause of the 500 returns.
SharePoint 2010 and IRM Integration – now with applicability to other RMS issues.