Cannot Enable Directory Service on MWS

When I enable the Directory Service on MWS, it get disable immediately with following error in MWS _problems.log.
We are using MWS 7.1.1 and connecting to AD Server for authentication.

netscape.ldap.LDAPException: error result (49); 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 775, vece
at netscape.ldap.LDAPConnection.checkMsg(LDAPConnection.java:4855)
at netscape.ldap.LDAPConnection.simpleBind(LDAPConnection.java:1750)
at netscape.ldap.LDAPConnection.authenticate(LDAPConnection.java:1248)
at netscape.ldap.LDAPConnection.authenticate(LDAPConnection.java:1197)
at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:941)
at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:889)
at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:1036)
at com.webMethods.portal.portlet.wm_xt_ldapdirsvc.service.connection.LdapPooledObjectManager.createLDAPConnection(LdapPooledObjectManager.java:192)
at com.webMethods.portal.portlet.wm_xt_ldapdirsvc.service.connection.LdapPooledObjectManager.create(LdapPooledObjectManager.java:95)
at com.webMethods.portal.system.pool.impl.DefaultPooledObjectManager.create(DefaultPooledObjectManager.java:55)
at com.webMethods.portal.system.pool.impl.SelfCleaningObjectPool.initialize(SelfCleaningObjectPool.java:73)
at com.webMethods.portal.portlet.wm_xt_ldapdirsvc.service.LdapDirService.onInitialize(LdapDirService.java:272)
at com.webMethods.portal.service.dir.impl.DirService.init(DirService.java:92)
at com.webMethods.portal.service.dir.impl.DirSystem.initDirComponent(DirSystem.java:446)
at com.webMethods.portal.service.dir.impl.DirSystem.getDirectoryServiceFromThingID(DirSystem.java:304)
at com.webMethods.portal.portlet.wm_userprofilewiring.UserprofilePortletType.initCustomPortletInfo(UserprofilePortletType.java:153)
at com.webMethods.portal.portlet.wm_userprofilewiring.UserprofilePortletType.getPortletInfo(UserprofilePortletType.java:191)
at com.webMethods.portal.service.portlet.impl.PortletProvider.getPortletInfo(PortletProvider.java:322)
at com.webMethods.portal.mech.storage.impl.BasicMechanics.canView(BasicMechanics.java:185)
at com.webMethods.portal.mech.portlet.impl.PortletMechanics.getWiredProperty(PortletMechanics.java:490)
at com.webMethods.portal.mech.portlet.impl.PortletMechanics.getAllWiredProperties(PortletMechanics.java:508)
at com.webMethods.portal.mech.portlet.impl.PortletMechanics.resolveWiring(PortletMechanics.java:555)
at com.webMethods.portal.mech.storage.page.PortletHelper.initializeWiredProperties(PortletHelper.java:224)
at com.webMethods.portal.mech.storage.page.PortletHelper.getInitializedBean(PortletHelper.java:334)
at com.webMethods.portal.mech.storage.page.PortletHelper.getInitializedBean(PortletHelper.java:319)
at com.webMethods.portal.mech.storage.page.PortletHelper.renderContent(PortletHelper.java:374)
at com.webMethods.portal.framework.presentation.renderers.ShellSubRenderer.renderPortlet(ShellSubRenderer.java:158)
at com.webMethods.portal.framework.presentation.renderers.PortalPageSubRenderer.renderColumn(PortalPageSubRenderer.java:206)
at com.webMethods.portal.framework.presentation.renderers.PortalPageSubRenderer.renderRow(PortalPageSubRenderer.java:167)
at com.webMethods.portal.framework.presentation.renderers.PortalPageSubRenderer.renderContent(PortalPageSubRenderer.java:128)
at com.webMethods.portal.framework.presentation.renderers.ShellSubRenderer.subrender(ShellSubRenderer.java:80)
at com.webMethods.portal.framework.presentation.renderers.DefaultRenderer.renderPageStart(DefaultRenderer.java:224)
at com.webMethods.portal.framework.presentation.renderers.DefaultRenderer.render(DefaultRenderer.java:187)
at com.webMethods.portal.framework.presentation.PresentationManager.handlePres(PresentationManager.java:359)
at com.webMethods.portal.framework.dispatch.DispatchManager.pres(DispatchManager.java:618)
at com.webMethods.portal.framework.dispatch.DispatchManager.handle(DispatchManager.java:458)
at com.webMethods.portal.framework.dispatch.DispatchManager.handleDispatch(DispatchManager.java:371)
at com.webMethods.portal.framework.impl.PortalServlet.service(PortalServlet.java:242)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
at com.webMethods.portal.framework.impl.NTLMFilter.doFilter(NTLMFilter.java:50)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at com.webMethods.caf.faces.servlet.GZIPFilter.doFilter(GZIPFilter.java:34)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at com.webMethods.portal.webApplication.WmWebAppContext.handle(WmWebAppContext.java:159)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
2011-06-23 12:56:20 EDT (portlet : WARN) [RID:21] - Setting returnUrl inside render method is not permitted
2011-06-23 13:04:05 EDT (Framework : WARN) [RID:25] - Disabling directory service: US_LINK
2011-06-23 13:04:05 EDT (Framework : WARN) [RID:25] - Unable to create new LDAP connection

I found the resolution.

After checking with Active Directory Administrator, we found that the Account was locked. It worked well after unlocking the Account.

Thanks.