Archived Content: This information is no longer maintained and is provided "as is" for your convenience.
Summary
Error
When attempting to start the Server Automation (SA) client on some Windows 7 workstations, as soon as the Login button is pressed, the client windows freezes and becomes grayed out. The client never connects to the SA core. This may occur the any time the client is started, though most frequently it will occur when a new client is installed and run the first time. A stack trace similar to the following will also be present in the error.log file in the SA client folder on the workstation
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at com.opsware.launcher.ClientLauncher.launch(ClientLauncher.java:296)
at com.opsware.launcher.LaunchDialog$LoginAction.actionPerformed(LaunchDialog.java:316)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.AbstractButton.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicRootPaneUI$Actions.actionPerformed(Unknown Source)
at javax.swing.plaf.basic.BasicComboBoxUI$Actions.actionPerformed(Unknown Source)
at javax.swing.plaf.basic.BasicComboBoxUI$Handler.actionPerformed(Unknown Source)
at javax.swing.JTextField.fireActionPerformed(Unknown Source)
at javax.swing.JTextField.postActionEvent(Unknown Source)
at javax.swing.JTextField$NotifyAction.actionPerformed(Unknown Source)
at javax.swing.SwingUtilities.notifyAction(Unknown Source)
at javax.swing.JComponent.processKeyBinding(Unknown Source)
at javax.swing.JComponent.processKeyBindings(Unknown Source)
at javax.swing.JComponent.processKeyEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.KeyboardFocusManager.redispatchEvent(Unknown Source)
at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(Unknown Source)
at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(Unknown Source)
at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(Unknown Source)
at java.awt.DefaultKeyboardFocusManager.dispatchEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Cause
Fix
To workaround the problem, set a valid locale for the SA Client.
- Start the client
- Set values as needed and appropriate
- Click on the Advanced button
- Click on the resulting More button
- Set the locale field to a valid value for your workstation; typically, this will be one of <en>, <ja>, or <ko>
- Login to the SA core