Friday, August 8, 2014

EJPSG0002E: Requested Member does not exist

You receive the following error message in the WebSphere Portal log: EJPSG0002E: Requested Member does not exist. uid=wpsadmin,o=defaultWIMFileBasedRealm/nullcauses initialization failures for portal server startup.

SystemOut.log says :

PortalCollect E com.ibm.hrl.portlets.WsPse.PortalCollectionsService PortalCollectionsService EJPJO0119E: Failed to initialize portal collections services.
java.lang.NoClassDefFoundError: com.ibm.wps.ac.impl.AccessControlDataManagement (initialization failure)
...
Caused by: java.lang.RuntimeException: Exception while loading dynamically re-ordered service class com.ibm.wps.ac.impl.AccessControlDataManagementService
...
Caused by: com.ibm.wps.ac.DomainAdministratorNotFoundException: EJPSB0107E: Exception occurred while retrieving the identity of the domain admin user/admingroup uid=wpsadmin,o=defaultWIMFileBasedRealm.
...
Caused by: com.ibm.portal.puma.MemberNotFoundException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,o=defaultWIMFileBasedRealm
...
Caused by: com.ibm.wps.um.exceptions.impl.MemberNotFoundExceptionImpl: com.ibm.portal.puma.MemberNotFoundException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,o=defaultWIMFileBasedRealm/null
...
Caused by: com.ibm.portal.puma.MemberNotFoundException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,o=defaultWIMFileBasedRealm/null
...

Accessing the Portal from a browser returns the following error:

404: Initialization of one or more services failed

Environment

Any Portal 6.1, 7.0 or 8.0 environment
Resolving the problem

Change the administrative user and group by running the ConfigEngine task wp-change-portal-admin-user. Specify an administrative user and group that exist in the repository.

Only if the ConfigEngine task fails and you need a manual work-around that enables WebSphere Portal to start:
Update all AdminUser and AdminGroup properties for the Access Control Data Management Service with the appropriate administrative user and group from the LDAP. 

Technote : 

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





SECJ0371W: Validation of the LTPA token failed

WebSphere Portal received a request with an expired or otherwise invalid LTPA token for which it needed to generate one or more URLs. By default, the LTPA token timeout is two hours. This timeout is encoded into the token itself. With the default settings, this condition could occur if someone logged in and worked in WebSphere Portal for longer than two hours.

Check your SystemOut.log for :

at com.ibm.wps.util.HttpUtils.validateLTPATokenCookies(HttpUtils.java:458)
at com.ibm.wps.auth.extensions.impl.ExtendedAuthenticationServiceImpl.isUserLoggedIn(ExtendedAuthenticationServiceImpl.java:136)
at com.ibm.wps.state.accessors.url.EngineURLOnRequest.isProtected(EngineURLOnRequest.java:371)
at com.ibm.wps.state.accessors.url.EngineURLOnRequest.reset(EngineURLOnRequest.java:450)
atcom.ibm.wps.state.accessors.url.URLAccessorFactoryExImpl.newURL(URLAccessorFactoryExImpl.java:319)

Such stack traces indicate that WebSphere Portal explicitly requests LTPA token validation from WebSphere Application Server during URL generation. This is by design.


You may either ignore the warning or suppress them. To suppress such warnings, set:

com.ibm.ws.security.ltpa.LTPAServerObject=severe

per the WebSphere Application Server InfoCenter section on Log level settings.


Monday, August 4, 2014

Scheduler Error Messages upon Portal Startup

Problem

Upon the portal startup, the following error message can be found in the log:

[...] 0000006a AlarmListener E SCHD0063E: A task with ID 451 failed to run on Scheduler WPSTaskScheduler (wps/Scheduler) because of an exception:
java.rmi.RemoteException: CORBA INTERNAL 0x4942f58c No;
nested exception is as follows:
org.omg.CORBA.INTERNAL: initial and forwarded IOR inaccessible vmcid: IBM minor code: 58C completed: No.

Symptom

The scheduler does not run.

Cause

One known cause is that a WAS upgrade was done. WAS cannot migrate schedulers, therefore this part of the migration needs to be done by the application - in this case the portal.
Note: There can be other causes and other scheduler related error messages that require the scheduler to be recreated.


Diagnosing the problem

Check the logs.

Resolving the problem


Remove and recreate the scheduler by using the following config tasks:

WebSphere Portal V 6.1 and later:
  1. Remove the scheduler by running the following task:
    ConfigEngine remove-scheduler

  2. Recreate the scheduler by running the following task:
    ConfigEngine create-scheduler

     
  3. Modify the settings by running the following task:
    ConfigEngine create-scheduler-custom-property


WebSphere Portal V 6.0 and later:
  1. Remove the scheduler by running the following task:
    WPSConfig action-remove-scheduler-cleanup-daemon

  2. Recreate the scheulder by running the following task:
    WPSConfig action-create-scheduler-cleanup-daemon

  3. Modify the settings by using the following tasks:
    WPSConfig action-modify-scheduler-base-properties-cleanup-daemon
    WPSConfig action-modify-scheduler-custom-properties-cleanup-daemon


WebSphere Portal V 5.1 and later:
  1. Remove the scheduler by running the following task:
    WPSConfig action-remove-scheduler-cleanup-daemon

  2. Recreate the scheulder by running the following task:
    WPSConfig action-create-scheduler-cleanup-daemon

  3. Modify the settings by running the following task:
    WPSConfig action-modify-scheduler-cleanup-daemon-jndi-wps-ds

If these tasks do not help, you need to remove the schedules with this command:

WebSphere Portal V 5.1, V 6.0 and later:
   WPSConfig action-clean-scheduled-tasks

WebSphere Portal V 6.1 and later:
   ConfigEngine action-clean-scheduled-tasks

After you have done this, restart the server. Upon restart, the server will re-insert the default schedule. If you modified the default scheduled task, recreate your schedules by using the XML configuration interface.

Note: In a cluster you need to do this only on the primary node.   

Source : https://www-304.ibm.com/support/docview.wss?uid=swg21289958