Cisco Cisco IPCC Web Option Installation Guide
Refer to
(http://support.installshield.com/kb/
view.asp?articleid=Q101901) (MacroVision Knowledge Base document ID: Q101901) for
detailed information on how to create a silent installation.
detailed information on how to create a silent installation.
Recovering from Failures of the Installer
There are situations where the Installer might fail for reasons that cannot be anticipated or
controlled.
controlled.
Possible failure scenarios:
•
The system experiences a loss in power.
•
The system might lock up due to the failure of another process.
•
The virtual machine hangs or is accidentally shut down.
•
Using an incorrect or incomplete response file for silent installs.
•
The installer completes successfully, but for some unknown reason you are unable to un-install
using Add/Remove Programs in the Control Panel.
using Add/Remove Programs in the Control Panel.
Under "normal" conditions, when a failure in an InstallShield program occurs, the Installer can
be aborted. An abort event is processed by InstallShield and the setup program attempts to undo
the changes it has made. Changes include file deployments, registry modifications, and other
modifications to Windows shell objects.
be aborted. An abort event is processed by InstallShield and the setup program attempts to undo
the changes it has made. Changes include file deployments, registry modifications, and other
modifications to Windows shell objects.
The InstallShield engine does not include native capabilities for either file backup during install
or file return during uninstallation. These additional tasks are scripted enhancements made to
the Windows based installer. If there is a catastrophic failure during the installation (or any
other state that blocks the uninstaller program from running) the file return needs to be performed
manually.
or file return during uninstallation. These additional tasks are scripted enhancements made to
the Windows based installer. If there is a catastrophic failure during the installation (or any
other state that blocks the uninstaller program from running) the file return needs to be performed
manually.
Warning: Do not attempt to repair a system by only modifying the registry and running
the installation a second time. This causes you to lose the ability to return the system back
to its pre-installation state. If the Installer is run a second time, it backs up the recently
installed versions of files, overwriting the original files previously copied to the backup
directories.
the installation a second time. This causes you to lose the ability to return the system back
to its pre-installation state. If the Installer is run a second time, it backs up the recently
installed versions of files, overwriting the original files previously copied to the backup
directories.
The manual recovery steps outlined below are performing a “Temporary” uninstallation. This
means that files are being restored to their pre-installation (Release 7.0(0)) state, but the previous
database schema is not restored. In the event of a major failure, it might not be easy to determine
whether or not the proper files are in place to rollback the schema. By following the procedures
listed below the system can be returned to a known state from which the Installer can be reapplied.
means that files are being restored to their pre-installation (Release 7.0(0)) state, but the previous
database schema is not restored. In the event of a major failure, it might not be easy to determine
whether or not the proper files are in place to rollback the schema. By following the procedures
listed below the system can be returned to a known state from which the Installer can be reapplied.
Backup files are stored in directories that are immediate children of the original file location.
The directory name is the minor release version number with each numerical component separated
by an underscore, as in ICM_7_2_1_0_0_0_44. For example, files patched in the C:\icm\bin
The directory name is the minor release version number with each numerical component separated
by an underscore, as in ICM_7_2_1_0_0_0_44. For example, files patched in the C:\icm\bin
Installation Guide Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.2(1)
47
Chapter 4: Silent Installation and Manual Recovery from Installer Failures
Recovering from Failures of the Installer