Troubleshoot: Error codes in the log files
A log file shows errors during a fix pack installation on your WebSphere Commerce instance.
Problem
You see a WASX7023E error code in the exportear_instance.log file under the stopWCApplictions or stopPMApplications target. For example:stopPMApplications: [wsadmin] WASX7023E: Error creating "SOAP" connection to host "localhost"; exception information: com.ibm.websphere.management.exception. ConnectorNotAvailableException: com.ibm.websphere.management.exception. ConnectorNotAvailableException: Failed to get a connection with IP address associated with hostname localhost [wsadmin] WASX7213I: This scripting client is not connected to a server process; please refer to the log file C:\Program Files\IBM\WebSphere\AppServer\ profiles\wpm\logs\wsadmin.traceout for additional information. [wsadmin] WASX8011W: AdminTask object is not available. [wsadmin] WASX7303I: The following options are passed to the scripting environment and are available as argument that is stored in the argv variable: "[wpm_Commerce_Payments_App]" [wsadmin] WASX7017E: Exception received while running file "C:/Program Files/ IBM/WebSphere/CommerceServer60/config/deployment/scripts/stopApps.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: AdminControl service not available
Solution
Ensure that the WAS Administrative server is started, and attempt the install or uninstall again.
Related tasks
Install WebSphere Commerce fix packs
Uninstall WebSphere Commerce fix packs
Related Reference