none
"one or more ADRMS role services could not be configured: AD RMS setup failed because of invalid configuraion setting"

    Question

  • HI,

    when I configure AD RMS configuration it gives me error that "one or more  ADRMS role services could not be configured: AD RMS setup failed because of invalid configuraion setting". The user which I try to install is an administrator of DC and also the service account is a member of enterprise domain group. When I tried this on test environment it works perfectly but on production environment it didn't. pls help me with this....

    Thanks......

    I am using windows 2012 standard Server.. 
    Thursday, February 27, 2014 2:55 AM

All replies

  • Hi,

    I saw your in post in http://social.technet.microsoft.com/Forums/security/en-US/d2479a1e-c0e5-45b8-b71f-b981fb2ffffb/ad-rms-setup-failed-because-of-invalid-configuration-setting?forum=winserverDS

    Are you using a WSUS server in your production environment but not in your test lab?

    If so, disable WSUS on the production server and try the install again. (check for the WSUS entries in the registry http://www.windowsnetworking.com/articles-tutorials/windows-xp/Registry-Keys-Tweaking-Windows-Update-Part1.html)

    Regards,

    Lutz

    Thursday, February 27, 2014 5:31 PM
  • Hi Lutz,

    Thanks for reply.. Yes i have WSUS configured in my production environment.. Let me try to disable that & try...

    Regards

    Mukul

    I had tried after disable WSUS but no success.. same error...

    • Edited by Mukulpandey Friday, February 28, 2014 7:17 AM
    Friday, February 28, 2014 3:15 AM
  • Was RMS or ADRMS ever installed in the production environment?
    If this will be the root cluster, make sure there is no SCP entry in AD

    go into adsiedit.msc on a Domain Controller.

    Connect to the Configuration container (“Select a well known Naming Context: Configuration”

    navigate the following nodes: CN=Configuration [server name], CN=Services .   Check that  CN=RightsManagementServices, CN=SCP

    AND

    CN=RightsManagementServices

    are gone.

    Recreate them as empty:

    navigate to CN=Configuration [server name], CN=Services

    Right-Click in Services and choose NEW Object

    Select Container.

    Name the Container RightsManagementServices

    In that new container right-click  and choose NEW Object

    Select Container.

    Name the Container SCP

    Exit out of ADSIEdit.

    Then try again.  Also, I would go ahead and choose the option to not set the SCP during install and then set it once it's installed (just to simplify things further)

    Friday, February 28, 2014 7:22 PM
  • No, AD RMS never installed in my environment.... also no entry for CN=RightsManagementServices..

    I had tried with the option to set SCP later but no success..

    any other changes I can do?

    Regards 

    Mukul

    We have SharePoint 2013, Exchange 2013 and office communication server 2008 R2 configured at our production, and my DC is in 2012 server.
    Monday, March 03, 2014 3:16 AM
  • Are all (or any) of those roles running on the same server as the ADRMS server?
    Monday, March 03, 2014 5:33 PM
  • No.. all roles are running on separate computers...

    Tried ADRMS on DC as well as member server.. but same problem...

    Tuesday, March 04, 2014 3:09 AM
  • This is a weird one.  You can try some debugging and see if you can see a more specific error.

    1. Locate the
           machine.config files on the RMS server in the following directories:

                                
      <drive:>\Windows\Microsoft.NET\Framework64\v4.0.30319\CONFIG\



    1. Paste the following lines of code before the </configuration> tag:                           
      <system.diagnostics>
           <switches>
                 <add name="TMS Trace" value="4" />
           </switches>
      </system.diagnostics>


    1. Download dbgview.exe (http://technet.microsoft.com/en-us/sysinternals/bb896647).
    2. Launch dbgview.exe ason the Capture menu).
    3. Add the Role.  You should see debug info in debug View



    Thursday, March 06, 2014 5:04 PM
  • HI Eddie,

    Thanks for reply.. Pls find the debug log below... It says " Message: The 'http://tempuri.org/RMProvisionSettingsSchema.xsd:Domain' element is invalid - The value 'D' is invalid according to its datatype 'http://tempuri.org/RMProvisionSettingsSchema.xsd:WindowsDomainName' - The actual length is less than the MinLength value. "

    00000706 56.78187180 [11964] CallStack:Microsoft.RightsManagementServices.Configuration.HelperMethods.IsValidConfigSetting
    00000707 56.78187180 [11964] System.Xml.Schema.XmlSchemaValidationException
    00000708 56.78187180 [11964]         Message: The 'http://tempuri.org/RMProvisionSettingsSchema.xsd:Domain' element is invalid - The value 'D' is invalid according to its datatype 'http://tempuri.org/RMProvisionSettingsSchema.xsd:WindowsDomainName' - The actual length is less than the MinLength value.
    00000709 56.78187180 [11964]         StackTrace:    at Microsoft.RightsManagementServices.Configuration.HelperMethods.ProvisionSchemaValidationEventHandler(Object sender, ValidationEventArgs e)
    00000710 56.78187180 [11964]    at System.Xml.Schema.XmlSchemaValidator.CheckElementValue(String stringValue)
    00000711 56.78187180 [11964]    at System.Xml.Schema.XmlSchemaValidator.ValidateAtomicValue(String stringValue, XmlSchemaSimpleType& memberType)
    00000712 56.78187180 [11964]    at System.Xml.Schema.XmlSchemaValidator.InternalValidateEndElement(XmlSchemaInfo schemaInfo, Object typedValue)
    00000713 56.78187180 [11964]    at System.Xml.DocumentSchemaValidator.ValidateElement()
    00000714 56.78187180 [11964]    at System.Xml.DocumentSchemaValidator.ValidateNode(XmlNode node)
    00000715 56.78187180 [11964]    at System.Xml.DocumentSchemaValidator.ValidateElement()
    00000716 56.78187180 [11964]    at System.Xml.DocumentSchemaValidator.ValidateNode(XmlNode node)
    00000717 56.78187180 [11964]    at System.Xml.DocumentSchemaValidator.ValidateElement()
    00000718 56.78187180 [11964]    at System.Xml.DocumentSchemaValidator.ValidateNode(XmlNode node)
    00000719 56.78187180 [11964]    at System.Xml.DocumentSchemaValidator.ValidateElement()
    00000720 56.78187180 [11964]    at System.Xml.DocumentSchemaValidator.ValidateNode(XmlNode node)
    00000721 56.78187180 [11964]    at System.Xml.DocumentSchemaValidator.ValidateElement()
    00000722 56.78187180 [11964]    at System.Xml.DocumentSchemaValidator.ValidateNode(XmlNode node)
    00000723 56.78187180 [11964]    at System.Xml.DocumentSchemaValidator.ValidateNode(XmlNode node)
    00000724 56.78187180 [11964]    at System.Xml.DocumentSchemaValidator.Validate(XmlNode nodeToValidate)
    00000725 56.78187180 [11964]    at System.Xml.XmlDocument.Validate(ValidationEventHandler validationEventHandler, XmlNode nodeToValidate)
    00000726 56.78187180 [11964]    at Microsoft.RightsManagementServices.Configuration.HelperMethods.IsValidConfigSetting(ConfigOperationType configOperation)
    00000727 56.78187180 [11964]  
    00000728 56.78199768 [11964] -Microsoft.RightsManagementServices.Configuration.Commands.InstallADRMS.ProcessRecord
    00000729 56.84855270 [11964] +Microsoft.RightsManagementServices.Configuration.DeploymentPSProvider.RemoveDrive
    00000730 56.84864807 [11964] -Microsoft.RightsManagementServices.Configuration.DeploymentPSProvider.RemoveDrive
    00000731 56.86203766 [23784] +[Tier2Diagnostic]  
    00000732 56.86203766 [23784] CallStack:System.Windows.Threading.ExceptionWrapper.InternalRealCall
    00000733 56.86203766 [23784] Microsoft.ADRoles.ServerManager.Common.PowerShellRemoting.RemotingException
    00000734 56.86203766 [23784]         Message: AD RMS setup failed because of invalid configuration settings.
    00000735 56.86203766 [23784]         StackTrace:    at Microsoft.ADRoles.ServerManager.Common.PowerShellRemoting.WorkflowExecutor.ExecuteCommand(Command workflowCommand, EventHandler`1 outputEventsHandler, EventHandler`1 progressEventHandler, EventHandler`1 finishedEventHandler, EventHandler`1 warningEventHandler, EventHandler`1 errorEventHandler)
    00000736 56.86203766 [23784]    at Microsoft.RightsManagementServices.Deployment.M3PPowerShellEngine.ExecuteCommand(CmdletProperties propertyBag, EventHandler`1 outputHandler, EventHandler`1 progressStatusHandler, EventHandler`1 progressPercentageHandler, EventHandler`1 warningHandler, EventHandler`1 errorHandler)
    00000737 56.86203766 [23784]    at Microsoft.RightsManagementServices.Deployment.AbstractPowerShellProvider.<>c__DisplayClass3`1.<ExecuteAsynchronously>b__0(Object sender, DoWorkEventArgs eventArgs)
    00000738 56.86203766 [23784]    at Microsoft.RightsManagementServices.Configuration.AbortableBackgroundWorker.OnDoWork(DoWorkEventArgs e)
    00000739 56.86203766 [23784]    at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    00000740 56.86203766 [23784]   + System.Management.Automation.RemoteException
    00000741 56.86203766 [23784]   +         Message: AD RMS setup failed because of invalid configuration settings.
    00000742 56.86203766 [23784]   +         StackTrace:  
    00000743 56.86203766 [23784]  
    00000744 56.86225891 [23784] +[Tier2Diagnostic] One or more AD RMS role services could not be configured:
    00000745 56.86225891 [23784] CallStack:Microsoft.RightsManagementServices.Configuration.AbortableBackgroundWorker`1+<>c__DisplayClass1.<Run>b__0
    00000746 56.86225891 [23784] Microsoft.ADRoles.ServerManager.Common.PowerShellRemoting.RemotingException
    00000747 56.86225891 [23784]         Message: AD RMS setup failed because of invalid configuration settings.
    00000748 56.86225891 [23784]         StackTrace:    at Microsoft.ADRoles.ServerManager.Common.PowerShellRemoting.WorkflowExecutor.ExecuteCommand(Command workflowCommand, EventHandler`1 outputEventsHandler, EventHandler`1 progressEventHandler, EventHandler`1 finishedEventHandler, EventHandler`1 warningEventHandler, EventHandler`1 errorEventHandler)
    00000749 56.86225891 [23784]    at Microsoft.RightsManagementServices.Deployment.M3PPowerShellEngine.ExecuteCommand(CmdletProperties propertyBag, EventHandler`1 outputHandler, EventHandler`1 progressStatusHandler, EventHandler`1 progressPercentageHandler, EventHandler`1 warningHandler, EventHandler`1 errorHandler)
    00000750 56.86225891 [23784]    at Microsoft.RightsManagementServices.Deployment.AbstractPowerShellProvider.<>c__DisplayClass3`1.<ExecuteAsynchronously>b__0(Object sender, DoWorkEventArgs eventArgs)
    00000751 56.86225891 [23784]    at Microsoft.RightsManagementServices.Configuration.AbortableBackgroundWorker.OnDoWork(DoWorkEventArgs e)
    00000752 56.86225891 [23784]    at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    00000753 56.86225891 [23784]   + System.Management.Automation.RemoteException
    00000754 56.86225891 [23784]   +         Message: AD RMS setup failed because of invalid configuration settings.
    00000755 56.86225891 [23784]   +         StackTrace:  
    00000756 56.86225891 [23784]  
    00000757 56.86357880 [23784] PageLeave: Progress
    00000758 56.86389160 [23784] ErrorNotification: <null>
    00000759 56.86653519 [23784] PageEnter: Results
    00000760 56.89128876 [23784] +[Tier2Diagnostic] One or more AD RMS role services could not be configured:
    00000761 56.89128876 [23784] CallStack:Microsoft.RightsManagementServices.Deployment.ViewModel.ResultsPageViewModel.SetUpResultDetails
    00000762 56.89128876 [23784] System.Management.Automation.ApplicationFailedException
    00000763 56.89128876 [23784]         Message: One or more AD RMS role services could not be configured:
    00000764 56.89128876 [23784]         StackTrace:  
    00000765 56.89128876 [23784]   + Microsoft.ADRoles.ServerManager.Common.PowerShellRemoting.RemotingException
    00000766 56.89128876 [23784]   +         Message: AD RMS setup failed because of invalid configuration settings.
    00000767 56.89128876 [23784]   +         StackTrace:    at Microsoft.ADRoles.ServerManager.Common.PowerShellRemoting.WorkflowExecutor.ExecuteCommand(Command workflowCommand, EventHandler`1 outputEventsHandler, EventHandler`1 progressEventHandler, EventHandler`1 finishedEventHandler, EventHandler`1 warningEventHandler, EventHandler`1 errorEventHandler)
    00000768 56.89128876 [23784]    at Microsoft.RightsManagementServices.Deployment.M3PPowerShellEngine.ExecuteCommand(CmdletProperties propertyBag, EventHandler`1 outputHandler, EventHandler`1 progressStatusHandler, EventHandler`1 progressPercentageHandler, EventHandler`1 warningHandler, EventHandler`1 errorHandler)
    00000769 56.89128876 [23784]    at Microsoft.RightsManagementServices.Deployment.AbstractPowerShellProvider.<>c__DisplayClass3`1.<ExecuteAsynchronously>b__0(Object sender, DoWorkEventArgs eventArgs)
    00000770 56.89128876 [23784]    at Microsoft.RightsManagementServices.Configuration.AbortableBackgroundWorker.OnDoWork(DoWorkEventArgs e)
    00000771 56.89128876 [23784]    at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    00000772 56.89128876 [23784]       + System.Management.Automation.RemoteException
    00000773 56.89128876 [23784]       +         Message: AD RMS setup failed because of invalid configuration settings.
    00000774 56.89128876 [23784]       +         StackTrace:  
    00000775 56.89128876 [23784]  
    00000776 56.89152908 [23784] +[Tier2Diagnostic] OnOperationError
    00000777 56.89152908 [23784] CallStack:Microsoft.RightsManagementServices.Configuration.AbortableBackgroundWorker`1+<>c__DisplayClass1.<Run>b__0
    00000778 56.89152908 [23784] System.Management.Automation.ApplicationFailedException
    00000779 56.89152908 [23784]         Message: One or more AD RMS role services could not be configured:
    00000780 56.89152908 [23784]         StackTrace:  
    00000781 56.89152908 [23784]   + Microsoft.ADRoles.ServerManager.Common.PowerShellRemoting.RemotingException
    00000782 56.89152908 [23784]   +         Message: AD RMS setup failed because of invalid configuration settings.
    00000783 56.89152908 [23784]   +         StackTrace:    at Microsoft.ADRoles.ServerManager.Common.PowerShellRemoting.WorkflowExecutor.ExecuteCommand(Command workflowCommand, EventHandler`1 outputEventsHandler, EventHandler`1 progressEventHandler, EventHandler`1 finishedEventHandler, EventHandler`1 warningEventHandler, EventHandler`1 errorEventHandler)
    00000784 56.89152908 [23784]    at Microsoft.RightsManagementServices.Deployment.M3PPowerShellEngine.ExecuteCommand(CmdletProperties propertyBag, EventHandler`1 outputHandler, EventHandler`1 progressStatusHandler, EventHandler`1 progressPercentageHandler, EventHandler`1 warningHandler, EventHandler`1 errorHandler)
    00000785 56.89152908 [23784]    at Microsoft.RightsManagementServices.Deployment.AbstractPowerShellProvider.<>c__DisplayClass3`1.<ExecuteAsynchronously>b__0(Object sender, DoWorkEventArgs eventArgs)
    00000786 56.89152908 [23784]    at Microsoft.RightsManagementServices.Configuration.AbortableBackgroundWorker.OnDoWork(DoWorkEventArgs e)
    00000787 56.89152908 [23784]    at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    00000788 56.89152908 [23784]       + System.Management.Automation.RemoteException
    00000789 56.89152908 [23784]       +         Message: AD RMS setup failed because of invalid configuration settings.
    00000790 56.89152908 [23784]       +         StackTrace:  
    00000791 56.89152908 [23784]  



    Friday, March 07, 2014 4:07 AM
  • Someone has the answer for this..? 
    Tuesday, March 25, 2014 5:43 AM
  • The code appears to enforce a minimum domain length of two characters.
    Tuesday, March 25, 2014 7:53 PM
  • It means I have to reconfigure my domain.. I can't do this on my production environment..

    any other alternative???

    Wednesday, March 26, 2014 5:44 AM
  • Other than opening a case with Microsoft to investigate changing this behavior, there really isn't a way to work around it. The RFC doesn't appear to have any minimum character length for the domain, so I would think you have good standing to say that this is a bug.
    Wednesday, April 02, 2014 9:47 PM
  • hi Eddie,

    thanks for reply.. Please tell me how could I raise a ticket in Microsoft because i don't have a MSDN or technet subscription for raise a ticket. There is only one option to raise a complaint on chargeable basis, but if this is a Microsoft bug than why should I pay for this.. 

    Thanks

    Mukul

    Monday, April 07, 2014 3:56 AM
  • It's not ideal, but the way it works (or at least what I understand) is that they still need a credit card to open the incident, but once they associate a bug it will be flagged to not change (charge happens on case closure).  It still may take a while to get it fixed.  It's likely this was done for a reason, so there may be some more complex underlying issue that has to be resolved.

    Monday, April 07, 2014 11:06 PM
  • Hi Eddie,

    I had talked to Microsoft customer care, they are asking for either gold subscription or technet Id to raise a ticket.

     

    Friday, April 11, 2014 6:54 AM