Troubleshooting
Problem
The script 'wsadmin.bat' fails to install when deploying IBM i2 Intelligence Analysis Platform.
Symptom
Buildfile: C:\IBM\IAP-3.0.5.2\IAP-Deployment-Toolkit\scripts\deploy.xml
start-all-applications:
[exec] AMQ8146: WebSphere MQ queue manager not available.
[exec] Result: 40
[exec] WebSphere MQ queue manager 'IAPQM' starting.
[exec] The queue manager is associated with installation 'Installation1'.
[exec] 5 log records accessed on queue manager 'IAPQM' during the log replay phase.
[exec] Log replay for queue manager 'IAPQM' complete.
[exec] Transaction manager state recovered for queue manager 'IAPQM'.
[exec] WebSphere MQ queue manager 'IAPQM' started using V7.5.0.0.
[for-each-application] Using topology C:\IBM\IAP-3.0.5.2\IAP-Deployment-Toolkit\configuration\environment\topology.xml
[echo] Waiting for remote server-(xxx-xxxx-xxx). This will wait for up to an hour
[echo] Executing C:\IBM\WebSphere\AppServer\bin\retrieveSigners.bat
[echo] CWPKI0309I: All signers from remote keystore already exist in local keystore.
[echo] Waiting for remote server-(xxx-xxxx-xxx). This will wait for up to an hour
[echo] Executing C:\IBM\WebSphere\AppServer\bin\retrieveSigners.bat
[echo] CWPKI0308I: Adding signer alias "root_1" to local keystore
[echo] "ClientDefaultTrustStore" with the following SHA digest:
[echo] 1D:4B:7E:82:94:9E:F4:71:03:94:71:21:A0:93:14:F1:CE:ED:18:8D
[for-each-application] Using topology C:\IBM\IAP-3.0.5.2\IAP-Deployment-Toolkit\configuration\environment\topology.xml
[echo] hostName: (xxx-xxxx-xxx), WC_adminhost: 8881, command: startApplication, serverName: ApolloServerwrite, nodeName: Node01write, cellName: Node01Cellwrite
[propertyfile] Updating property file: C:\IBM\IAP-3.0.5.2\IAP-Deployment-Toolkit\scripts\websphere\noecho.properties
[echo] Executing C:\IBM\WebSphere\AppServer\bin\wsadmin.bat
[exec] Result: 105
[echo] Script Output:
[echo] WASX7209I: Connected to process "ApolloServerwrite" on node Node01write using SOAP connector; The type of process is: UnManagedProcess
[echo] WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[-command, startApplication, -process, ApolloServerwrite, -node-name, Node01write, -cell-name, Node01Cellwrite, -app-name, ApolloGarEar, -ignore-errors, false]"
[echo] $Id: wsadminlib.py 115 2011-01-03 15:51:00Z dingsor $
[echo] Starting application 'ApolloGarEar'
[echo] node 'Node01write'
[echo] process 'ApolloServerwrite'
[echo] WASX7017E: Exception received while running file "C:\IBM\IAP-3.0.5.2\IAP-Deployment-Toolkit\scripts\websphere/manage-application.py"; exception information: javax.management.MBeanException
[echo] com.ibm.ws.exception.RuntimeWarning
[echo] com.ibm.ws.webcontainer.exception.WebAppNotLoadedException: com.ibm.ws.webcontainer.exception.WebAppNotLoadedException: Failed to load webapp: help_host
BUILD FAILED with the following error:
C:\IBM\IAP-3.0.5.2\IAP-Deployment-Toolkit\scripts\application\manage-application.xml:66: The following error occurred while executing this line:
C:\IBM\IAP-3.0.5.2\IAP-Deployment-Toolkit\scripts\application\manage-application.xml:85: The following error occurred while executing this line:
C:\IBM\IAP-3.0.5.2\IAP-Deployment-Toolkit\scripts\application\manage-application.xml:91: The following error occurred while executing this line:
C:\IBM\IAP-3.0.5.2\IAP-Deployment-Toolkit\scripts\application\manage-application.xml:219: The following error occurred while executing this line:
C:\IBM\IAP-3.0.5.2\IAP-Deployment-Toolkit\scripts\common\was-utils.xml:147: The following error occurred while executing this line:
C:\IBM\IAP-3.0.5.2\IAP-Deployment-Toolkit\scripts\common\was-utils.xml:92: Script 'C:\IBM\WebSphere\AppServer\bin\wsadmin.bat' failed.
Cause
This issue occurs because the WebSphere profiles have become corrupt.
Resolving The Problem
Delete WebSphere Application Server profile on the Write server using the following command:
- Python deploy.py –s write –t delete-was-profile
Delete the following entries from the file “deployment.progress.properties”
checkpoint.time.profile.started=2014-09-24 10\:24\:49
checkpoint.time.profile.created=2014-09-24 10\:32\:30
checkpoint.time.tai.installed=2014-09-24 10\:32\:32
checkpoint.time.ear.prepared=2014-09-24 10\:33\:13
checkpoint.time.app.installed=2014-09-24 10\:35\:52
checkpoint.time.http.config.updated=2014-09-24 10\:36\:14
Then run the following commands in sequence as described below:
On write server:
- Python deploy.py -s write -t stop-was-server
- Python deploy.py -s write -t start-was-server
On read server
- Python deploy.py -s read -t stop-was-server
- Python deploy.py -s read -t start-was-server
On write server:
- Python deploy.py -s write -t stop-queue-manager
- Python deploy.py -s write -t start-all-applications
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21687849