[SOLVED] Unable to add a new account.

[Stergil]

When attempting to add a new account I get the following error:

Message: createAccount invalid attr value: [LDAP: error code 21 - objectClass: value #3 invalid per syntax] Error code: 
account.INVALID_ATTR_VALUE Method: 
ZmCsfeCommand.prototype.invoke Details:soap:Sender

LDAP service is running. This is the first user I'm attempting to add since upgrading to v5 a couple of weeks ago.

In searching the forums I saw a few mentions of samba & posix accounts. In an earlier release I played around with the samba PDC integration. However, I've upgraded several versions since then w/o re-issuing the necessary configuration changes. I currently have no posix or samba options in the add account dialoge.

Any direction would be appreciated.

[Stergil]

I've upgraded from 5.0 to 5.0.2 and am having the same result.

I've also followed suggestions in another thread to see if I had a deadlocks, which I didn't. (Creating account problem)

I'm continuing to browse the forums in hopes of finding something I've over-looked.

[Stergil]

tailing /opt/zimbra/log/mailbox.log when the failure occurs results in the following:

2008-02-06 20:33:40,089 INFO  [btpool0-8] [name=addr@fourtysix.com;ip=192.168.1.100;ua=ZimbraWebClient - FF3.0 (Win);] SoapEngine - handler exception
com.zimbra.cs.account.AccountServiceException: createAccount invalid attr value: [LDAP: error code 21 - objectClass: value #3 invalid per syntax]
Code:account.INVALID_ATTR_VALUE
        at com.zimbra.cs.account.AccountServiceException.INVALID_ATTR_VALUE(AccountServiceException.java:153)
        at com.zimbra.cs.account.ldap.LdapUtil.createEntry(LdapUtil.java:1228)
        at com.zimbra.cs.account.ldap.LdapProvisioning.createAccount(LdapProvisioning.java:760)
        at com.zimbra.cs.account.ldap.LdapProvisioning.createAccount(LdapProvisioning.java:609)
        at com.zimbra.cs.service.admin.CreateAccount.handle(CreateAccount.java:58)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:342)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:208)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:113)
        at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:272)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:174)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
        at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
        at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
        at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
        at org.mortbay.jetty.handler.RewriteHandler.handle(RewriteHandler.java:176)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
        at org.mortbay.jetty.Server.handle(Server.java:313)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Caused by: javax.naming.directory.InvalidAttributeValueException: [LDAP: error code 21 - objectClass: value #3 invalid per syntax]; remaining name 'uid=test,ou=people,dc=fourtysix,dc=com'
        at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3018)
        at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2951)
        at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2758)
        at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:774)
        at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
        at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
        at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:183)
        at com.zimbra.cs.account.ldap.LdapUtil.createEntry(LdapUtil.java:1220)
        ... 33 more

[quanah]

Are you able to add an account from the commandline as the zimbra user, using the "zmprov ca" command?

It's complaining that objectClass #4 is not valid during your user creation (they are 0 based in the numbering, so that's why value#3 is objectClass #4 ).

I note that my object's only have 3 objectClasses, so I wonder if the samba stuff got triggered somehow.

--Quanah

[Stergil]

No luck.

zimbra@zimbra:~$ zmprov ca test@fourtysix.com testtest
ERROR: account.INVALID_ATTR_VALUE (createAccount invalid attr value: [LDAP: error code 21 - objectClass: value #3 invalid per syntax])

fwiw I also tried the permissions fix that was suggested in another thread, same result.

[Greg]

Please run this command to see what values are in zimbraAccountExtraObjectClass config attribute:

/opt/zimbra/bin/zmprov gacf | grep zimbraAccountExtraObjectClass

[Stergil]

Good one. Apparently the samba stuff is still hanging around.

zimbra@zimbra:~$ /opt/zimbra/bin/zmprov gacf | grep zimbraAccountExtraObjectClass
zimbraAccountExtraObjectClass: amavisAccount
zimbraAccountExtraObjectClass: posixAccount
zimbraAccountExtraObjectClass: sambaSamAccount

I undeployed the admin extensions long ago, and they're not in the list. Nor do I get Samba or Posix options when adding/editing an account.

How can I go about removing the extra objects properly?

[Stergil]

I re-deployed and then undeployed the samba & posix admin extensions attempting to remove the objects that it adds/creates.

This didn't seem to help. I've not had much luck finding any direction in the wiki or forums.

Does anyone have some advice on how to handle this situation?

[schmicha]

Hello

I have the same Issue in 5.0.1 GA:

our zimbraAccountExtraObjects are:

 zmprov gacf | grep ObjectClass
     zimbraAccountExtraObjectClass: amavisAccount
     zimbraAccountExtraObjectClass: posixAccount
     zimbraAccountExtraObjectClass: sambaSamAccount
     zimbraAccountExtraObjectClass: sambaAccount

I remove the ExtraObjectClass with this:

 zmprov mcf -zimbraAccountExtraObjectClass posixAccount
 zmprov mcf -zimbraAccountExtraObjectClass sambaAccount
 zmprov mcf -zimbraAccountExtraObjectClass sambaSamAccount

After removing the objects I can add new accounts

[Stergil]

Great find schmicha, that worked perfectly. Thanks loads!!

How'd you dig up that solution btw? I spent hours digging through the wiki & forums without coming across that.