Summary of problems during Moss RMS Integration

This problem occurs when many people integrate Moss RMS.

This log will write down the problems and solutions I have encountered.

The most likely cause is that

1. The required windows rights management client exists, but the server has rejected access. Before the server is granted permissions, the system does not run. XXXX mname $ domain.com xxxx

This error is caused by permission settings. In AD, add the moss Administrator (and the running account of the moss site application pool) to the RMS Service Group, then add the RMS Service Group to _ wmcs \ certification \ servercertification. asmx.

Correct: Put the moss Administrator (the Running Account of the moss site application pool) and the moss server in the AD (yes, that is, the machine !), Add the RMS Service Group and the moss server to _ wmcs \ certification \ servercertification. asmx.

2. An error occurred while sending the document to the Downloaded copy: the error is from hresult: 0x80041056. When the document is opened online, the word is blank (it should be said that it is blank blue)

This error occurs because the current Moss user does not have the correct mail attribute, or it may be that the user has been imported to SSP when the mail attribute is not set in AD, later, it was set in ad, but it was not synchronized to SSP.

3. the download box does not pop up for half a day when you download the document. When you open it directly, word displays a download progress bar.

This is because Moss cannot access the RMS server. Check it ....

4. Open the document online. The word is blank.

This error was solved and shared by a friend in the group, because the IIS pool uses a local account and cannot interact with RMS.

 

That's all you can think. I think about it later, or I met it again, and then updated it. If you have any other questions, please reply to them ^_^.