[
https://issues.apache.org/jira/browse/DIRSTUDIO-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712593#action_12712593
]
Stefan Seelmann commented on DIRSTUDIO-487:
-------------------------------------------
Hi James,
thanks for your report.
I checked the code. Your reported error "Can't set Base DN entry" is only
thrown in one case: if the namingContext is _not_ empty, but the DN can't be
parsed, I just added the code snippet below. I was able to reproduce your error
by setting namingContext to the space or newline character. Could you please
check if the namingcontexts of the domino server is really empty or if there is
some whitespace? Nevertheless it makes sense to trim() the value in the code...
--------------------------------------------------------------------------------------------------
if ( !"".equals( namingContext ) ) //$NON-NLS-1$
{
try
{
LdapDN dn = new LdapDN( namingContext );
...
}
catch ( InvalidNameException e )
{
monitor.reportError(
BrowserCoreMessages.model__error_setting_base_dn, e );
}
}
--------------------------------------------------------------------------------------------------
> empty namingcontexts causes javax.naming.InvalidNameException: Bad DN
> ---------------------------------------------------------------------
>
> Key: DIRSTUDIO-487
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-487
> Project: Directory Studio
> Issue Type: Improvement
> Affects Versions: 1.4.0
> Environment: Domino 7, Exchange 5.5
> Reporter: James Brown
> Priority: Minor
>
> When attempting to connect to domino server with an empty namingcontexts,
> using option to get base DNs from Root DSE (or leaving as empty), an error is
> generated and DIT does not display.
> Problem Occurred popup when fetching Base DNs:
> Error while fetching base DNs
> - Can't set Base DN entry
> - Bad DN :
> javax.naming.InvalidNameException: Bad DN :
> Modification Logs when connecting:
> #!RESULT ERROR
> #!CONNECTION ldap://10.x.x.x:389
> #!DATE 2009-04-24T12:04:10.247
> #!ERROR [LDAP: error code 89 - No given DN]
> dn:
> changetype: modify
> add: namingcontexts
> namingcontexts: o=mydomain
> -
> And Domino Root DSE:
> objectClass: top
> namingcontexts:
> subschemasubentry: cn=schema
> supportedextension: 1.3.6.1.4.1.1466.20037
> supportedextension: LanguageCodes
> supportedldapversion: 2
> supportedldapversion: 3
> supportedschemamechanisms: EXTERNAL
> vendorname: IBM Lotus Software
> vendorversion: Release 7.0.2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.