Problems starting or using the wsadmin command

What kind of problem are you having?

If you do not see your problem here:

If none of these steps fixes your problem, check to see if the problem has been identified and documented by looking at the available online support (hints and tips, technotes, and fixes). If you don't find your problem listed there contact IBM support.

"WASX7023E: Error creating "SOAP" connection to host" or similar error trying to launch wsadmin command line utility

By default, the wsadmin utility attempts to connect to an appserver at startup. This is because some commands act upon running appservers. This error indicates that no connection could be established.

To resolve this problem:

"com.ibm.bsf.BSFException: error while eval'ing Jacl expression: no such method command name in class com.ibm.ws.scripting.AdminConfigClient" returned from wsadmin command.

This error is usually caused by a misspelled command name. Use the $AdminConfig help command to get information about what commands are available. Note that command names are case-sensitive.

WASX7022E returned from running "wsadmin -c ..." command, indicating invalid command

If the command following -c appears to be valid, the problem may be caused by the fact that on Unix, using wsadmin -c to invoke a command that includes dollar signs results in the shell attempting to do variable substitution. To confirm that this is the problem, check the command to see if it contains an unescaped dollar sign, for example: wsadmin -c "$AdminApp install ....".

To correct this problem, escape the dollar sign with a backslash. For example: wsadmin -c "\$AdminApp install ...".

com.ibm.ws.scripting.ScriptingException: WASX7025E: String "" is malformed; cannot create ObjectName

One possible cause of this error is that an empty string was specified for an object name. This can happen if you use one scripting statement to create an object name and the next statement to use that name, perhaps in an "invoke" or "getAttribute" command, but you don't check to see if the first statement really returned an object name. For example (the following samples use basic Jacl commands in addition to the wsadmin Jacl extensions to make a sample script): 

#let's misspell "Server" 
set serverName [$AdminControl queryNames type=Server,*] 
$AdminControl getAttributes $serverName

To correct this error, make sure that object name strings have values before using them. For example: 

set serverName[$AdminControl queryNames type=Server,*] 
if {$serverName == ""} {puts "queryNames returned empty - check query argument"} 
else {$AdminControl getAttributes $serverName}

For details on Jacl syntax beyond wsadmin commands, refer to the Tcl developers' site, http://www.tcl.tk .

"The input line is too long" error returned from the wsadmin command on a Windows platform

This error indicates that the Windows command line limit of 1024 characters has been exceeded, probably due to a long path name used within the wsadmin.bat command. The problem can be avoided by using the Windows subst command, which allows you to map an entire path to a virtual drive. To see the syntax of the subst command, enter help subst from a Windows command prompt.

For example if the product resides in c:\TestEnvironment\Beta\WebSphere\AppServer, edit the file c:\TestEnvironment\Beta\WebSphere\AppServer\bin\setupCmdLine.bat as follows: 

     subst w: c:\TestEnvironment\Beta\WebSphere\AppServer

     REM comment out the old line
     REM SET WAS_HOME=C:\TestEnvironment\Beta\WebSphere\AppServer
     
     SET WAS_HOME=w:
     
     REM comment out the old line
     REM SET JAVA_HOME=C:\TestEnvironment\Beta\WebSphere\AppServer\java
     
     SET JAVA_HOME=w:\java

IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.

Related tasks
Troubleshooting by task: What are you trying to do?
Troubleshooting by component: What is not working?