• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 539
  • Last Modified:

Problems deploying microsoft exchange 2010

When I try to add a mailbox database I receive this error. This is a new installation of exchange. I have set the preferred DC. Not sure what is happening. Any feedback is appreciated.
ss.png
0
J C
Asked:
J C
  • 4
1 Solution
 
Adam BrownSr Solutions ArchitectCommented:
I think you might have added the wrong screenshot. That shows the successful Outlook configuration screen.
0
 
J CAuthor Commented:
You're right will correct shortly
0
 
J CAuthor Commented:
Correct screenshot
ss.jpg
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
pradeep7880Commented:
Exchange 2010 Error New MailboxDatabase 000020B5

The Command
New-MailboxDatabase -Server 'GEMINI1' -NAME 'domain_local'-EdbFilePath 'K:\MailBoxDatabase\domain_local\domain_local.ebd'-LogFolderPath 'L:\MailboxLogs\domain_local' -Verbose

The Error
Active Directory operation failed on server2.domain.local. This erroris not retriable. Addition information: The name reference is invalid.
This may be caused by replication latency between Active Directory domain controllers.
Active directory response: 000020B5: AtrErr: DSID-03152804, #1: 0: 000020B5: DSID-03152804, Problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 992e8635 (homeMDB)
+ CategoryInfo : NotSpecified: (0:Int32) [New-MailboxDatabase], ADOperationException
+ FullyQualifiedErrorId: 31d36CF7, Microsoft.Exchange.Management.SystemConfigurationTasks.NewMailboxDatabase


The Reason
Replication time between domain controllers will cause this issue, to keep this from happening In a multi domain enviorment the Configuration Domain Controller and the Preferred Domain Controllers settings in Exchange 2010 should be set to the same server

The Fix
get-adserversettings
set-adserversettings -preferredserver server1.domain.local
set-adserversettings -configurationdomaincontroller server1.domain.local
0
 
J CAuthor Commented:
I transferred all of the FSMO roles to the DC that the exchange 2010 server could communicate with. I reinstalled exchange 2010 with sp1 and did not run into this problem a second time after reinstalling.
0
 
J CAuthor Commented:
The responses did not solve the problem I was having. I had already tried setting the preferredDNS server.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now