Return
-
Title
Exchange agent fails to activate with error LDAP: error code 34 - 0000208F: NameErr: DSID-031001F7 -
Description
Exchnage agent fails to activate.First it fails to retrieve data from Microsoft_LocalDomainInfo WMI class in DC and then encounters an LDAP Error
ERROR [IncomingMessage-7107] com.quest.agent.service.ldap.LDAPEndPoint - LDAPEndPoint.CN=Configuration,: [LDAP: error code 34 - 0000208F: NameErr: DSID-031001F7, problem 2006 (BAD_NAME), data 8350, best match of:
'CN=Configuration,'
]: []
javax.naming.InvalidNameException: CN=Configuration,: [LDAP: error code 34 - 0000208F: NameErr: DSID-031001F7, problem 2006 (BAD_NAME), data 8350, best match of:
'CN=Configuration,' -
Cause
Exchange agent cannot get the rootDomainNamingContext property from authenticating DC specified in Exchange agent properties
-
Resolution
- Point to a different Domain controller in Exchange agent properties and check if the error persists
- For WMI error when querying Microsoft_LocalDomainInfo, please run the RAD tool on authenticating Domian Controller to verify that all prerequisites are set correctly
- For LDAP error, run attached java tool to test the related LDAP query
- Check the firewall setting in both Domain controller and Exchange server
- Rule #1: need local ports 135, 139, 389 (or 636) and 445 opened.
Rule #2: need "Dynamic RPC" local ports opened.
For more information, see the following article: https://support.quest.com/SolutionDetail.aspx?id=SOL85903. - After applying above steps, please restart FglAM. As the LDAP command has failed once for environment setting, it will still return NULL for rootDomainNamingContext as Fglam JRE may have cached the results
-
Attachments