Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
EmailArticle ID: 961403 - Last Review: October 8, 2011 - Revision: 2.0 After the Active Directory RMS role is decommissioned on a Windows Server 2008-based server, users cannot open documents that IRM helps protect
On This PageSYMPTOMSIn a network environment, you have an Active Directory (AD) Rights Management Services (RMS) server that is running Windows Server 2008. After the AD RMS role is decommissioned, users in the network cannot open documents that Information Rights Management (IRM) helps protect. Note This issue does not occur if the AD RMS server is running on a Windows Server 2003-based computer. CAUSEThis issue occurs because the RMS server does not specify the XML element orders when it defines XML serialization for decommissioning SOAP responses. When an RMS server is decommissioned, the server no longer responds to regular AcquireLicense requests from a client. Instead, the server responds only to AcquireContentKey requests in which the content key is returned directly to the requestor. Therefore, the application does not interpret the response correctly. RESOLUTIONHotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page. PrerequisitesTo apply this hotfix, you must have Windows Server 2008 installed on the computer.Restart requirementYou have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2008 file information noteThe .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.For all supported x86-based versions of Windows Server 2008Collapse this table
For all supported x64-based versions of Windows Server 2008Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about RMS, visit the following Microsoft Web sites: http://www.microsoft.com/windowsserver2003/technologies/rightsmgmt/default.mspx
(http://www.microsoft.com/windowsserver2003/technologies/rightsmgmt/default.mspx)
http://technet.microsoft.com/en-us/library/cc771307.aspx
(http://technet.microsoft.com/en-us/library/cc771307.aspx)
For more information about decommissioning AD RMS, visit the following Microsoft Web sites:http://technet.microsoft.com/en-us/library/cc754967.aspx
(http://technet.microsoft.com/en-us/library/cc754967.aspx)
For more information about the AcquireLicense function, visit the following Microsoft Web sites:http://msdn.microsoft.com/en-us/library/aa964283(vs.85).aspx
(http://msdn.microsoft.com/en-us/library/aa964283(vs.85).aspx)
For more information about the AcquireContentKey function, visit the following Microsoft Web sites:http://msdn.microsoft.com/en-us/library/aa362763(VS.85).aspx
(http://msdn.microsoft.com/en-us/library/aa362763(VS.85).aspx)
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Additional file information for Windows Server 2008Additional files for all supported x86-based versions of Windows Server 2008Collapse this table
Additional files for all supported x64-based versions of Windows Server 2008Collapse this table
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|
Back to the top
