WASX7023E: Error creating "SOAP" connection to host "localhost"

[s***@gmail.com]

hi frnds,
i m running WAS v5.0 base configuration on windows xp professional.
i am new to websphere and when i am trying to use wsadmin using the following command

C:\WebSphere\AppServer\bin>wsadmin.bat -user admin -password admin

its throwing me the following error...

WASX7023E: Error creating "SOAP" connection to host "localhost"; exception infor
mation: com.ibm.websphere.management.exception.ConnectorNotAvailableException
WASX7213I: This scripting client is not connected to a server process; please re
fer to the log file C:\WebSphere\AppServer\logs\wsadmin.traceout for additional
information.

can any body help me this?

thanks in advance,
Niva.

[b***@yahoo.com]

Does your websphere has been started, if not use the option conntype NONE

The syntax is as
wsadmin -conntype NONE -user xyx -pwd xyz.

Thanks

[Ken Hygh]

Post by s***@gmail.com
hi frnds,
i m running WAS v5.0 base configuration on windows xp professional.
i am new to websphere and when i am trying to use wsadmin using the following command
C:\WebSphere\AppServer\bin>wsadmin.bat -user admin -password admin
its throwing me the following error...
WASX7023E: Error creating "SOAP" connection to host "localhost"; exception infor
mation: com.ibm.websphere.management.exception.ConnectorNotAvailableException
WASX7213I: This scripting client is not connected to a server process; please re
fer to the log file C:\WebSphere\AppServer\logs\wsadmin.traceout for additional
information.
can any body help me this?
thanks in advance,
Niva.

As another poster mentioned, the appserver does need to be running in
order for wsadmin to connect.

Some other things to look at:
1) make sure a firewall isn't blocking the traffic
2) make sure you're using the default port for SOAP (its port number is
printed in SystemOut.log on server startup). You can put a non-default
port number as a parameter for wsadmin

Ken

[Ony]

The easiest way to troubleshoot this is to tail the SystemOut.log file
for details.

Stop the application server process
Make sure the SOAP_CONNECTOR_ADDRESS port is not in use.
Restart the app server as normal

Onyema Akpakwu

[Dexthor]

If your Server has started properly then look for the "SOAP" in the
SystemOut.log. Use that port# in the wsadmin command:

wsadmin -conntype SOAP -host localhost -port soap_port# -user
valid_user_name -password xxxxx

Are you able to see the WebAdmin Console ? (http://....:9090/admin ??)

-Dexthor.