The installation of "Server", "Administration Center" or "Monitoring and Reporting" fails with FATAL ERROR - class com.ibm.ac.coi.ext.ia.plugin.COIProcessPlan FatalInstallException: The Deployment Plan Execution Failed.
When installing any of the Tivoli Storage Manager Server components such as the Tivoli Storage Manager Server, Administration Center or Reporting and Monitoring, it may fail with the following errors in the installation log.
Here is an example of an installation failure of Reporting and Monitoring. The following was logged in "Tivoli_Storage_Manager_for_Reporting_and_Monitoring_InstallLog.log":
Deployement Plan execution general failure:
Status: FATAL ERROR
Additional Notes: FATAL ERROR - The Deployement Plan Execution failed.
Custom Action: com.ibm.ac.coi.ext.ia.plugin.COIProcessPlan
Status: FATAL ERROR
Additional Notes: FATAL ERROR - class com.ibm.ac.coi.ext.ia.plugin.COIProcessPlan FatalInstallException: The Deployment Plan Execution Failed.
For the above error, the following was logged in "log.txt":
Jul 06 16:20:02.669 EST 2010 : FINER : THROW (from com.ibm.ac.coi.ext.ia.plugin.COIPlanCreation.install)
Caused by: java.io.FileNotFoundException: C:\Inst\V6.2 Reporting\184.108.40.206-TSMRPT-TSMALL-WindowsX64\COI\PackageSteps\DB2_9.5\META-INF\packagedIU.xml (The system cannot find the path specified.)
Di Jul 06 16:20:02.685 CEST 2010 : STDERR : Execute Custom Code
Di Jul 06 16:20:02.685 CEST 2010 : STDERR : class com.ibm.ac.coi.ext.ia.plugin.COIPlanCreation FatalInstallException The Deployment Plan is not found or Invalid.
The base path where the installation was installed is too long, which causes the extraction of sub-components to be extracted in sub-directories with a full path that is longer that what is supported by the operating system.
Diagnosing the problem
Check that the path where the installation was extracted is short.
Resolving the problem
As documented in the download instructions:
"Use short path names for the directory used to extract the packages, for example: C:\tsm_images. Path names inside the package are long and extracting the package to a lengthy directory name can cause problems with the 255 character file path limit on Windows.
Note: Ensure that the path does not contain non-ASCII character."