EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  3. Topics

KB484231: Patch installer cannot find the principal.sh file when the home and install paths are different

Richard Gardner

Vice President, Project Delivery • Strategy

This article addresses the error encountered when MicroStrategy is installed and the home path is not the parent of the install path. This article also provides a workaround to avoid this error and to successfully install the MicroStrategy 2020 Patch Installer.

Description

When Strategy is installed and its home path is not a parent of the install path, an error occurs and the Strategy 2020 Patch Installer installation fails. For example, the patch installation will fail in the following configuration:

  • Home path: 
    /var/opt/Strategy
  • Install path: 
    /opt/Strategy

The patch installation is successful with the following configuration:

  • Home path: 
    /opt/Strategy
  • Install path: 
    /opt/MicroStrategy/install

Why is this happening?


After the patch installer copies 

libMIXTBFCT.so
under the Strategy 
lib
directory, it checks if the owner of that library file needs to be altered by parsing 
Principal.sh
. The location of 
Principal.sh
is 
/env
.
However, when searching for 
Principal.sh
, the installer uses 
<MSTR_HOME_PATH>/
install/_uninst
first (retrieved from 
mstrinstallers.xml
), navigates two levels up, then to the 
env
directory.
When the Strategy home path is not a parent of the install path, it causes the detection of 
Principal.sh
to fail.  
 

Solution 


Instead of the 

<uninstdir>
value, which indicates the 
_uninst
directory path, retrieve the 
<home>
value from 
mstrinstaller.xml
to accurately and reliably locate 
Principal.sh
. 

Workaround


Use the following steps as a workaround after the path installation fails:

  1. Copy 
    Principal.sh
    from 
    /env
    to the location where the patch installer is searching. This can be checked in 
    Strategypatchinstaller.log
    :
    • SEVERE: An error occurred during patch installation: /opt/env/Principal.sh (No such file or directory)
  2. Inside the patch installer directory, or wherever 
    StrategyPatchInstaller.sh
    was launched, there may be a 
    tmp
     directory with the 
    libMIXTBFCT.so
    file inside. Remove the 
    tmp
    directory.
  3. Inside 
    <MSTR_INSTALL_PATH>/lib
    , if the new l
    ibMIXTBFCT.so
    file is already copied, delete it.
  4. Run the patch installer again.
  5. If the patch installation is successful, delete the copied 
    Principal.sh
    file in 
    /opt/env.
Comment

0 comments

Details

Knowledge Article

Published:

May 4, 2020

Last Updated:

May 4, 2020