BPM, Workflow, and Case

BPM, Workflow, and Case

Come for answers. Stay for best practices. All we’re missing is you.

 View Only
Expand all | Collapse all

startManager command fail with runConfigActions script

  • 1.  startManager command fail with runConfigActions script

    Posted Thu March 24, 2022 06:53 PM

    Hi,

    I have upgrading existing profiles for IBM Business Automation Workflow V20.0.0.1 to IBM Business Automation Workflow V21.0.3.

    I have follow the upgrade document (https://www.ibm.com/support/pages/node/6507347) thoroughly.

    all the steps have been successfully completed, once I started the dmgr profile using the ./startManager command, received the below exception.

    Can anyone help me out to fix this issue?

    runConfigActions script execution failed. Exit code: 1

    Exception caught while waiting for runConfigActions script to complete: /opt/IBM/WebSphere/AppServer/profiles/DmgrProfile/bin/runConfigActions.sh

    below is the ffdc result:

    root:/opt/IBM/WebSphere/AppServer/profiles/DmgrProfile/logs/ffdc_upgrade_DmgrProfile_20220324-230617# cat ffdc.6928086832306837812.txt

    [3/24/22 23:08:06:152 PKT] FFDC Exception:java.lang.NullPointerException SourceId:com.ibm.bpm.config.BPMConfig.main ProbeId:202 Reporter:java.lang.Class

    java.lang.NullPointerException

    at com.ibm.bpm.config.capability.standard.ComponentContentNavigator.installApplication(ComponentContentNavigator.java:672)

    at com.ibm.bpm.config.capability.standard.ComponentContentNavigator.upgradeDeploymentTarget(ComponentContentNavigator.java:1145)

    at com.ibm.bpm.config.capability.Capability.upgrade(Capability.java:603)

    at com.ibm.bpm.config.capability.CapabilityApplication.upgrade(CapabilityApplication.java:146)

    at com.ibm.bpm.config.capability.ProvisionDe.upgradeDeploymentEnvironment(ProvisionDe.java:929)

    at com.ibm.bpm.config.BPMConfig.upgradeProfile(BPMConfig.java:1460)

    at com.ibm.bpm.config.BPMConfig.access$1100(BPMConfig.java:169)

    at com.ibm.bpm.config.BPMConfig$Actions.upgradeProfile(BPMConfig.java:5762)

    at com.ibm.bpm.config.cli.UpgradeAction.runInner(UpgradeAction.java:131)

    at com.ibm.bpm.config.cli.AbstractConfigAction.run(AbstractConfigAction.java:129)

    at com.ibm.bpm.config.cli.UpgradeAction.run(UpgradeAction.java:40)

    at com.ibm.bpm.config.BPMConfig.main(BPMConfig.java:315)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)

    at java.lang.reflect.Method.invoke(Method.java:508)

    at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:234)

    at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:96)

    at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:77)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)

    at java.lang.reflect.Method.invoke(Method.java:508)

    at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)

    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)

    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)

    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)

    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)

    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)

    at java.lang.reflect.Method.invoke(Method.java:508)

    at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)

    at org.eclipse.core.launcher.Main.basicRun(Main.java:282)

    at org.eclipse.core.launcher.Main.run(Main.java:981)

    at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:424)

    at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:177)

    CapturedDataElements begin

    arg:[-upgrade, -profile, /opt/IBM/WebSphere/AppServer/profiles/DmgrProfile]

    CapturedDataElements end



    #BusinessAutomationWorkflow(BAW)
    #Support
    #SupportMigration


  • 2.  RE: startManager command fail with runConfigActions script

    Posted Mon April 04, 2022 06:33 PM

    Hi Moin,

    It looks like you opened a case with support but it was closed by you when asked for entitlement support info. You should probably re-engage Support and provide the entitlement info.

    From looking at the error, it looks like the Navigator ear was uninstalled in the source environment before you upgraded. You should rollback and make sure the navigator ear is present before trying the upgrade again.

    If you still have problems, you should verify your entitlement and open a case with Support



    #BusinessAutomationWorkflow(BAW)
    #Support
    #SupportMigration


  • 3.  RE: startManager command fail with runConfigActions script

    Posted Mon April 04, 2022 07:47 PM

    Hi phjones1,

    I have already opened the case with the support team on behalf of the client.

    support team working on it since the week, and has not provided any solution yet.

    no ear file was uninstalled before performing the upgrade steps, and the system was working fine before applying the patch.



    #BusinessAutomationWorkflow(BAW)
    #Support
    #SupportMigration