Event ID 11 — AD RMS Cluster Configuration
Applies To: Windows Server 2008
Servers in an Active Directory Rights Management Services (AD RMS) cluster are configured to both send and receive requests from AD RMS clients, other servers in the AD RMS cluster, and the AD RMS databases.
Event Details
Product: | Windows Operating System |
ID: | 11 |
Source: | Active Directory Rights Management Services |
Version: | 6.0 |
Symbolic Name: | ConfigurationErrorEvent |
Message: | An error occurred when the AD RMS cluster attempted to retrieve data from the configuration database or this computer's configuration storage. Parameter Reference Context: %1 RequestId: %2 %3 %4 |
Resolve
Fix AD RMS error conditions
To determine how to fix this error condition, examine the exception errors reported in the event message text. The additional details are displayed as exception errors.
The event message can report the following exceptions:
- ConfigSourcePolicyNameNotUniqueException
- ConfigSourceMissingLicensorCertificateException
- ConfigSourceConnectionStringNotFoundException
- ConfigureSourceTrustedAuthorityDataIntegrityException
- InvalidPrivateKeyPasswordException
- BadPrivateKeyDataException
- InvalidDatabaseConfigurationStringException
ConfigSourcePolicyNameNotUniqueException
This exception indicates that there is a duplicate configuration policy name in the AD RMS configuration database. The name of each configuration policy stored in the AD RMS configuration database must be unique.
To perform this procedure, you must be a member of the local System Administrators database role, or you must have been delegated the appropriate authority.
To check if there is a duplicate configuration policy name in the AD RMS configuration database:
- Log on to the AD RMS configuration database server.
- Click Start, point to All Programs, click Microsoft SQL Server 2005, and then click SQL Server Management Studio.
- In the Server name box, type the name of the AD RMS configuration database server, and then click Connect.
- Expand Databases, and then click the AD RMS configuration database. By default, the name of this database is DRMS_Config*_clustername*_portnumber, where clustername is the name of the AD RMS cluster and portnumber is the TCP port in which the AD RMS Web services listens for requests.
- Click New Query.
- Type select * from drms_clusterpolicies, and then click Execute.
- Determine the entry that is not correct and delete it.
ConfigSourceMissingLicensorCertificateException
To perform this procedure, you must be a member of the local Administrators group, or you must have been delegated the appropriate authority.
This exception indicates that the server licensor certificate (SLC) for this AD RMS cluster cannot be found. To resolve this error, you must restore the AD RMS configuration database from a previous backup.
To restore AD RMS configuration database from previous backup:
- Log on to the AD RMS configuration database server, click Start, point to All Programs, click Microsoft SQL Server 2005, and then click SQL Server Management Studio.
- In the Server name box, type the name of the AD RMS configuration database server, and then click Connect.
- Right-click Databases, and then click Restore Database.
- In the To database box, select the AD RMS configuration database from the list.
- Click the From device option, and then click the browse button.
- Click Add.
- In the Locate Backup File window, select the database backup file, and then click OK two times.
- Select the Restore check box, and then click OK.
ConfigSourceConnectionStringNotFoundException
This exception indicates that the database connection string for the AD RMS configuration database in the registry on a server in the AD RMS cluster does not exist or is incorrect.
To perform this procedure, you must be a member of the local Administrators group, or you must have been delegated the appropriate authority.
To check the database connection string in the registry on a server in the AD RMS cluster:
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
- Log on to a AD RMS server in the cluster, and then click Start.
- In the Start Search box, type regedit, and then press ENTER.
- Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\DRMS\2.0\ConnectionString.
- Right-click ConfigDatabaseConnectionString, and then click Modify.
- Change the data source to the name of AD RMS configuration database server.
- Change the database to the name of the AD RMS configuration database. By default, the name of the AD RMS configuration database is DRMS_Config_clustername_portnumber where clustername is the name of the AD RMS cluster and portnumber is the TCP port number used for AD RMS communication.
- Click OK.
ConfigureSourceTrustedAuthorityDataIntegrityException
To perform this procedure, you must be a member of the local System Administrators database role, or you must have been delegated the appropriate authority.
To check if there is a valid trusted certification authority in the AD RMS configuration database:
- Log on to the AD RMS configuration database server.
- Click Start, point to All Programs, click Microsoft SQL Server 2005, and then click SQL Server Management Studio.
- In the Server name box, type the name of the AD RMS configuration database server, and then click Connect.
- Expand Databases, and then click the AD RMS configuration database. By default, the name of this database is DRMS_Config*_clustername*_portnumber, where clustername is the name of the AD RMS cluster and portnumber is the TCP port in which the AD RMS Web services listens for requests.
- Click New Query.
- Type select * from drms_TrustedCertificateAuthorities, and then click Execute.
- Verify that a valid trusted certification authority exists with the associated GUID.
InvalidPrivateKeyPasswordException
This exception indicates that the AD RMS cluster key password is missing from the registry. The cluster key password is encrypted and stored in the registry under HKEY_LOCAL_MACHINE\Software\Microsoft\DRMS\2.0\KeyProtection.
To perform this procedure, you must be a member of the local AD RMS Enterprise Administrators group, or you must have been delegated the appropriate authority.
To restore the AD RMS signing key password:
- Log on to a server in the AD RMS cluster.
- Open the Active Directory Rights Management Services console, and then expand the AD RMS cluster.
- In the console tree, expand Security Policies, and then click Change cluster key password.
- In the Cluster Key Password wizard, type the password for the cluster key in the Password box.
- In the Confirm password box, type the password again.
- Click Apply to complete the password reset.
- Repeat steps 1 - 6 on each server in the AD RMS cluster.
Caution: The cluster key password must be set to the password used by the AD RMS cluster before the registry key was deleted.
BadPrivateKeyDataException
This exception indicates that the cryptographic service provider (CSP) cannot find the key container specified in the AD RMS configuration database. This exception could also occur when importing a trusted publishing domain that a CSP to protect the cluster key.
To make it possible for the CSP to find the key container:
- Consult with the CSP manufacturer to verify that the CSP is compatible with AD RMS.
- Reinstall AD RMS cluster using compatible CSP.
InvalidDatabaseConfigurationStringException
This exception indicates that the database connection string for the AD RMS configuration database in the registry on a server in the AD RMS cluster does not exist or is incorrect.
To perform this procedure, you must be a member of the local Administrators group, or you must have been delegated the appropriate authority.
To check the database connection string in the registry on a server in the AD RMS cluster:
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
- Log on to a AD RMS server in the cluster, and then click Start.
- In the Start Search box, type regedit, and then press ENTER.
- Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\DRMS\2.0\ConnectionString.
- Right-click ConfigDatabaseConnectionString, and then click Modify.
- Change the data source to the name of AD RMS configuration database server.
- Change the database to the name of the AD RMS configuration database. By default, the name of the AD RMS configuration database is DRMS_Config_clustername_portnumber where clustername is the name of the AD RMS cluster and portnumber is the TCP port number used for AD RMS communication.
- Click OK.
Verify
To perform this procedure, you must be a member of the local Users group, or you must have been delegated the appropriate authority.
Note: Microsoft Office Word 2007 is used as an example in this section. Any AD RMS-enabled application can be used in place of Word 2007.
To verify that AD RMS is configured correctly, do the following:
- Log on to an AD RMS-enabled client computer.
- Click Start, point to All Programs, point to Microsoft Office, and then click Microsoft Office Word 2007.
- In the new document type This is a test document.
- Click the Microsoft Office Start Button, point to Prepare, point to Restrict Permissions, and then click Restricted Access.
- Select the Restrict permissions to this document check box.
- Type another AD RMS user's e-mail address in the Read box, and then click OK.
- Send this file to the person who was granted access in step 6.
- Have this person open the document and verify that he or she cannot do anything else with the document such as print it.