Microstrategy Business Intelligence knowledge sharing platform
Search This Blog
Clean uninstall MicroStrategy Analytics Enterprise using the Uninstallation Cleanup Utility
How to clean uninstall MicroStrategy Analytics Enterprise using the Uninstallation Cleanup Utility
CONSIDERATIONS/GUIDELINES:
This Uninstallation Cleanup Utility is designed to remove the obsolete or leftover services, files and registries after uninstalling MicroStrategy products.
The goal of this cleanup utility is to remove the leftover files and registries after uninstallation to make the machine "cleaner" for a second time installation (it can solve some known downgrade installation issues).
The basic assumption for removing files is that the user installed MicroStrategy in a path that contains the string "MicroStrategy". If not, the files and certain registry keys will not be removed.
Using the cleanup utility incorrectly can cause system-wide problems that may require re-installation of the Operating System. This utility should always be tested in a test environment before being run in a production environment.
Link to download cleanup utility under files - Cleanup.zip:
Uninstall all the MicroStrategy and related products from Control Panel:
Any MSTR Hotfixes applied
MSTR Secure Enterprise
MSTR Health Center (if it's not uninstalled)
MSTR Office (if installed)
DHTML Editing Component (if installed)
Restart the machine.
Copy cleanup.exe to this machine.
Right click and "Run as Administrator" to execute. This will do the following things:
Back up the entire registry to "reg_backup_<timestamp>.reg" file (this file will get created in the same folder where the executable resides)
Stop and remove MicroStrategy services (if they exist)
MicroStrategy Distribution Manager
MAEMETLS
MicroStrategy Execution Engine
MicroStrategy Intelligence Server
MicroStrategy Logging Client
MicroStrategy Logging Consumer
MicroStrategy Logging Server
MAPing
EMService
MicroStrategy SMTP Service
MicroStrategy NC PDF Formatter
SubscriptionAdministrator
SubscriptionServer
SubscriptionEngine
SubscriptionLogger
SubscriptionRMIRegistry
MicroStrategy System Monitor
TransactorAdministrator
TransactorCommunicationServer
TransactorTransactionEngine
TransactorLogger
TransactorLookup
MHealthAgent
HealthAgent
Tomcat8
MySQL
usherIDM
usherGW
Apache2.4
memcached
Stop MicroStrategy related services
RemoteRegistry
Spooler
W3SVC
Generate a list of registries to be cleaned from the system "applyCleanup.reg" (this file will get created in the same folder where the cleanup executable resides)
Rename the leftover folder C:\Program Files (x86)\MicroStrategy to C:\Program Files (x86)\MicroStrategy_<timestamp>
Rename the leftover folder C:\Program Files (x86)\Common Files\MicroStrategy to C:\Program Files (x86)\Common Files\MicroStrategy_<timestamp>
Prompt "Do you want to import applyCleanup.reg to registry now? (y/n):"
Enter "y", the registry entries in applyCleanup.reg will be removed from system registry
Enter "n", the registry entries won't be removed. Users can always review applyCleanup.reg later and manually apply it by double clicking on it
If the user wants to delete the entire MicroStrategy folders instead of renaming it, the user can run "cleanup.exe -f" in the Windows Command prompt.
After the executable is run, users should restart the machine
Usage in Windows Command Prompt
cleanup.exe [-h] [-f]
optional arguments:
-h, --help
show this help message and exit
-f
remove directories instead of renaming
Disclaimers and Limitation of Liabilities
Disclaimer:The utility application is provided "as is" and without warranty of any kind. MicroStrategy Expressly disclaims all warranties, express, implied or statutory, including, without limitation, the implied warranties of merchantability, fitness for a particular purpose, satisfactory quality and non-infringement.
Limitation of Liability: MicroStrategy shall have no liability to licensee for any damages of any kind, including, but not limited to, liability for direct, indirect, special, incidental or consequential, damages (which shall include, but not be limited to, loss of data or information, loss of revenue or anticipated profits or lost business).
MSTR KB Ref: KB000021893
Version
MicroStrategy version family that this article applies to.
How are the fact tables determined using the logical table size for SQL generation in MicroStrategy The logical table size is an integer number that represents the granularity or level of aggregation of a particular table. It is called 'logical' because it is not related to the physical size of the tables (number of rows). It is calculated according to the attribute IDs that are present in the table and their level in the system hierarchy. Even though, the number does not reveal the actual number of rows in the table, it is an accurate way of measuring a table size without having to access its contents. IMPORTANT: The system hierarchy is defined by the parent-child relationships between attributes of the same family (formerly known as a dimension), not by user-defined hierarchies (i.e., drilling hierarchies). MicroStrategy Engine utilizes an algorithm based on attribute keys to calculate the Logical Table Size (LTS): Given the following tables: ...
Types of prompts in Microstrategy The different types of prompts allow you to create a prompt for nearly every part of a report. Prompts can be used in many objects including reports, filters, metrics, and custom groups, but all prompts require user interaction when the report is executed. The correct prompt type to create depends on what report objects you want users to be able to base a filter on to filter data, as described in the list below. Filter definition prompts allow users to determine how the report's data is filtered, based on one of the following objects: Attributes in a hierarchy : Users can select prompt answers from one or more attribute elements from one or more attributes. The attribute elements that they select are used to filter data displayed on the report. This prompt lets you give users the largest number of attribute elements to choose from when they answer the prompt to define their filtering criteria. For example, on a repor...
Error "Conversion failed Error "Conversion failed when converting the varchar value 'xxxx' to data type int" happens when displaying Picture type attribute form using ApplySimple in expression against SQL Server 2012 in MicroStrategy The attribute form is in Picture type and defined with the following ApplySimple function with Int type column [ID_BARANG] as the input parameter against SQL Server 2012. Solutions is to use Concat("Images/demo/s", [BARANG_ID_INT], ".png") ApplySimple("'images/demo/'�&'.png'", [ID_BARANG]) However, when running reports with attribute to show the picture form in Web, error message happens in both Web and Developer. Conversion failed when converting the varchar value 'images/demo/s' to data type int. STEPS TO REPRODUCE: SQL Server 2012 database should be used as the warehouse. Create an attribute form as type Picture and us custom expressi...
To display a group horizontally or Add sections horizontally: 1. In MicroStrategy Web, open the document in Design or Editable Mode . 2. From the Tools menu, select Grouping . The Grouping panel is displayed. 3. In the Grouping panel, right-click the grouping field to display horizontally, and select Grouping Properties . The Grouping Properties dialog box opens. 4 . Select the Render object name horizontally check box. 5 . Click OK to apply the changes and return to the document. Step1: Step 2: More Info: https://www2.microstrategy.com/producthelp/10.7/DocCreationGuide/WebHelp/Lang_1033/Content/DocumentCreationGuide/Displaying_a_group_horizontally.htm#grouping_and_sorting_4135344594_1105953
The 'Alert' option does not appear when attempting to create an alert-based subscription in MicroStrategy Distribution Services In MicroStrategy Distribution Service 9.x and 10.x, and 11.x versions it is possible to create an alert-based subscription. When right-clicking the metric header of a report in MicroStrategy Web 9.0.x, the 'Alerts' option does not appear: Cause : This issue occurs because the user attempting to create the alert does not have all of the necessary privileges on alerts. Fix : In order to create an alert-based subscription, the following privileges are required: In order ti get permissions to create alerts the user should be given the following privileges by the admin: New Version of Microstrategy 11.x: Server- Distribution: Older Versions of Microstrategy 9.x, 10.x etc..: Web Reporter > Web user Web Analyst > Web create alert ...
Create Email Subscription in Microstrategy Creates an email subscription. Do not include any leading or trailing spaces in the ANSWER parameters. This causes a SQL error and prevents the command from executing. Ex: CREATE EMAILSUBSCRIPTION "New Multi Users" FOR OWNER "administrator" SCHEDULE "Books Closed" CONTACTGROUP "TEST" CONTENT "Electronics Revenue by Region" IN FOLDER "\Public Objects\REPORTS\SUBJECT Areas\Sales and Profitability Analysis" IN PROJECT "MicroStrategy Tutorial" DELIVERYFORMAT HTML EXPIRATIONDATE NEVER EXPRIED FILENAME "file_name" SUBJECT "Test REPORT" MESSAGE "Please Test"; CREATE EMAILSUBSCRIPTION [ subscription_name ] [FOR OWNER login_name ] SCHEDULE schedule_name (ADDRESS address_name | USER user_name | CONTACT contact_name [ADDRESS contact_ address_name ] | CONTACTGROUP contact_group_name ) CONTENT ( report_or_document_name IN FOLDER loc...
Microstrategy Internationalization Design Technics MicroStrategy supports data internationalization through two different techniques. You can either provide translated data through the use of extra tables and columns, or you can provide separate databases to store your translated data. These techniques are described below: You can support data internationalization in your database by using separate tables and columns to store your translated data. You can use various combinations of tables and columns to support and identify the translated data in your database. To support displaying the name of each month in multiple languages, you can include the translated names in a separate column, one for each required language, within the same table. Each column can use a suffix to identify that the column contains translated data for a certain language. The same LU_MONTH_OF_YEAR table with translated data for the Spanish and German langua...
Non Aggregate metrics Beginning lookup, Ending lookup, Beginning fact ., Ending fact A nonaggregatable metric, such as an inventory metric, is one that should not be aggregated across an attribute. For example, if you have monthly inventory numbers in your data warehouse and want to calculate the yearly inventory, adding the monthly numbers together does not provide a useful business measure. Instead, you may want to use the end-on-hand and beginning-on-hand inventory numbers to see how the total inventory changed during the year. The following options are available: • To use the first value in the lookup table, select Beginning lookup . • To use the last value in the lookup table, select Ending lookup . • To use the first value in the fact table, select Beginning fact . • To use the last value in the fact table, select Ending fact .
Customers Who Live in the Same City as Call Centers Your new utility company has call centers located throughout the country, and your recent surveys indicate that customers who live in the same city as a call center are particularly satisfied with service due to extremely rapid repairs during power outages. To begin your new advertising campaign, you want to generate a list of Call Centers that coincide with Customer Cities. The following steps create an attribute-to-attribute qualification filter that generates the list of desired cities. To Create an Attribute-To-Attribute Qualification that Compares the Call Center and Customer City Attributes In MicroStrategy Web, log in to a project. Open any folder page (for example, click Shared Folders on the home page). Click the Create Filter icon . From the Object browser on the left, select the Customer City attribute from the Customers hierarchy and drag it to the filter pane on the right. Change Qualify...
Super Cubes in MicroStrategy 2019 Beginning in MicroStrategy 11.0 and 2019, users will notice objects referred to as " Super Cubes ". Super Cubes are simply a renaming of what was previously referred to as MTDI (Multi Table Data Import) Cubes. Note that only the naming convention has changed, as the functionality remains the same . This name change is visible in MicroStrategy Workstation and MicroStrategy Web. In MicroStrategy Workstation, right click on any cube created via Data Import and select Properties . The object Type is listed as Super Cube: This can also be seen when editing or authoring a dossier. In your Datasets panel, hover over the name of your dataset. The tooltip will show the dataset type listed as a Super Cube.
nice..........!
ReplyDeletemicro strategy certification training
msbi course training
spring boot certification course training