Troubleshooting administration

Use the following information to troubleshoot administration, including starting and stopping servers, using the xscmd utility, and so on.

Procedure

Problem: Administration scripts are missing from the profile_root/bin directory of a WebSphere® Application Server installation.

Cause: When you update the installation, new script files do not automatically get installed in the profiles.

Solution: If you want to run a script from your profile_root/bin directory, unaugment and reaugment the profile with the latest release. For more information, see Unaugmenting a profile using the command prompt and Creating and augmenting profiles for WebSphere eXtreme Scale.

Problem: When you are running a xscmd command, the following message is printed to the screen:

java.lang.IllegalStateException: Placement service MBean not available.
[]
        at
com.ibm.websphere.samples.objectgrid.admin.OGAdmin.main(OGAdmin.java:1449)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:267)
Ending at: 2011-11-10 18:13:00.000000484

Cause: A connection problem occurred with the catalog server.

Solution: Verify that your catalog servers are running and are available through the network. This message can also occur when you have a catalog service domain defined, but less than two catalog servers are running. The environment is not available until two catalog servers are started.

Problem: When you are running a xscmd command, the following message is printed to the screen:
```
CWXSI0066E: Unmatched argument argument_name was detected.
```
Cause: You entered a command format that the xscmd utility did not recognize.

Solution: Check the format of the command. You might encounter this issue when running regular expressions with the -c findbyKey command. For more information, see Querying , displaying, and invalidating data.
Problem: All of start, stop, and xscmd commands fail with a java.lang.UnsupportedClassVersionError error.
For example, you might see one of the following errors when you are using the start, stop orxscmd utility commands:
```
The java class could not be loaded. java.lang.UnsupportedClassVersionError: 
(com/ibm/ws/xs/admin/wxscli/WXSAdminCLI) bad major version at offset=6
```
```
The java class could not be loaded. java.lang.UnsupportedClassVersionError: 
(com/ibm/ws/objectgrid/server/impl/ProcessLauncher) bad major version at offset=6
```
Cause: The commands are running with an unsupported Java™ version for the WebSphere eXtreme Scale.

Solution: Update the JAVA_HOME environment variable to point to a supported Java Development Kit (JDK) installation. For supported JDK versions and instructions on updating the JDK, see Java SE considerations.