Troubleshoot: Errors WASX7023E, WASX7213I, WASX8011W, WASX7206W occur during feature enablement
When enabling a feature on your WebSphere Commerce instance, error messages are displayed.
Problem
You receive the following errors during feature enablement:
UpdateSOAPTimeout: [wsadmin] profileName=demo registry=/opt/IBM/WebSphere/AppServer/properties/profileRegistry.xml [wsadmin] profileHome=/opt/IBM/WebSphere/AppServer/profiles/demo [wsadmin] WASX7023E: Error creating "SOAP" connection to host "localhost"; exception information: 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 /opt/IBM/WebSphere/AppServer/profiles/demo/logs/wsadmin.traceout for additional information. [wsadmin] WASX8011W: AdminTask object is not available. [wsadmin] Not output parameters [wsadmin] WASX7017E: Exception received while running file "/opt/IBM/WebSphere/CommerceServer60/components/jca4webservices/scripts/disableFeature.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7206W: The application management service is not running. Application management commands will not run.
Solution
The feature enablement tooling must communicate with the WAS that manages your environment. These error codes are defined by the wasadmin scripting agent, and indicate that the agent cannot connect to a WAS . Ensure that the server that manages your WebSphere Commerce instance has been started; refer to the following information:
AIX|Linux|Solaris|Starting an application server
Windows:
Related Concepts
WebSphere Commerce feature packs
Related tasks
Related Reference