While creating a new mailbox database in Exchange Server 2013 you may encounter the following error.
[PS] C:\>New-MailboxDatabase DB07 -Server E15MB1 -EdbFilePath E:DB07DB07.edb -LogFolderPath F:DB07
An inconsistency in the Active Directory was detected: Database ‘DB07’ is expected to be in a database availability
group but the value for its MasterServerOrAvailabilityGroup property (‘E15MB1’) is not valid. This may be a defect in
the product and this should be reported to Microsoft Product Support.
+ CategoryInfo : InvalidOperation: (DB07:MailboxDatabase) [New-MailboxDatabase], InconsistentADException
+ FullyQualifiedErrorId : [Server=E15MB1,RequestId=b008e2ed-bbd4-465e-9681-b8b64b734db0,TimeStamp=16/02/2014 1:07:
18 PM] 8006979E,Microsoft.Exchange.Management.SystemConfigurationTasks.NewMailboxDatabase
+ PSComputerName : e15mb1.exchange2013demo.com
This appears to be a bug that, at least in my specific case, occurs when an Exchange 2013 mailbox server has been removed as a member of a database availability group, and then a mailbox database is created on that mailbox server.
Despite the error message the database object is created in Active Directory, however the database and log folder paths are not created on the server and the database itself can’t be mounted.
[PS] C:\>Mount-Database DB07 Failed to mount database "DB07". Error: An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: An error occurred while preparing to mount database 'DB07'. Error: An I/O error occurred while attempting to enumerate log files in directory 'F:DB07'. Error 0x3 (The system cannot find the path specified) from Windows API 'FindFirstFile'. [Database: DB07, Server: E15MB1.exchange2013demo.com] + CategoryInfo : InvalidOperation: (DB07:ADObjectId) [Mount-Database], InvalidOperationException + FullyQualifiedErrorId : [Server=E15MB1,RequestId=a930a445-11de-4fba-a648-881662a8e5f7,TimeStamp=16/02/2014 1:11: 38 PM] FC4C3D31,Microsoft.Exchange.Management.SystemConfigurationTasks.MountDatabase + PSComputerName : e15mb1.exchange2013demo.com
In my testing I found that the database creation error would not appear if I first re-added the mailbox server to a DAG (any DAG, not necessarily the one it was previously a member of). Obviously that is not an ideal solution, so fortunately it also appears that the new database will be mountable if you manually create the log folder path on the server.
[PS] C:\>New-Item -Type Directory -Path (Get-MailboxDatabase DB07).LogFolderPath
After creating the log folder path the database should mount successfully.
[PS] C:\>Mount-Database DB07 [PS] C:\>Get-MailboxDatabase DB07 | Test-MAPIConnectivity MailboxServer Database Result Error ------------- -------- ------ ----- E15MB1 DB07 Success
I am not sure exactly which versions of Exchange Server 2013 would exhibit this behaviour, as I only have Exchange 2013 CU3 available to me at the moment.