Topic
  • 11 replies
  • Latest Post - ‏2013-04-04T13:36:53Z by httweed
SystemAdmin
SystemAdmin
30895 Posts

Pinned topic WebSphere Portal Server v8.0 FP1 Upgrade fail

‏2013-02-07T04:06:16Z |
I have migrated Websphere portal server from 6.1.5.3 to v8.0.
After this, i tried to upgrade the FP1. I have upgraded WASv8 with FP 6.

During Portal Upgrade, i am getting following error,

Target finished: change-workdir-permission-iseries
xmlaccess EJPXB0006I: Connecting to URL http://localhost:10040/wps/config/
xmlaccess EJPXB0004I: Writing output file C:\IBM\WebSphere\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml
xmlaccess EJPXB0002I: Reading input file C:\IBM\WebSphere\PortalServer\installer\wp.migration.core\migration\components\wp.migration.core\exportWebApps.xml
xmlaccess EJPXB0019E: Server response indicates an error. For status and details of the XmlAccess error look at file C:\IBM\WebSphere\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml.
xmlaccess EJPXB0019E: Server response indicates an error. For status and details of the XmlAccess error look at file C:\IBM\WebSphere\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml.
  • Exception Thrown ---
C:\IBM\WebSphere\ConfigEngine\config\includes\upgrade_cfg.xml:104: EJPXB0019E: Server response indicates an error. For status and details of the XmlAccess error look at file C:\IBM\WebSphere\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml.
at com.ibm.wps.xmlaccess.XmlAccessTask.fail(Unknown Source)
at com.ibm.wps.xmlaccess.XmlAccessTask.execute(Unknown Source)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)
at com.ibm.wps.config.tasks.AntCallTask.execute(AntCallTask.java:13)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at com.ibm.wps.config.tasks.ConsolidateConfigExtensionTask.executeSequential(ConsolidateConfigExtensionTask.java:173)
at com.ibm.wps.config.tasks.ConsolidateConfigExtensionTask.execute(ConsolidateConfigExtensionTask.java:88)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)
at com.ibm.wps.config.tasks.AntCallTask.execute(AntCallTask.java:13)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.Main.start(Main.java:150)
at com.ibm.wps.config.ConfigEngine.process(ConfigEngine.java:953)
at com.ibm.wps.config.ConfigEngine.main(ConfigEngine.java:219)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:274)

Target finished: deploy-portlets-upgrade
  • Exception Thrown ---
C:\IBM\WebSphere\PortalServer\installer\wp.update\config\includes\wp.update.fix_cfg.xml:194: The following error occurred while executing this line:
C:\IBM\WebSphere\ConfigEngine\config\includes\upgrade_cfg.xml:104: EJPXB0019E: Server response indicates an error. For status and details of the XmlAccess error look at file C:\IBM\WebSphere\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml.
at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:539)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)
at com.ibm.wps.config.tasks.AntCallTask.execute(AntCallTask.java:13)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at com.ibm.wps.config.tasks.ConsolidateConfigExtensionTask.executeSequential(ConsolidateConfigExtensionTask.java:173)
at com.ibm.wps.config.tasks.ConsolidateConfigExtensionTask.execute(ConsolidateConfigExtensionTask.java:88)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)
at com.ibm.wps.config.tasks.AntCallTask.execute(AntCallTask.java:13)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.Main.start(Main.java:150)
at com.ibm.wps.config.ConfigEngine.process(ConfigEngine.java:953)
at com.ibm.wps.config.ConfigEngine.main(ConfigEngine.java:219)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:274)
Caused by: C:\IBM\WebSphere\ConfigEngine\config\includes\upgrade_cfg.xml:104: EJPXB0019E: Server response indicates an error. For status and details of the XmlAccess error look at file C:\IBM\WebSphere\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml.
at com.ibm.wps.xmlaccess.XmlAccessTask.fail(Unknown Source)
at com.ibm.wps.xmlaccess.XmlAccessTask.execute(Unknown Source)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
... 38 more
  • Nested Exception ---

