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