Installer Messages

CommandLineArgs.missingMaxLogSize You changed the default maximum log size using -maxLogSize but did not provide the new value for new log size. Provide the new value for the maximum log size, followed by either 'k' or 'm'.
Explanation

You changed the default maximum log size using -maxLogSize but did not provide the new value for log size.

Action

Provide the new value for the maximum log size, followed by either 'k' or 'm'.


DLInitFilesProgressPanel.cannotLoadJNI Unable to load resource {0}. Run the installer again with a 32-bit JDK instead of a 64-bit JDK.
Explanation

This message is displayed when the user uses 64-bit JDK to install an older version that did not support 64-bit JDK. The 64-bit library will be missing.

Action

Run the installer again with a 32-bit JDK instead of a 64-bit JDK.


DLInitFilesProgressPanel.unsupportedPlatformInternal The installer has requested files for {0} but no files are available for that operating system at {1}.

DLInitFilesProgressPanel.unsupportedPlatformProduction Release {0} does not support {1}. See the system requirements documents on the Software AG Empower web site for supported operating systems for each product in release {2}.
Explanation

The user is trying to install on a platform that not supported on the current install machine.

Action

The user should select a different product suite that does support the current platform.


DLJarsProgressPanel.errorImagePlatformAs400 April 2011 and later Software AG Installers do not support creation of images for IBM AS/400 systems. The installer will now exit.

DistManInstallMain.relaunchBadJavaHome The JDK located at {0} is version {1}, which only supports classes up to major.minor version {2}. You must execute the installer or uninstaller with a JDK that supports classes with a major.minor of at least {3}. You can use the -javaHome command line option to launch the uninstaller using a different JDK. The JDK located in {4} is not working; verify that the path is correct.
Explanation

This message is displayed when the user gave the installer or uninstaller an alternate JDK to launch the installer or uninstaller, and the path was incorrect. See 'DistManInstallMain.relaunchNoJavaHome' for more details -- {4} is the location the user gave for the JDK installation.

Action

The user should provide a proper JDK installation directory.


DistManInstallMain.relaunchJavaHomeSetText The JDK located at {0} is version {1}, which only supports classes up to major.minor version {2}. However, you must execute the installer or uninstaller with a JDK that supports classes with a major.minor of at least {3}. Please provide a JDK installation directory that meets these requirements; the JDK located at {4} does not meet these requirements or does not exist.
Explanation

This message displayed when the user provides an alternate JDK to execute the installer or uninstaller, and the given path is too old or is not a proper directory. {0} - the JDK that is running this client {1} - the current JDK version {2} the major.minor class version that this JDK supports {3} - the required major.minor {4} - the location the user gave as an alternate JDK to run the installer or uninstaller.

Action

Supply a proper JDK directory.


DistManInstallMain.relaunchJavaHomeText The JDK located at {0} is version {1}, which only supports classes up to major.minor version {2}. However, you must execute the installer or uninstaller with a JDK that supports classes with a major.minor of at least {3}. Download a JDK that meets these requirements. See the Using the Software AG Installer guide for details and instructions.
Explanation

If the user tries to launch the installer or uninstaller with a JDK that is too old, this message will be shown. The user will be queried to supply an alternate location for a more recent JDK. {0} - location of the current JDK executing the installer or uninstaller {1} -- version of the current JDK {2} major.minor class version the current version of JDK supports, {3} -- the minimum that is required to execute the client classes.

Action

Enter the newer JDK installation directory and the installer or uninstall will execute themselves again using that JDK.


DistManInstallMain.relaunchNoJavaHome The JDK located at {0} is version {1}, which only supports classes up to major.minor version {2}. You must execute the installer or uninstaller with a JDK that supports classes with a major.minor of at least {3}. You can use the -javaHome command line option to launch the uninstaller using a different JDK.
Explanation

This message is displayed when the user tries to execute the installer or uninstaller with a JDK version that is too old. This can happen, for example, if the user installs webMethods 6 (which includes JDK 1.3 or 1.3.1) and tries to run the uninstaller. The message parameters are {0} - Installation home directory for java, {2} major.minor version of the java the user used to run the installer or uninstaller {3} - the major.minor version that is required as an absolute minimum.

Action

As long as the user is not using console mode and running the installer, the user can point the installer or uninstaller at a newer JDK installation; the installer or uninstaller will launch again using that JDK.


InstallDirWizardPanel.cannotFindRegistryKeys The Software AG Uninstaller cannot find the proper registry keys for this installation and cannot continue.

LockedFilesWizardPanel.explainText The installer has detected running processes that must be stopped before you can continue. First shut down the listed products; this might also automatically shut down other listed processes. Shut down products by stopping services or exiting applications. Do not use Task Manager. If you need shutdown instructions, see the product documentation.

SAGEnvironmentManagerUnix.configFileNotReadable The installation user has no permissions to read the config file "{0}"! Change the permissions and try again or exit the current installation.
Explanation

The message that pops up when the current installation user has no read permission for the config file '/etc/sagconf.xml' on Unix systems.


ZipManager.errorLockedFile The process cannot access the file because another process has locked a portion of the file.