EJPSB0107E Domain Administrator not found

EJPSB0107E Domain Administrator not found exception appears in Portal server logs. This exception occurs during different scenarios,

1. After Clustering setup

2. After LDAP Configuration

3. After certain tasks during Portal clustering

What happens when we get the exception,

1. Portal Server fails to start

2. Portal Server console gives 404 message

3. Service Initialization errors pop up in System Out logs.

4. System Logs gets filled up with exception related to wpsadmins group problem.

IBM have given 2-3 resolutions for the same in the form of technotes. They are mostly related to adding the group name that is existing in the exception. Below are exception and resolution details.

Exception:

[8/10/16 16:16:37:686 IST] 00000024 Servlet       E com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of service failed.
com.ibm.wps.ac.DomainAdministratorNotFoundException: EJPSB0107E: Exception occurred while retrieving the identity of the domain admin user/admingroup cn=wpsadmins,o=defaultWIMFileBasedRealm.
at com.ibm.wps.ac.impl.AccessControlDataManagementServiceImpl.convertDNtoObjectID(AccessControlDataManagementServiceImpl.java:1163)
at com.ibm.wps.ac.impl.AccessControlDataManagementServiceImpl.access$000(AccessControlDataManagementServiceImpl.java:78)

Caused by: com.ibm.portal.puma.MemberNotFoundException: EJPSG0002E: Requested Member does not exist.cn=wpsadmins,o=defaultWIMFileBasedRealm
at com.ibm.wps.services.puma.PumaServiceImpl.findGroupById(PumaServiceImpl.java:381)
at com.ibm.wps.services.puma.Puma.findGroupById(Puma.java:406)
at com.ibm.wps.ac.impl.AccessControlDataManagementServiceImpl.convertDNtoObjectID(AccessControlDataManagementServiceImpl.java:1143)
… 40 more
Caused by: com.ibm.wps.um.exceptions.impl.MemberNotFoundExceptionImpl: com.ibm.websphere.wim.exception.EntityNotFoundException: CWWIM4001E  The ‘cn=wpsadmins,o=defaultWIMFileBasedRealm’ entity was not found.
at com.ibm.wps.um.VMMFilter.rethrowGet(VMMFilter.java:532)
at com.ibm.wps.um.FilterAdapter.get(FilterAdapter.java:166)

Resolution:

http://www-01.ibm.com/support/docview.wss?uid=swg21584591

http://www-01.ibm.com/support/docview.wss?uid=swg21392124

http://www-01.ibm.com/support/docview.wss?uid=swg21668460

Adding the wpsadmins group in Portal WAS console resolved the issue in my case. Adding the required user information within wimconfig.xml could be an ideal solution.