| Event Id | 167 |
| Source | Active Directory Rights Management Services |
| Description | The cluster to which you are trying to join this server is not currently provisioned as either a root or licensing-only cluster. The provisioning process cannot continue. Join this server to a cluster that is already provisioned as either a root or licensing-only cluster. |
| Event Information | According to Microsoft : Cause : This event is logged when the provisioning process cannot continue. Join this server to a cluster that is already provisioned as either a root or licensing-only cluster. Resolution : Check the ClusterType value in configuration database During AD RMS installation a configuration database is created that stores information about the AD RMS cluster, including whether or not the cluster is a root or licensing-only cluster. If the value is not either certification or licensing, the AD RMS server cannot be added to the cluster. You should ensure that the cluster type stored in the AD RMS configuration database is valid and then install the AD RMS role again. Check the ClusterType value in AD RMS configuration database To perform this procedure, you must be a member of theSystem Administrators database server role, or must have been delegated the appropriate authority. To check the ClusterType value in AD RMS configuration database: 1.Log on to the AD RMS configuration database server. 2.ClickStart, point toAll Programs, clickMicrosoft SQL Server 2005, and then clickSQL Server Management Studio. 3.In theServer name box, type the name of the AD RMS configuration database server, and then click Connect. 4.ExpandDatabases, 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 on which the AD RMS Web services listens for requests. 5.ClickNew Query. 6.Typeselect * from drms_clusterpolicies where policyname = 'ClusterType', and then click Execute. 7.If the result in thePolicyData column is notCertification orLicensing, new AD RMS servers cannot be joined to this cluster. 8.Restore a previous version of the AD RMS configuration database that has the correct value in the PolicyData column of the ClusterType row. Restore AD RMS configuration database from previous backup To restore AD RMS configuration database from previous backup:1.Log on to the server that is hosting the AD RMS configuration database, clickStart, point toAll Programs, click Microsoft SQL Server 2005, and then clickSQL Server Management Studio. 2.In theServer name box, type the name of the AD RMS configuration database server, and then clickConnect. 3.Right-clickDatabases, and then clickRestore Database. 4.In theTo database box, select the AD RMS configuration database from the list. 5.Click the From device option, and then click the browse button. 6.ClickAdd. 7.In theLocate Backup File window, select the database backup file, and then clickOK two times. 7.Select theRestore check box, and then clickOK. Install the AD RMS role by using Server Manager To perform this procedure, you must be a member of the local Administrators group, or must have been delegated the appropriate authority. To install the AD RMS role by using Server Manager: 1.ClickStart, point toAdministrative Tools, and then clickServer Manager. 2.In theRoles Summary section, clickAdd Roles, and then clickNext. 3.Select theActive Directory Rights Management Services check box, and then clickNext. 4.Complete the appropriate information in the AD RMS role wizard setup. 5.ClickInstall. 6.When the installation is complete, clickClose. Verify: 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 verify that the AD RMS cluster installation is working properly: 1.Log on to a server in the AD RMS cluster. 2.ClickStart, point to Administrative Tools, and then click Active Directory Rights Management Services. 3.Verify that the AD RMS cluster was added successfully by expanding the AD RMS cluster name. |
| Reference Links | Event ID 167 from Source Active Directory Rights Management Services |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.