IBM Support

Missing objectClass in VMM configuration causes "LDAP: error code 2 - Bad search filter".

Technote (FAQ)


The WebSphere Application Server Deployment Manager (WSAS DMGR) and WebSphere Portal cannot be stopped. Users cannot log in to the IBM Websphere Integrated Solutions Console (ISC) or IBM Websphere Portal user interface. SystemOut.log records the following exception: search(String, String, Object[], SearchControls)
                        CWWIM4520E  The 'javax.naming.CommunicationException: [LDAP: error code 2 - Bad search filter]; Remaining name: 'o=test,dc=mycompany,dc=com'; Resolved object: 'com.sun.jndi.ldap.LdapCtx@3c923c92'' naming exception occurred during processing.

Why does this happen and how can I recover from this issue?


The stanza for PersonAccount entity type in wimconfig.xml is missing the objectClass:

<config:ldapEntityTypes name="PersonAccount" searchFilter=""/>


Back up profile/config/cells/cellname/wim/config/wimconfig.xml. Then add the appropriate objectClass for the PersonAccount entity type, save the wimconfig.xml, and restart the server.

For example, in an environment using IBM® Tivoli® Directory Server (ITDS) as the LDAP, change it to:

<config:ldapEntityTypes name="PersonAccount" searchFilter="">

(In a clustered environment, the change should be made to copy of this file in the <dmgr_profile> on the dmgr node and propagated to the Portal nodes.)

Document information

More support for: WebSphere Portal
VMM - Virtual Member Manager

Software version: 6.1, 7.0, 8.0

Operating system(s): AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS

Reference #: 1469971

Modified date: 12 November 2014

Translate this page: