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
  2. Topics
  3. KB43861: What information does the mstrinstalls.xml file contain?

KB43861: What information does the mstrinstalls.xml file contain?


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This article explains the individual xml elements along with the base structure of the mstrinstalls.xml

mstrinstalls.xml is a file that exists starting in MicroStrategy 9.3.x and newer versions. This file is located in the $HOME directory of the user that installed MicroStrategy 9.3.x or newer on a UNIX/Linux machine. For further information regarding the location and purpose of the mstrinstalls.xml, refer to the following MicroStrategy Knowledge Base technical note:

 

KB42406 - The vpd.properties file is replaced by mstrinstalls.xml for UNIX/Linux installations in MicroStrategy 9.3.x and newer

 

However, it may be necessary to edit this file in order to correct an existing installation. An explanation of each XML element along with the base structure is described below. The base empty structure of the mstrinstalls.xml is as follows :

 

<Instances>
<Instance>
<host></host>
<home></home>
<version></version>
<build></build>
<hfbuild></hfbuild>
<lastop></lastop>
<modtime></modtime>
<medialoc></medialoc>
<hfmedialoc></hfmedialoc>
<uninstdir></uninstdir>
<dirty></dirty>
</Instance>
</Instances>

 

Each of these elements within the XML file has a purpose, as described below:

Instances

This is the root element for the XML File. If multiple instances exist, they will exist within this element.

Instance

This defines each individual instance. An instance will represent a single installation. An instance will contain many elements of an installation. There can be multiple 'instance' elements if multiple installations exist on the machine.

host

This is the host machine name of the machine which MicroStrategy is installed.

home

This defines the home directory of MicroStrategy. The default location is "/var/opt/MicroStrategy".

version

This defines the GA version of which is installed. Example: "9.3.0".

build

This should be the exact build of the GA version installed. Example of 9.3.0: "9.3.000.055".

hfbuild

If a hotfix has been installed, this field will contain the build version with the hotfix. If no hotfix is installed, this should be the same version as the GA. Example of 9.3.0 Hotfix 4: "9.3.080.055".

lastop

This defines the last operation done on the installation. This can be Repair, Fresh Install, etc.

modtime

The last time this installation has been modified or altered by a MicroStrategy Installer.

medialoc

This defines the location where the downloaded installation was extracted to and installed from. If this location no longer exists or is invalid, operations such as a repair install may fail.

hfmedialoc

This defines the location where the downloaded Hotfix installation was extracted to and installed from. If this location no longer exists, operations such as a repair install for a Hotfix may fail. If no Hotfix has been applied in this environment, the entry is: "undefined".

uninstdir

This defines the location where the uninstaller for MicroStrategy is located. The default location is "/opt/MicroStrategy/_uninstall".

dirty

If a previous installation was not successful, this flag will be set to "true". If this flag is set to "true", any MicroStrategy Installer will prompt for this installation to have a repair install performed on it. When this flag is set to "false", it is assumed that the integrity of the installation is correct.

 

Note: Modifying any of these values should be done with full knowledge of the environment and proper caution. It is best to perform a backup of the mstrinstalls.xml before performing any modifications. If this file contains incorrect information, any further MicroStrategy installation operations performed may fail or cause an existing installation to become corrupt. In such situations, it may be required to perform a complete uninstall/reinstall of MIcroStrategy.


Comment

0 comments

Details

Knowledge Article

Published:

July 14, 2023

Last Updated:

January 31, 2024