To avoid failed installs, make sure that your operating system is updated to the most current version and that all system requirements are met. See
Prerequisites
in the
iManager 2.6 Installation Guide.
Recovery from a failed install varies by platform, but in every case you need to assess the problem based upon the error message generated during installation.
If the error involves one of these components, check the specified log files for errors:
NICI: installed directory\temp\wcniciu0.log
Apache: root install directory\apache_install.log . For example, C:\Program Files\Novell\apache_install.log.
Tomcat: tomcat install directory\Apache_Tomcat_InstallLog.log . For example, C:\Program Files\Novell\Tomcat\Apache_Tomcat_InstallLog.log.
Check the iManager install log file ( servlet root\WEB_INF\log\iManager_Install_2.6_InstallLog.log ) for any errors.
If the log file does not give sufficient information to identify the problem, rerun the install in debug mode.
To view or capture the debug output from an installer, open and copy the console output to a text file for later review.
Immediately after launching the installer, hold down the Ctrl key until a console window appears.
After the install has completed, click the icon in the upper left corner of the console window and select
> .Change the buffer size to 3000, then click
.In the Layout window, select
> > > .Open a text editor and paste the output of the debug in it.
Identify and correct any errors or stack traces, then rerun the install.
Check the iManager install log file ( servlet root\WEB_INF\log\iManager_Install_2.6_InstallLog.log) for any errors.
If the log file does not give sufficient information to identify the problem, rerun the install in debug mode.
At the command line, enter the following:
export LAX_DEBUG=true
Identify and correct any errors or stack traces, then rerun the install.
Check the iManager install log file ( /var/log/Novell/iManager_Install_2.6_InstallLog.log) for any errors.
If the log file does not give sufficient information to identify the problem, rerun the install in debug mode.
At the command line, type the following:
export LAX_DEBUG=true
Identify and correct any errors or stack traces, then rerun the install.