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 application server at startup. This is because some commands act upon running application servers. This error indicates that no connection could be established.
The port that wsadmin should send on depends on the server process wsadmin is trying to connect to.
"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
#let's misspell "Server" set serverName [$AdminControl queryNames type=Srever,*] $AdminControl getAttributes $serverName
set serverName[$AdminControl queryNames node=mynode,type=Server,name=server1,*] 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 2048 characters has been exceeded, probably due to a long profile path used within the wsadmin.bat command. You may get this error when running wsadmin in a Windows command prompt or calling wsadmin from a .bat file, an ant build file, or Profile Creation Tool. If this error results in running wsadmin in a way other than from the Profile Creation Tool, you can avoid the problem 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.
SET CUR_DIR=%cd% cd /d "%~dp0.." SET WAS_HOME=%cd% cd /d "%CUR_DIR%" @REM add the following two lines to workaround Windows 2K command line length limit subst w: %WAS_HOME% set WAS_HOME=w: ... ...
SET WAS_USER_PROFILE=... SET USER_INSTALL_ROOT=... SET WAS_HOME=c:\Program Files\IBM\WebSphere\AppServer SET JAVA_HOME=c:\Program Files\IBM\WebSphere\AppServer\java @REM add the following three lines to workaround Windows 2K command line length limit subst w: %WAS_HOME% set WAS_HOME=w: set JAVA_HOME=%WAS_HOME%\java ... ...
If this error occurred while running the Profile Creation Tool, you have to rerun the Profile Creation Tool to provide a shorter profile path with a shorter profile name. If this does not fix the problem, then you have to follow the same instruction given above to edit the setupCmdLine.bat file resided in the bin directory of your WebSphere install. After editing the file, rerun Profile Creation Tool. If the same problem persists, then you may have to reinstall WebSphere with a shorter install path.
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.
WASX701E: Exception received while running file "scriptName.jacl"; exception information: com.ibm.bsf.BSFException: error while evaluating Jacl expression: missing close-bracket
This error is caused by a mix-up between the code page that the scripting client expects to see and the code page in which the Jacl script was written.
Separator exception
You must use forward slashes (/) as your path separator. Backward slashes (\) will not work.
Related tasks
Troubleshooting by task
Troubleshooting by component