cyberleo2000
asked on
LDAP error while installing exchange 2007
My exchange 2007 install stops with this error -
Setup encountered a problem while validating the state of Active Directory: An Active Directory error 0x51 occurred when trying to check server 'MYEXCHANGESERVER.MYDOMAIN .com:3268' suitability: 'The LDAP server is unavailable.'.
I've confirmed that there is a domain controller which is also configured to be a global catalog in the site that the exchange server is in using AD Sites and Services.
Is this a replication error? Am I being too hasty in my installation?
thank you.
Setup encountered a problem while validating the state of Active Directory: An Active Directory error 0x51 occurred when trying to check server 'MYEXCHANGESERVER.MYDOMAIN
I've confirmed that there is a domain controller which is also configured to be a global catalog in the site that the exchange server is in using AD Sites and Services.
Is this a replication error? Am I being too hasty in my installation?
thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
all cluster resources are online so i went ahead and ignored this so called "error" and installed the passive node. it installed successfully. i am not applying SP3 and then will apply RU10, then do the active node.
ASKER
well that didn't work, so we're back to
The computer account 'EXCHANGECMS' was created on the domain controller '\\DC.mydomain.com', but has not replicated to the desired domain controller (LocalDC.mydomain.com) after waiting approximately 60 seconds. Please wait for the account to replicate and re-run setup /newcms.
The computer account 'EXCHANGECMS' was created on the domain controller '\\DC.mydomain.com', but has not replicated to the desired domain controller (LocalDC.mydomain.com) after waiting approximately 60 seconds. Please wait for the account to replicate and re-run setup /newcms.
I've written such a big thread to ensure that you're issue is understood and detected and you're not even giving it an attempt to work on it. What further can i say?
Regards,
Exchange_Geek
Regards,
Exchange_Geek
ASKER
The servers were moved to the same site as All my other exchange servers. That solved all the replication problems, for now.
ASKER
setup.com /newcms /cmsname:CMSSERVER /cmsipaddfress:xxx.xx.xx.x
I am looking at this article but I have not been given the ok to try the workaround yet by my manager. http://support.microsoft.com/kb/947345
Out AD admins are looking for another solution