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.
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.
A while ago I had the opportunity to prepare a short training on the FreeForm SQL reports for some of my colleagues. I thought I’d better share this with you as well, so… here is a not-at-all-exhaustive list of things worth knowing about this type of report.
What is a FF SQL?
FreeForm SQL (aka FreeStyle SQL) is a type of report which allows the designer to define its own SQL code. Notice this is a rather different approach than what we are normally used to in MicroStrategy, where we would usually let the SQL Engine do the job.
When should it be used?
1. Whenever you tried everything (VLDB properties, Metric Levels, Attribute Relationships, Table Logical Size, Data Model changes…) and the SQL Engine still doesn’t perform that join the way you want it to.
2. Whenever you want to use a data source which does not exist in the Warehouse Catalog. That’s right, with FF SQL you can use almost any data source, including those tables you see in the left hand side of the Catalog.
How do I recognize it?
You don’t, at least not from the outside. You can either edit a report and see if you can spot the unnoticeable “Freeform SQL Definition” button, or you can right click on the report and make a component search. If it has no components, you found it.
So, unless you set up some naming convention for FF SQL reports you will very soon lose track of them.
How is it created?
Click on “New -> Report” and select “Freeform SQL” from the list (you need a special role to see this option).
Type your code in the upper right hand side frame.
Now you have to map the items from the “Select” section of your script to virtual Attributes and Metrics. To do this, right click on the lower frame and select either “Add new Attribute form” or “Add new Metric”.
For a script like “SELECT country_id, country_name, SUM(sales)…” the mapping should be defined as:
These are virtual objects. You may actually have a “Country” Attribute in your project, but please don’t make the mistake of thinking these two are the same thing.
Click OK and you are back on familiar grounds.
Prompts in FF SQL
You can either create or insert them into a WHERE clause, by using the two dedicated buttons. The Prompts will show in bold pink.
Now, here is the interesting part. Let’s say you want to make some changes to the script, and you copy it into an external editor. You will notice that the prompts were converted into object IDs. Now, paste the text back into the FF SQL editor. They are bold pink again. Too bad the report won’t work anymore…
The prompts will have to be inserted again, the “button” way, if you want the report to run properly.
Words of caution.
Being what I call a “manually defined object”, the FF SQL is not subjected to automatic Schema updates. That is to say, you won’t be warned if you delete a table which is being used by such a report. So please bear in mind that maintenance for FF SQL can be harsh.
Note: Part 3 includes the work done so far in Part 1 and Part 2.
You probably found out by now that the Type and SubType properties of an IDSSObjectInfo (or similar class) return a numeric value. Call me picky, but if I were to build an application I would rather use layman’s terms such as Attribute or Drill Map instead of SubType 3072 or SubType 14336.
This third part of our tutorial offers a great way to convert these not-so-intuitive numerical values into their English meaning, by using a custom made function called DSS2Name.
You can download the VB6 files here.
MicroStrategy pricing is highly secretive and any one having license is barred from making any comment/information about the pricing they negotiated for license for 3 year from the date of acquiring the product license.
I was searching for product that will generate price-list and stumbled upon this page. Oracle has given DETAILED price list of the license with Named User, CPU with Feature List.
When MicroStrategy, Inc would do this. I know they have differential pricing for various Geographical Regions, but the price is a closely guarded secret. If you have anything to share on license/pricing, please share.