When first invoking the SAS windowing environment, the following errors are typically displayed at the top of your SAS log:

ERROR: The ODS initializer failed to instantiate during SAS startup.
ERROR: Exception text: Assistive Technology not found:
       com.actividentity.sso.javasso.awt_swing.JavaSSOHook.

One of the following error messages might be issued when attempting to produce graphics output with ODS Graphics or with one of the SAS/GRAPH SG procedures:

ERROR: Java virtual machine exception. java.awt.AWTError: Assistive Technology 
       not found:
       com.sentillion.bridge.VExtJava2Hook.hooks.AccEventQueue.
NOTE: The SAS System stopped processing this step because of errors.

ERROR: Java virtual machine exception. java.lang.NoClassDefFoundError: Could not initialize class javax.swing.UIManager.
NOTE: The SAS System stopped processing this step because of errors.

This problem occurs if either of the files below exist in the LIB directory in your Java install directory (such as C:\Program Files\Java\jre6\lib):

awt.properties
accessibility.properties

awt.old
accessibility.old

proc options option=jreoptions;
run;

After renaming the files mentioned above, restart SAS. You should no longer see the "Assistive Technology not found" error in the SAS log.

In certain situations, your system might be set up so that the original awt.properties and the accessibility.properties files are restored the next time you log on to your machine or reboot your machine. If this happens, another way to circumvent this problem is to edit the awt.properties and accessibility.properties files and insert the pound sign character (#) in column 1 of each line of the file. This makes each line in the file a comment line, which circumvents the original problem without having to rename the two files.

Operating System and Release Information