Steps to help resolve wsadmin problems
- Are you trying to start the wsadmin connected with some running server
(for example: dmgr or nodeagent)?
- Yes, continue to the next question.
- No, be aware that in local mode some of the
functions are not available, such as $AdminControl. Continue to
the next question.
- Is there a firewall between the server and wsadmin client?
- Is security enabled?
- Yes, continue to next question.
- No, continue with question 5.
- Does the problem occur with security disabled?
- Yes, continue to the next question.
- No, this might be related with security issues.
Address the security problem first.
- Do you receive any errors when attempting to start wsadmin?
For example:
WASX7023E: Error creating "SOAP"
connection to host "<name>" |
|
- Yes,
- The server to which wsadmin is attempting to connect is not
running. Start the server, then retry. Debug the server process, TroubleShooting:
Start/Stop server fails.
- The port or hostname that wsadmin is attempting to use is incorrect.
Correct the hostname or port and retry.
- If you are intending to start wsadmin while not connected to a running
server, then you should specify the option, -conntype NONE.
- No, continue to the next question.
|
|
- Are you able to execute simple commands?
For example:
- If the stand-alone command, such as $AdminApp list works and
your script fails then this is probably a scripting issue. Review your
script.
What to do next
If the preceding troubleshooting steps did not solve your problem, see
the MustGather
for wsadmin problems. |