Is this common issue?
Updated on 2013-04-04T13:36:53Z at 2013-04-04T13:36:53Z by httweed
  • SystemAdmin
    SystemAdmin
    30895 Posts

    Re: WebSphere Portal Server v8.0 FP1 Upgrade fail

    ‏2013-02-07T06:11:13Z  
    Yes. This issue would occur as the WAS v8 installation does not have EJBDeploy feature enabled which is a required feature for Portal v8 server.

    The following URL would give useful info:

    ===
    http://www-01.ibm.com/support/docview.wss?uid=swg21607518
    ===
  • SystemAdmin
    SystemAdmin
    30895 Posts

    Re: WebSphere Portal Server v8.0 FP1 Upgrade fail

    ‏2013-02-07T09:47:09Z  
    Yes. This issue would occur as the WAS v8 installation does not have EJBDeploy feature enabled which is a required feature for Portal v8 server.

    The following URL would give useful info:

    ===
    http://www-01.ibm.com/support/docview.wss?uid=swg21607518
    ===
    I have upgraded WAS v8 with FP5 and the EJB Features are already enabled.
    Do i need to upgrade any iFixes?
  • SystemAdmin
    SystemAdmin
    30895 Posts

    Re: WebSphere Portal Server v8.0 FP1 Upgrade fail

    ‏2013-02-07T11:40:44Z  
    I have upgraded WAS v8 with FP5 and the EJB Features are already enabled.
    Do i need to upgrade any iFixes?
    The wps_scheduler application gets reinstalled during the migration process.

    You should be able to add this feature without having to implement any iFix.

    You can follow the steps specified in the URL in previous post to add the same.

    I guess this would solve the issue.
  • SystemAdmin
    SystemAdmin
    30895 Posts

    Re: WebSphere Portal Server v8.0 FP1 Upgrade fail

    ‏2013-02-08T04:47:00Z  
    The wps_scheduler application gets reinstalled during the migration process.

    You should be able to add this feature without having to implement any iFix.

    You can follow the steps specified in the URL in previous post to add the same.

    I guess this would solve the issue.
    EJB is already enabled.
    In your previous post says like, we need to enable EJB features.

    Thanks in Advance.
  • SystemAdmin
    SystemAdmin
    30895 Posts

    Re: WebSphere Portal Server v8.0 FP1 Upgrade fail

    ‏2013-02-08T07:17:19Z  
    EJB is already enabled.
    In your previous post says like, we need to enable EJB features.

    Thanks in Advance.
    On further looking into the logs, do you find something like this:

    ==
    EJBMDOrchestr E CNTR0075E: The
    user-provided class
    "com.ibm.wps.datastore.ejb.cleanup.EJSRemoteStatelessSchedulerManager
    _03598d10" needed by the EnterpriseBean could not be found or loaded.
    ==

    This class is supposed to be part of the wp.ejb.scheduler.jar file
    within the wps_scheduler application.
    Also do you see following things in the logs?

    ======================
    wsadmin ADMA0245W: EJBDeploy feature is not installed. Cannot
    execute "deploy enterprise beans" option.
    wsadmin ADMA5016I: Installation of wps_scheduler started.
    wsadmin ADMA5058I: Application and module versions are validated
    with versions of deployment targets.
    wsadmin ADMA5005I: The application wps_scheduler is configured in
    the WebSphere Application Server repository.
    ======================

    You can look further in logs to see if you get any other error.
  • SystemAdmin
    SystemAdmin
    30895 Posts

    Re: WebSphere Portal Server v8.0 FP1 Upgrade fail

    ‏2013-02-11T03:58:21Z  
    On further looking into the logs, do you find something like this:

    ==
    EJBMDOrchestr E CNTR0075E: The
    user-provided class
    "com.ibm.wps.datastore.ejb.cleanup.EJSRemoteStatelessSchedulerManager
    _03598d10" needed by the EnterpriseBean could not be found or loaded.
    ==

    This class is supposed to be part of the wp.ejb.scheduler.jar file
    within the wps_scheduler application.
    Also do you see following things in the logs?

    ======================
    wsadmin ADMA0245W: EJBDeploy feature is not installed. Cannot
    execute "deploy enterprise beans" option.
    wsadmin ADMA5016I: Installation of wps_scheduler started.
    wsadmin ADMA5058I: Application and module versions are validated
    with versions of deployment targets.
    wsadmin ADMA5005I: The application wps_scheduler is configured in
    the WebSphere Application Server repository.
    ======================

    You can look further in logs to see if you get any other error.
    Thanks for ur reply.

    I didn't find any error like as you mentioned. Because, EJBDeploy features are enabled.

    I have attached both SystemOut.log and ConfigTrace.log for Websphere_Portal Server.

    Please have a look on that.

    Thanks in advance.

    Regards,
    Nehrukannan

    Attachments

  • SystemAdmin
    SystemAdmin
    30895 Posts

    Re: WebSphere Portal Server v8.0 FP1 Upgrade fail

    ‏2013-04-04T11:48:05Z  
    Thanks for ur reply.

    I didn't find any error like as you mentioned. Because, EJBDeploy features are enabled.

    I have attached both SystemOut.log and ConfigTrace.log for Websphere_Portal Server.

    Please have a look on that.

    Thanks in advance.

    Regards,
    Nehrukannan
    I had installed POrtal 8.0.0.0 on WAS ND 8.0.0.3 (single server, no dmgr).
    I upgraded WAS to 8.0.0.5 succesfully.
    I attempted to upgrade Portal to 8.0.0.1 but got same failures as above.

    WAS 8.0.0.5 does have EJB Tools installed.

    The POrtal got started:

    echo Starting 'WebSphere_Portal'
    exectimeout Executing command: C:/IBM/WP8/wp_profile/bin/startServer.bat WebSphere_Portal
    exectimeout Could not parse timeout. Defaults to 0.
    exectimeout StdOut: ADMU0116I: Tool information is being logged in file
    exectimeout StdOut: C:\IBM\WP8\wp_profile\logs\WebSphere_Portal\startServer.log
    exectimeout StdOut: ADMU0128I: Starting tool with the wp_profile profile
    exectimeout StdOut: ADMU3100I: Reading configuration for server: WebSphere_Portal
    exectimeout StdOut: ADMU3200I: Server launched. Waiting for initialization status.
    exectimeout StdOut: ADMU3000I: Server WebSphere_Portal open for e-business; process id is 3304

    Then jars from the deploytool folder were used:

    set-wsadmin-scripting-classpath-in-jacl-properties-2:
    echo jacl.properties com.ibm.ws.scripting.classpath: 'C:/IBM/WP8/ConfigEngine/lib/wkplc.misc.jar;C:/IBM/WP8/AppServer/deploytool/itp/batchboot.jar;C:/IBM/WP8/AppServer/deploytool/itp/batch2.jar;C:/IBM/WP8/PortalServer/base/wp.base/shared/app/wp.base.jar;C:/IBM/WP8/PortalServer/shared/app/wp.base.jar'
    echo jacl.properties com.ibm.ws.scripting.port: '10025'
    echo jacl.properties com.ibm.ws.scripting.host: 'Win2003STD64.rcsnl.ams.nl.ibm.com'
    Target finished: set-wsadmin-scripting-classpath-in-jacl-properties-2

    finally the error appeared:

    xmlaccess EJPXB0006I: Connecting to URL http://localhost:10039/wps/config/
    xmlaccess EJPXB0004I: Writing output file C:\IBM\WP8\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml
    xmlaccess EJPXB0002I: Reading input file C:\IBM\WP8\PortalServer\installer\wp.migration.core\migration\components\wp.migration.core\exportWebApps.xml
    xmlaccess EJPXB0019E: Server response indicates an error. For status and details of the XmlAccess error look at file C:\IBM\WP8\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml.
    xmlaccess EJPXB0019E: Server response indicates an error. For status and details of the XmlAccess error look at file C:\IBM\WP8\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml.
    • Exception Thrown ---
    C:\IBM\WP8\ConfigEngine\config\includes\upgrade_cfg.xml:104: EJPXB0019E: Server response indicates an error. For status and details of the XmlAccess error look at file C:\IBM\WP8\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml.
    at com.ibm.wps.xmlaccess.XmlAccessTask.fail(Unknown Source)
    at com.ibm.wps.xmlaccess.XmlAccessTask.execute(Unknown Source)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
    at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
    at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)
    at com.ibm.wps.config.tasks.AntCallTask.execute(AntCallTask.java:13)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
    at com.ibm.wps.config.tasks.ConsolidateConfigExtensionTask.executeSequential(ConsolidateConfigExtensionTask.java:173)
    at com.ibm.wps.config.tasks.ConsolidateConfigExtensionTask.execute(ConsolidateConfigExtensionTask.java:88)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
    at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
    at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)
    at com.ibm.wps.config.tasks.AntCallTask.execute(AntCallTask.java:13)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:64)
    at com.ibm.wps.config.If.execute(If.java:75)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
    at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
    at org.apache.tools.ant.Main.runBuild(Main.java:668)
    at org.apache.tools.ant.Main.startAnt(Main.java:187)
    at org.apache.tools.ant.Main.start(Main.java:150)
    at com.ibm.wps.config.ConfigEngine.process(ConfigEngine.java:953)
    at com.ibm.wps.config.ConfigEngine.main(ConfigEngine.java:219)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:274)

    I attach the Portal logs and the IM logs.
  • SystemAdmin
    SystemAdmin
    30895 Posts

    Re: WebSphere Portal Server v8.0 FP1 Upgrade fail

    ‏2013-04-04T12:01:34Z  
    I had installed POrtal 8.0.0.0 on WAS ND 8.0.0.3 (single server, no dmgr).
    I upgraded WAS to 8.0.0.5 succesfully.
    I attempted to upgrade Portal to 8.0.0.1 but got same failures as above.

    WAS 8.0.0.5 does have EJB Tools installed.

    The POrtal got started:

    echo Starting 'WebSphere_Portal'
    exectimeout Executing command: C:/IBM/WP8/wp_profile/bin/startServer.bat WebSphere_Portal
    exectimeout Could not parse timeout. Defaults to 0.
    exectimeout StdOut: ADMU0116I: Tool information is being logged in file
    exectimeout StdOut: C:\IBM\WP8\wp_profile\logs\WebSphere_Portal\startServer.log
    exectimeout StdOut: ADMU0128I: Starting tool with the wp_profile profile
    exectimeout StdOut: ADMU3100I: Reading configuration for server: WebSphere_Portal
    exectimeout StdOut: ADMU3200I: Server launched. Waiting for initialization status.
    exectimeout StdOut: ADMU3000I: Server WebSphere_Portal open for e-business; process id is 3304

    Then jars from the deploytool folder were used:

    set-wsadmin-scripting-classpath-in-jacl-properties-2:
    echo jacl.properties com.ibm.ws.scripting.classpath: 'C:/IBM/WP8/ConfigEngine/lib/wkplc.misc.jar;C:/IBM/WP8/AppServer/deploytool/itp/batchboot.jar;C:/IBM/WP8/AppServer/deploytool/itp/batch2.jar;C:/IBM/WP8/PortalServer/base/wp.base/shared/app/wp.base.jar;C:/IBM/WP8/PortalServer/shared/app/wp.base.jar'
    echo jacl.properties com.ibm.ws.scripting.port: '10025'
    echo jacl.properties com.ibm.ws.scripting.host: 'Win2003STD64.rcsnl.ams.nl.ibm.com'
    Target finished: set-wsadmin-scripting-classpath-in-jacl-properties-2

    finally the error appeared:

    xmlaccess EJPXB0006I: Connecting to URL http://localhost:10039/wps/config/
    xmlaccess EJPXB0004I: Writing output file C:\IBM\WP8\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml
    xmlaccess EJPXB0002I: Reading input file C:\IBM\WP8\PortalServer\installer\wp.migration.core\migration\components\wp.migration.core\exportWebApps.xml
    xmlaccess EJPXB0019E: Server response indicates an error. For status and details of the XmlAccess error look at file C:\IBM\WP8\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml.
    xmlaccess EJPXB0019E: Server response indicates an error. For status and details of the XmlAccess error look at file C:\IBM\WP8\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml.
    • Exception Thrown ---
    C:\IBM\WP8\ConfigEngine\config\includes\upgrade_cfg.xml:104: EJPXB0019E: Server response indicates an error. For status and details of the XmlAccess error look at file C:\IBM\WP8\wp_profile\ConfigEngine\config\work\deployedWebAppXmlAccess-PTF\preExistingWebApps.xml.
    at com.ibm.wps.xmlaccess.XmlAccessTask.fail(Unknown Source)
    at com.ibm.wps.xmlaccess.XmlAccessTask.execute(Unknown Source)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
    at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
    at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)
    at com.ibm.wps.config.tasks.AntCallTask.execute(AntCallTask.java:13)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
    at com.ibm.wps.config.tasks.ConsolidateConfigExtensionTask.executeSequential(ConsolidateConfigExtensionTask.java:173)
    at com.ibm.wps.config.tasks.ConsolidateConfigExtensionTask.execute(ConsolidateConfigExtensionTask.java:88)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
    at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
    at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)
    at com.ibm.wps.config.tasks.AntCallTask.execute(AntCallTask.java:13)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:64)
    at com.ibm.wps.config.If.execute(If.java:75)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
    at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
    at org.apache.tools.ant.Main.runBuild(Main.java:668)
    at org.apache.tools.ant.Main.startAnt(Main.java:187)
    at org.apache.tools.ant.Main.start(Main.java:150)
    at com.ibm.wps.config.ConfigEngine.process(ConfigEngine.java:953)
    at com.ibm.wps.config.ConfigEngine.main(ConfigEngine.java:219)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:274)

    I attach the Portal logs and the IM logs.
    Here are the logs. Note that the line that fails is: 104

    99: <property name="PortalAdminIdShort" value="${PortalAdminId}" />
    100: <xmlaccess
    101: user="${PortalAdminIdShort}"
    102: password="${PortalAdminPwd}"
    103: srcfile="${exportWebAppsXmlAccessScript}"
    104:**> destfile="${preExistingDeployedWebAppsXmlAccessScript}" />


    Properties and values used in the failed target
    preExistingDeployedWebAppsXmlAccessScript=C:/IBM/WP8/wp_profile/ConfigEngine/config/work/deployedWebAppXmlAccess-PTF/preExistingWebApps.xml
    PortalAdminPwd=PASSWORD_REMOVED
    XMLAccessUrl=http://localhost:10039/wps/config/
    PortalAdminId=wpsadmin
    isIseries=${isIseries}
    exportWebAppsXmlAccessScript=C:/IBM/WP8/PortalServer/installer/wp.migration.core/migration/components/wp.migration.core/exportWebApps.xml
    PortalAdminIdShort=wpsadmin

    After IM reported the failure, the directory:

    C:/IBM/WP8/wp_profile/ConfigEngine/config/work/

    no longer exists. The file C:/IBM/WP8/PortalServer/installer/wp.migration.core/migration/components/wp.migration.core/exportWebApps.xml contains:

    <?xml version="1.0" encoding="UTF-8" ?>
    • <!--
    Licensed Materials - Property of IBM

    5655-R17, 5724-E76, 5724-E77, 5724-I29

    (C) Copyright IBM Corp. 2008 All Rights Reserved.

    US Government Users Restricted Rights - Use, duplication or
    disclosure restricted by GSA ADP Schedule Contract with IBM
    Corp.

    -->
    <request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PortalConfig_8.0.0.xsd" type="export">
    <portal action="locate">
    <web-app objectid="*" action="export" />
    </portal>
    </request>

    Any suggestions for what to try next? Thank you and regards, Lara
  • SystemAdmin
    SystemAdmin
    30895 Posts

    Re: WebSphere Portal Server v8.0 FP1 Upgrade fail

    ‏2013-04-04T12:41:47Z  
    Here are the logs. Note that the line that fails is: 104

    99: <property name="PortalAdminIdShort" value="${PortalAdminId}" />
    100: <xmlaccess
    101: user="${PortalAdminIdShort}"
    102: password="${PortalAdminPwd}"
    103: srcfile="${exportWebAppsXmlAccessScript}"
    104:**> destfile="${preExistingDeployedWebAppsXmlAccessScript}" />


    Properties and values used in the failed target
    preExistingDeployedWebAppsXmlAccessScript=C:/IBM/WP8/wp_profile/ConfigEngine/config/work/deployedWebAppXmlAccess-PTF/preExistingWebApps.xml
    PortalAdminPwd=PASSWORD_REMOVED
    XMLAccessUrl=http://localhost:10039/wps/config/
    PortalAdminId=wpsadmin
    isIseries=${isIseries}
    exportWebAppsXmlAccessScript=C:/IBM/WP8/PortalServer/installer/wp.migration.core/migration/components/wp.migration.core/exportWebApps.xml
    PortalAdminIdShort=wpsadmin

    After IM reported the failure, the directory:

    C:/IBM/WP8/wp_profile/ConfigEngine/config/work/

    no longer exists. The file C:/IBM/WP8/PortalServer/installer/wp.migration.core/migration/components/wp.migration.core/exportWebApps.xml contains:

    <?xml version="1.0" encoding="UTF-8" ?>
    • <!--
    Licensed Materials - Property of IBM

    5655-R17, 5724-E76, 5724-E77, 5724-I29

    (C) Copyright IBM Corp. 2008 All Rights Reserved.

    US Government Users Restricted Rights - Use, duplication or
    disclosure restricted by GSA ADP Schedule Contract with IBM
    Corp.

    -->
    <request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PortalConfig_8.0.0.xsd" type="export">
    <portal action="locate">
    <web-app objectid="*" action="export" />
    </portal>
    </request>

    Any suggestions for what to try next? Thank you and regards, Lara
    Here are also the logs of the wp_profile.
  • httweed
    httweed
    510 Posts

    Re: WebSphere Portal Server v8.0 FP1 Upgrade fail

    ‏2013-04-04T13:34:08Z  
    Here are also the logs of the wp_profile.
    Hi LaraZiosi,

    It looks like your wps.ear application is broken on the WebSphere_Portal server. It starts up cleanly, but it doesn't contain the WebSphere Portal Server module...so it's not going to work. This would have caused the Credential Validation to fail as well, and I can see that is the case in the ConfigTrace.log. Did you edit the config.ini file to get past the credential validation? If so, that edit is only meant for if credential validation hangs. If validation fails, then there is a real problem.

    Has wps.ear ever been redeployed in this environment? I don't know why the Portal Server module would suddenly go missing without a manual redeployment.

    In any case, we can try to fix it by running these ConfigEngine scripts:

    ConfigEngine.bat action-remove-ear-wp.ear
    ConfigEngine.bat action-create-ear-wp.ear

    This will reinstall wps.ear. If you have made any customizations to wps.ear, like changes to web.xml or added your themes or something like, they are going to be removed by these steps, so just warning you.

    After those scripts complete successfully, remove the 'skip validaton' flag you added to IIM's config.ini. We need validation to be successful to ensure the Portal server is working (and again if validation hangs, then that's another issue). Validation will take some time though because it starts up the WebSphere_Portal server then runs an xmlaccess script against, so allow it several minutes at least.

    Then you can try the fixpack again.
    ~HT
    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM
  • httweed
    httweed
    510 Posts

    Re: WebSphere Portal Server v8.0 FP1 Upgrade fail

    ‏2013-04-04T13:36:53Z  
    Thanks for ur reply.

    I didn't find any error like as you mentioned. Because, EJBDeploy features are enabled.

    I have attached both SystemOut.log and ConfigTrace.log for Websphere_Portal Server.

    Please have a look on that.

    Thanks in advance.

    Regards,
    Nehrukannan
    Hi NehruKannan,

    Not sure if you're still following this thread but you've got a different issue than Lara. For you, wps.ear fails to initialize because of this exception:

    Caused by: java.lang.NoSuchMethodError: com/ibm/wps/services/platform/PlatformService.getLtpaNameAttribute()Ljava/util/HashMap;
    at com.ibm.wps.services.config.ConfigServiceImpl.init(ConfigServiceImpl.java:216)
    at com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:362)
    at com.ibm.wps.services.ServiceManager.initInternal(ServiceManager.java:261)
    at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:173)

    This prevents the xmlaccess script from working correctly. It's odd to see a NoSuchMethod exception in the middle of the upgrade. It implies we've got a mistmatch of Portal code. Either the upgrade did not upgrade something correctly, or maybe you received a test fix from Portal support at some point that's still on the system and conflicting with the upgrade?
    ~HT
    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM