All posts by Senthilraj


Deprecated: Function get_magic_quotes_gpc() is deprecated in /home1/microoat/public_html/blog/wp-includes/formatting.php on line 3964

Deprecated: Function get_magic_quotes_gpc() is deprecated in /home1/microoat/public_html/blog/wp-includes/formatting.php on line 3964

About Senthilraj

DW BI Architect and BI Project Management (Specialized in MicroStrategy). Hobbies/Passion about photography, tennis, music, travel-trekking. Website: www.b-diamonds.com www.facebook.com/SENRAJ81 www.linkedin.com/in/senraj

Critical Issue Alert: MicroStrategy 9.0.0 Hotfix 2 can cause instability or folder access problems

Critical Issue Alert: MicroStrategy 9.0.0 Hotfix 2 can cause instability or folder access problems

Please refer to the following technical notes for more details:

  • TN 31747 – In MicroStrategy 9.0.0 HF2, when trying to open a folder, M8MulPrc_32 or MJMulPrc are continuously spawned and the client application hangs
  • TN 31658 – “Invalid procedure call or argument” error message appears when trying to access a folder in MicroStrategy 9.0.0 after a migration with Object Manager 9.0.0 HF2

Both issues are corrected in MicroStrategy 9.0.0 Hotfix 3. Customers who are on 9.x are urged to upgrade to this latest Hotfix that is available on the MicroStrategy Download Site.

 

MicroStrategy Product Releases

MicroStrategy 9.0.0 Hotfix 3
MicroStrategy 9.0.0 Hotfix 3 is now generally available on the MicroStrategy Download Site to licensed customers. This is a maintenance release for customers currently running the 9.0.x version of the software. This release contains new issue corrections, as well as all corrections provided in the earlier 9.0.0 Hotfix 1 and 9.0.0 Hotfix 2 releases. In particular, Hotfix 3 addresses the two critical issues that may affect the stability and folder accessibility of the MicroStrategy environment as described in the technical notes TN 31747 and TN 31658. The Readme is available in the MicroStrategy Knowledge Base.

Installation problem in servers

In few version like Windows 2003, Vista; installation may stuck due to firewall issue or security issues.

How to resolve this? This issue may appear because of the 3rd party utilities.

Steps:

1)       Install manually all the 3rd party installation under MSTR setup package

2)      Remove the 3rd party installation setups from the MSTR package (from 3rd party folder)

3)      Now install MSTR setup

4)      MSTR setup will skip the 3rd party utilities since it’s not present in the 3rd party folder.

Silent installation/Un-Installation

Two files required to install/un-install using silent method.

1)      Setup.iss

2)      Response.ini

Once the two files are created place it in the folder where setup.exe place (installation setup) exist.

Open command prompt and type the following command to install the same.

D:\MSTR\Installations\Setup.exe –ResponseFile=”D:\mstr\response.ini” –s  -f1D:\mstr\setup.iss –f2D:\mstr\setup.log

Example: Setup.iss

[InstallShield Silent]

Version=v7.00

File=ReponseFile

[File Transfer]

OverwrittenReadOnly=NotToAll

[Application]

Name=MicroStrategy

Version=9.0

Company=MicroStrategy

Lang=0009

[{B339F3B3-E78C-45E8-B4D2-3C46C1C13663}-DlgOrder}

Count=0

Example: Response.ini

[Installer]
HideAllDialogs=TRUE
ForceReboot=TRUE
StopAllServices=TRUE
EnterpriseManagerOverwrite=TRUE
CreateShortcuts = TRUE
ShowConfigWizard = FALSE
RunConfigWizard = FALSE
StopIIS = TRUE
AnalyticsOverwrite = TRUE
TutReportingOverwrite = TRUE
EnableTracing = TRUE
ShowWelcomeScreen = FALSE
ConfigWizardResponseFile = response.ini
CheckTCPIP=TRUE
CheckIIS=TRUE
CheckSP=TRUE
OverwriteDSN = TRUE
[Welcome]
HideDialog=TRUE
RemoveAll=FALSE
[UserRegistration]
HideDialog=TRUE
UserName=MicroStrategy Brasil
CompanyName=MicroStrategy Inc.
LicenseKey=<KEY>
[SetupType]
HideDialog=TRUE
Type=Typical
[SuiteTarget]
HideDialog=TRUE
TargetDirectory=D:\Program Files\MicroStrategy
[ComponentSelection]
HideDialog=TRUE
### Visible Components ###
DesktopAnalystVisible=TRUE
DesktopDesignerVisible=TRUE
ArchitectVisible=TRUE
ProjectBuilderVisible=TRUE
ServerAdminVisible=TRUE
CommandManagerVisible=TRUE
EnterpriseManagerVisible=TRUE
ObjectManagerVisible=TRUE
IServerVisible=TRUE
SDKVisible=TRUE
AnalyticsModulesVisible=TRUE
NCSAdminVisible=TRUE
DeliveryEngineVisible=TRUE
SubscriptionEngineVisible=TRUE
SubscriptionPortalVisible=TRUE
JMSGatewayVisible=FALSE
WebGatewayVisible=FALSE
TutorialReportingVisible=TRUE
TutorialDeliveryInstallVisible=TRUE
TutorialDeliveryConfigureVisible=TRUE
WebReporterVisible=TRUE
WebAnalystVisible=TRUE
WebProfessionalVisible=TRUE
WebUniversalReporterVisible=TRUE
WebUniversalAnalystVisible=TRUE
WebUniversalProfessionalVisible=TRUE
WebServicesJSPVisible=FALSE
WebServicesASPNETVisible=TRUE
OfficeVisible=TRUE
eTrainerForWebVisible=TRUE
FunctionPluginVisible=FALSE
SequeLinkVisible=TRUE
IServerOLAPServicesVisible=TRUE
IServerReportServicesVisible=TRUE
### Components to Install (TRUE) or Remove (FALSE) ###
DesktopAnalystSelect=TRUE
DesktopDesignerSelect=TRUE
ArchitectSelect=TRUE
ProjectBuilderSelect=TRUE
ServerAdminSelect=TRUE
CommandManagerSelect=TRUE
EnterpriseManagerSelect=TRUE
ObjectManagerSelect=TRUE
IServerSelect=TRUE
SDKSelect=TRUE
AnalyticsModulesSelect=TRUE
NCSAdminSelect=TRUE
DeliveryEngineSelect=TRUE
SubscriptionEngineSelect=TRUE
SubscriptionPortalSelect=TRUE
TutorialReportingSelect=TRUE
TutorialDeliveryInstallSelect=TRUE
TutorialDeliveryConfigureSelect=TRUE
WebProfessionalSelect=TRUE
WebUniversalReporterSelect=TRUE
WebUniversalAnalystSelect=TRUE
WebUniversalProfessionalSelect=TRUE
WebServicesJSPSelect=FALSE
WebServicesASPNETSelect=TRUE
OfficeSelect=TRUE
WebServerASPNETSelect=TRUE
WebUniversalServerJSPSelect=TRUE
WebUniversalServerASPSelect=TRUE
eTrainerForWebSelect=TRUE
FunctionPluginSelect=
SequeLinkSelect=TRUE
IServerOLAPServicesSelect=TRUE
IServerReportServicesSelect=TRUE
[Programfolder]
HideDialog=TRUE
Name=MicroStrategy
[ServerDefinitionSetting]
HideDialog=TRUE
OverwriteServerDefinition=FALSE
[WebVirtualDirectory]
HideDialog=TRUE
VirtualDirectory=MicroStrategy
ReconfigureVirtualDirectory=TRUE
[PortalVirtualDirectory]
HideDialog=TRUE
VirtualDirectory=NarrowcastServer
ReconfigureVirtualDirectory=TRUE
[WebServicesVirtualDirectory]
HideDialog=TRUE
VirtualDirectory=MicroStrategyWS
ReconfigureVirtualDirectory=TRUE
[TutorialReportingSetting]
HideDialog=TRUE
OverwriteDSN=FALSE
[WebVirtualDirectory]
HideDialog=TRUE
VirtualDirectory=MicroStrategy
ReconfigureVirtualDirectory=TRUE
[PortalVirtualDirectory]
HideDialog=TRUE
VirtualDirectory=NarrowcastServer
ReconfigureVirtualDirectory=TRUE
[WebServicesVirtualDirectory]
HideDialog=TRUE
VirtualDirectory=MicroStrategyWS
ReconfigureVirtualDirectory=TRUE
[OfficeWebServicesURL]
HideDialog=TRUE
AllowBlankURL=FALSE
URL=http://localhost/MicroStrategyWS/mstrws.asmx
[MSOfficeLoadOptions]
HideDialog=TRUE
ConfigureExcel=TRUE
ConfigurePowerpoint=TRUE
ConfigureWord=TRUE
[IServerServiceAccount]
HideDialog=TRUE
SkipAccountSetting=FALSE
Login=Administrator
Password=
ServiceStartUp=AUTO
[NarrowcastServiceAccount]
HideDialog=TRUE
SkipAccountSetting=FALSE
Login=Administrator
Password=
[Summary]
HideDialog=TRUE
[Finish]
HideDialog=TRUE

To add/remove components; Change true or false for components.

Customizing Narrowcast XSL

In Narrowcast Server, when you use report in EXCEL document, instead of normal report output; you can customize the output result based on your own design by modifying default Narrowcast XSLT.

In order to design Narrowcast XSLT, first we need to understand the Report XML and its content present in XML file.

How to get the get the report xml:

  1. Run the corresponding report in the WEB.
  2. In the Address Bar, enter ‘&XML=1’ at the end of the URL as shown below.
  3. Right click in Browser and Select the ‘ViewSource’ option.
  4. Search for ‘<mi’ in the Source and starting from the ‘<mi’ tag copy till end tag (i.e) ‘mi>’.
  5. Paste the copied text in notepad and save it in ‘.xml’ file.

Note: Report data Tag starts with <RH>

Narrowcast XSLT’s and Tags specific to spreadsheet

Note: All aspects of this XML specification, including element (tag) names, attribute names, and attribute values are case sensitive. •

  • The pt-container is the root level of every Excel XML document element that contains the table tag. This tag is required.
  • The table tag contains both content and formatting tags for turning data into a well-formatted grid. The resulting grid overwrites a contiguous rectangle of cells in an Excel workbook when an Excel document is rendered. An Excel XML document element can contain only one table tag.
  • The fonts tag contains the set font definitions that control the font characteristics of cells written into the Excel workbook. Font definitions include font type, color, size, weight, and modifiers like italic. An Excel XML document element can contain only one fonts tag.
  • The font tag contains the definition of a specific font used for this document element. Zero or more font tags are required.
  • The styles tag contains the set style definitions that control cell formatting for cells written into the Excel workbook. Style definitions include all font characteristics as well as background color, orientation, alignment, and borders. An Excel XML document element can contain only one styles tag.
  • The style tag contains the definition of a specific style that is used for this document element. Zero or more style tags are required.
  • The formats tag contains the set of format strings that are used to format date, time, and numeric cell contents. An Excel XML document element can contain only one formats tag.
  • The format tag contains the definition of a specific format string that is used for this document element. Zero or more format tags are required.
  • Each row in a table contains cells. A blank row can be represented by the inclusion of a row containing an empty cell. One or more row tags are required.
  • Each cell in a row contains the data that should be placed into the corresponding cell in the resulting grid. One or more cell tags are required.

Sample Report output and used to design the XSL

Country Region Revenue
USA Northeast

$2,334,864

Mid-Atlantic

$3,413,340

Southeast

$2,016,186

Central

$1,773,270

South

$1,380,991

Northwest

$1,485,182

Southwest

$2,816,334

Web Web

$1,716,267

Sample XSL created for the above Report (you can take default Narrowcast XSL and Modify the content except parent tags)

[sourcecode language=”xml”]
<?xml version="1.0"?>;
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">;
<xsl:output method="xml" omit-xml-declaration="yes" indent="yes" />;
<xsl:template match="/">;

