Microsoft KB Archive/926135

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 18:33, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


Error message when you use a Microsoft program in Microsoft Windows XP or in Microsoft Windows Server 2003: "E_DRM_MANIFEST_POLICY_VIOLATION" or "E_DRM_ACTIVATIONFAILED"

Article ID: 926135

Article Last Modified on 2/12/2007



APPLIES TO

  • Microsoft Windows Rights Management Services (RMS) for Windows Server 2003
  • Microsoft Windows Rights Management Services (RMS) for Windows Server 2003 Service Pack 1



SYMPTOMS

When you use a Microsoft program in Microsoft Windows XP or in Microsoft Windows Server 2003, you may receive an error message that resembles one of the following:

Error message 1


E_DRM_MANIFEST_POLICY_VIOLATION

Error message 2


E_DRM_ACTIVATIONFAILED

CAUSE

This problem occurs because of a bug in the Windows Crypto Service.

RESOLUTION

To resolve this problem, rename the Catroot2 folder. To do this, follow these steps:

  1. Delete all the tmp*.cat files in the following folders:

    Drive letter\WINDOWS\system32\CatRoot\{127D0A1D-4EF2-11D1-8608-00C04FC295EE}
    Drive letter\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}

    Note Drive letter represents the letter of the drive on which Windows is installed.
  2. Click Start, click Run, type cmd, and then click OK.
  3. At the command prompt, type the following commands. Press ENTER after each command.

    net stop cryptsvc
    ren %systemroot%\System32\Catroot2 oldcatroot2
    net start cryptsvc
    exit

Important Do not rename the Catroot folder. The Catroot2 folder is automatically re-created by Windows. However, the Catroot folder is not re-created if you rename it.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Keywords: kbnofix kbtshoot kbbug KB926135