Users can't login after upgrade to 6.5.2

I just recently upgraded the portal from 6.5.0 to 6.5.2, the upgrade finished successfully. However some users are unable to login to the portal, the error message they get is that they have typed in invalid password, however the password is correct. The users are defined in an external Active Directory. This only happens for some users and not others. It seems definately to be a problem with 6.5.2 since the users can still login to the old portal running 6.5.0, even though the Active Directory is the same between these two portals. Do you have any idea what could be the problem. The error message I get in the log when the user can’t login is this (Username and IP are blanked with ‘x’):

netscape.ldap.LDAPException: error result (49); 80090308: LdapErr: DSID-0C09030F, comment: AcceptSecurityContext error, data 52e, vece
at netscape.ldap.LDAPConnection.checkMsg(LDAPConnection.java:4852)
at netscape.ldap.LDAPConnection.internalBind(LDAPConnection.java:1757)
at netscape.ldap.LDAPConnection.authenticate(LDAPConnection.java:1294)
at netscape.ldap.LDAPConnection.authenticate(LDAPConnection.java:1303)
at netscape.ldap.LDAPConnection.authenticate(LDAPConnection.java:1221)
at com.webMethods.portal.portlet.wm_xt_ldapdirsvc.service.LdapDirPrincipalProvider.authenticateUser(LdapDirPrincipalProvider.java:53)
at com.webMethods.portal.mech.dir.impl.DirSystemMechanics$3.visit(DirSystemMechanics.java:311)
at com.webMethods.portal.mech.dir.impl.DirSystemMechanics.visitDirServices(DirSystemMechanics.java:404)
at com.webMethods.portal.mech.dir.impl.DirSystemMechanics.authenticateUser(DirSystemMechanics.java:306)
at com.webMethods.portal.bizPolicy.command.dir.AuthenticateUser._authenticateUser(AuthenticateUser.java:116)
at com.webMethods.portal.bizPolicy.command.dir.AuthenticateUser.authenticateUser(AuthenticateUser.java:97)
at com.webMethods.portal.bizPolicy.biz.dir.impl.DirSystemBizPolicy.authenticateUser(DirSystemBizPolicy.java:37)
at com.webMethods.portal.framework.session.handlers.Validate.handle(Validate.java:147)
at com.webMethods.portal.framework.session.SessionManager.handleSession(SessionManager.java:157)
at com.webMethods.portal.framework.dispatch.DispatchManager.initSession(DispatchManager.java:622)
at com.webMethods.portal.framework.dispatch.DispatchManager.handleDispatch(DispatchManager.java:304)
at com.webMethods.portal.framework.impl.PortalServlet.service(PortalServlet.java:176)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:356)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:342)
at com.webMethods.portal.framework.impl.NTLMFilter.doFilter(NTLMFilter.java:50)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:334)
at com.webMethods.portal.framework.impl.CompressionFilter.doFilter(CompressionFilter.java:41)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:334)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:286)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1723)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:514)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1673)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:783)
at org.mortbay.http.ajp.AJP13Connection.handleNext(AJP13Connection.java:273)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:800)
at org.mortbay.http.ajp.AJP13Listener.handleConnection(AJP13Listener.java:204)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:454)
2007-06-19 08:32:23 GMT (Framework : INFO) [RID:849] - Validate::handle() - failed to login
2007-06-19 08:32:23 GMT (portalLogin : INFO) - User Login Failed: LoginName = ‘xxxx’, RemoteAddress = ‘xxx.xxx.xxx.xxx’, AuthType = ‘forms’

After a bit of googling it seems that the specific error code you are seeing is an invalid credentials error (http://forum.java.sun.com/thread.jspa?messageID=4227692)

I do know that we have released four Directory Services related fixes for 6.5.2, so after a quick review of the thread above, maybe you could try installing PRTL_6-5-2_Directory_Fix4?

Regards,
–mark