Exchangemaster GmbH company logo

Exchangemaster GmbH - A Swiss IT Consultancy
Services
References
Partners
Contact
Getting Started
FAQs
Presentations
Articles
Community
Search
Popular
Tell-a-Friend
Follow Me

Follow exchangemaster on Twitter

Who's Online
We have 51 guests online
Syndicate
FAQ 000110 - DAG creation failes with error you must provide a value for this property PDF Print E-mail
User Rating: / 50
PoorBest 
Written by Dejan Foro   
May 24, 2013 at 03:33 PM

This article applies to:

Exchange 2010 SP3

Windows Server 2008 R2

Windows Server 2012 

 

PROBLEM

When you try to create a new Database Availability Group (DAG) the following error is reported:


Error: You must provide a value for this property

 

During the process of a Database Availability Group (DAG) creation, the DAG wizard will create a Cluster Name Object (CNO) which is basically a computer account in Active Directory (AD) which is named identically as the DAG name. In regard to this following ca 

 

CAUSE 1

Account with such name already exists in Active Directory. It is either a leftover from a deleted DAG or you have accidentally created a DAG with a name that already exists in the Active Directory. 

 

SOLUTION

Delete the existing CNO account. If this is not possible select a different name for your DAG.

 

 

CAUSE 2

The CNO account is created in Active Directory Organizational Unit OU other then Computers or in an Organizational Unit where you don't have sufficient right to create or modify computer objects.

 

SOLUTION

In such case the CNO account has to be pre-staged manually. For instructions see TechNet Article :Pre-stage the Cluster Name Object for a Database Availability Group

 

 

CAUSE 3

If you are installing Exchange 2010 in a Windows Server 2012 Active Directory, due to the change in AD permissions, the Exchange DAG wizard will not be able to create the account.

 

SOLUTION 

In such case the CNO account has to be pre-staged manually. For instructions see TechNet Article :Pre-stage the Cluster Name Object for a Database Availability Group

 

Last Updated ( May 24, 2013 at 02:34 PM )
<Previous   Next>