<pt-container>;

<table row-count="3" column-count="12">;

<fonts>;
<font name="ObjectName1" family="Arial" size="10" weight="bold" style="italic" />;
<font name="ObjectName2" family="Arial" size="10" weight="bold" style="italic" />;
<font name="ObjectName3" family="Arial" size="10" weight="bold" style="italic" />;
<font name="ObjectValue1" family="Coronet" size="11" weight="bold" color="12" />;
<font name="ObjectValue2" family="Coronet" size="11" weight="bold" color="12" />;
<font name="ObjectValue3" family="Coronet" size="11" weight="bold" color="12" />;
</fonts>;

<styles>;
<style name="SObjectName1" background-color="47" align="center" border-top="style:medium" border-right="style:medium" border-left="style:medium" border-bottom="style:medium" font="ObjectName1" />;
<style name="SObjectName2" background-color="44" align="center" border-top="style:medium" border-right="style:medium" border-left="style:medium" border-bottom="style:medium" font="ObjectName2" />;
<style name="SObjectName3" background-color="34" align="center" border-top="style:medium" border-right="style:medium" border-left="style:medium" border-bottom="style:medium" font="ObjectName3" />;
<style name="SObjectValue1" background-color="47" align="center" border-top="style:medium" border-right="style:medium" border-left="style:medium" border-bottom="style:medium" font="ObjectValue1" />;
<style name="SObjectValue2" background-color="44" align="center" border-top="style:medium" border-right="style:medium" border-left="style:medium" border-bottom="style:medium" font="ObjectValue2" />;
<style name="SObjectValue3" background-color="34" align="center" border-top="style:medium" border-right="style:medium" border-left="style:medium" border-bottom="style:medium" font="ObjectValue3" />;
</styles>;

<formats/>;
<row>;
<cell style="SObjectName2" type="8">;Region</cell>;
<xsl:for-each select="/mi/rit/vw/gr/rh/rw">;
<xsl:if test="./h[1][@rfd=’4′]“>;
<cell style="SObjectValue2">;<xsl:value-of select="./h[2]/fv"/>;</cell>;
</xsl:if>;
<xsl:if test="./h[1][@rfd!=’4′]“>;
<cell style="SObjectValue2">;<xsl:value-of select="./h[1]/fv"/>;</cell>;
</xsl:if>;
</xsl:for-each>;
</row>;

<row>;
<cell style="SObjectName3" type="8">;Revenue</cell>;
<xsl:for-each select="/mi/rit/vw/gr/rh/rw">;
<xsl:if test="./h[1][@rfd=’4′]“>;
<cell style="SObjectValue3">;<xsl:value-of select="./mv"/>;</cell>;
</xsl:if>;
<xsl:if test="./h[1][@rfd!=’4′]“>;
<cell style="SObjectValue3">;<xsl:value-of select="./mv"/>;</cell>;
</xsl:if>;
</xsl:for-each>;
</row>;

</table>;

</pt-container>;
</xsl:template>;
</xsl:stylesheet>;
[/sourcecode]

Output for the above Report along with the XSL

1) Save the above XSLT

2) Insert the XSLT as XSL file in Narrowcast Server

3) In the documents, while mapping report in EXCEL document; Map this XSLT for the particular report

4) complete the service (as we do normally)

5) Run the service, you will get the customized output

Narrowcast XLST output

Narrowcast XLST output

Cannot save or move object System Hierarchy with id xxxx and type Hierarchy

Error: Cannot save or move object `System Hierarchy` with id ‘xxxx’ and type ‘Hierarchy’.

Symptoms: When try to create/modify new attribute the above error occurs.

Solution: Download ScanMD (8x), You can use the ScanMD (8x) for version 9 also.

1.  Start ScanMD
2.  Go to Step 3, and click “Add test”
3.  Select TQMS357866.dll

And continue the ScanMD process, Now the above error will get fixed.

Suggestions: Don’t create/modify Schema object in parallel.

Download the file here.