Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via zextras.com by Unknown author, 1 year ago
This exception has no message.
javax.naming.directory.InvalidAttributeIdentifierException: [LDAP: error code 17 - zimbraFeatureContactsDetailedSearchEnabled: attribute type undefined]; remaining name 'cn=ugbc parkrestored30c4466871c44f949eb369f5e5a4948a,cn=cos,cn=zimbra'	at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3110)	at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2987)	at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2794)	at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1455)	at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:255)	at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:172)	at javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.java:153)	at com.zimbra.cs.account.ldap.ZimbraLdapContext.modifyAttributes(ZimbraLdapContext.java:648)	at com.zimbra.cs.account.ldap.LdapUtil.modifyAttrs(LdapUtil.java:421)	at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrsInternal(LdapProvisioning.java:338)	at com.zimbra.cs.account.AccountServiceException.INVALID_ATTR_NAME(AccountServiceException.java:169)	at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrsInternal(LdapProvisioning.java:341)	at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrs(LdapProvisioning.java:316)	at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrs(LdapProvisioning.java:297)	at com.zimbra.cs.account.Provisioning.modifyAttrs(Provisioning.java:301)	at com.zimbra.cs.account.Cos.modify(Cos.java:43)