Open topic with navigation
Error 101: Illegal argument was passed.
Error 102: This program requires a Java Virtual Machine Version 1.5 or greater to run properly. Please refer to Configuring the LifeKeeper GUI to verify your setup.
Error 103: Could not set Look and Feel for LifeKeeper GUI.
Error 104: <filename> Image could not be loaded.
Error 106: Error trying to get data over RMI. Could not complete action.
Error 107: Failed to create Global Resource Instance.
Error 108: Failed to create Global Resource.
Error 109: Dialog requires a Server to be selected.
Error 112: Could not match Resource Instance to Global Equivalency.
Error 114: <server name> Security Exception caused connection failure to this server. Please note that this failure may result in degraded cluster resource rendering. Please refer to Configuring the LifeKeeper GUI to verify browser and/or Java plugin settings. Also, refer to Java Security Policy to verify that your Java Policy file is installed properly.
Error 115: <server name> Name of this server could not be resolved resulting in a connection failure to this server. Please note that this failure may result in degraded cluster resource rendering. Please refer to Configuring the LifeKeeper GUI to verify network naming conventions.
Error 116: <server name> This server could not resolve the name of this client host resulting in a connection failure to this server. Please note that this failure may result in degraded cluster resource rendering. Please refer to Configuring the LifeKeeper GUI to verify network naming conventions.
Error 117: Initial connection to server failed. LifeKeeper GUI will continue trying to connect. Please refer to Starting and Stopping LifeKeeper and Starting/Stopping the GUI Server to verify that LifeKeeper and the LifeKeeper GUI server are active on this system.
Error 118: Incompatible client and server packages caused connection failure. Please verify that the steeleye-lkGUI package versions are compatible between the target server and the server from which the client was started.
Error 119: Could not export remote object.
Error 120: Encountered exception when invoking remote method.
Error 121: Administrative java bean could not be initialized.
Error 122: Administrative java bean has no dialog classes to load. The properties file describing the administrative java bean is missing the "list" property.
Error 123: The properties file describing the administrative java bean has a missing property.
Error 124: Failed to find property bundle.
Error 125: Security Exception trying to create URLClassLoader. Please verify that the .java.policy file grants the proper permissions. You should typically create a .java.policy file in your home directory. The contents of the .java.policy file are case sensitive, so it is best to copy the sample file that is distributed with the LifeKeeper GUI package.
If you are using a browser plug-in for Java, then the user home directory that is being used for the java environment can be verified by enabling the Java console and examining the first few lines that are displayed. Refer to Running the GUI on a Remote System for more information on configuring the GUI client.
Error 126: Could not find resource on server.
Error 127: Could not find extend properties file for this kit.
Error 128: Internal properties file error.
Error 129: Cannot establish an RMI connection to the server. Verify the LifeKeeper GUI Server is running on the server.
Note: If you receive this message while trying to create communications paths, then there may be a conflict with a firewall running on the LifeKeeper server. See Running LifeKeeper with a Firewall for more information.
Error 130: The tag entered is being used by another resource. Please enter another tag.
Error 131: Exception calling invokeAndWait method to update the user interface.
Error 132: Encountered exception when invoking administrative java bean.
Error 133: Invalid value entered for equivalency priority. The priority value must be in the range of 1 through 999.
Error 134: The equivalency priority value conflicts with another priority in the table. Each equivalency priority value must be unique in the table.
© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.
Open topic with navigation