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.
"Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [HYT00:0: on SQLHANDLE] [MicroStrategy][ODBC Oracle Wire Protocol driver]Timeout expired" is shown when executing reports from Web When users are trying to execute some reports in MicroStrategy web in particular, they may receive the Error “SQL Generation Complete Index out of range” and “Timeout expired” error as shown below: Possible Causes: One possible cause is that the MicroStrategy Intelligence Server using a cached database connection that was already dropped by the RDBMS. To resolve this: Admin should delete the database connection caches and create a new DSNs in case they are sharing DSNs to connect to different databases. In addition, change the settings for the ‘Connection lifetime’ and the ‘Connection idle time out’. Follow the steps below to perform the mentioned changes and verify the report after each step and some of the settings require i-server r...
"Table structure cannot read or update" in the warehouse catalog error while updating a table structure while using Warehouse Catalog in MicroStrategy Developer This issue could be due to the incorrect prefix. To fix the issue. 1. Open the Warehouse Catalog. 2. Select the table and assign the correct Prefix update the structure. 3. Save and close the warehouse catalog.
Order of tables appear in the SQL generated by the MicroStrategy SQL Generation Engine By default, the MicroStrategy SQL Generation Engine orders the tables in the following way( FMRL ): Fact Tables Metric Qualification (MQ) Tables Relationship Tables Lookup Tables
Logical Views to specify an outer join between two attribute lookup tables when only attributes are on a report Apart from using the VLDB properties to create the left outer join, article describes how to use the Logical View to specify an outer join between two attribute lookup tables when only attributes are on a report. This method exists as attribute only outer joins will not be generated on their own by the MicroStrategy SQL engine. This is because they are only necessary with r agged/unbalanced hierarchies which are not supported as null attribute IDs are not supported (parent elements with no child elements or child elements with no parents). Brief instructions are provided using the example below. Consider, two attributes: Parent01 and Child01 have a parent-child relationship. Their Lookup tables are defined, as follows Parent01 Child01 Note that although there are 4 ID values for the attribute Parent01, there is no defined relationship ...
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 .
Optimization standards to help developers work with the System Administrator to optimize network data transfer speeds: Place all server components in the same segment to minimize latency between the Intelligence Server, Web server, data warehouse server, and metadata server Expand bandwidth and minimize latency between servers and clients to ensure that bottlenecks do not occur when data is requested over your network Use HTTP compression between the Web servers and Web clients to achieve maximum throughput between these components Configure a Web proxy server to handle caching and reduce the load on the Web server
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...
HyperIntelligence Training Videos Design and build hyper cards Optimizing Datasets for HyperIntelligence Using the HyperIntelligence for Office Outlook Add-In Building HyperIntelligence Cards Using HyperIntelligence for Mobile on Android Deploying HyperIntelligence for Outlook Insights On-The-Go: HyperIntelligence for Mobile Building HyperIntelligence Profile Cards Designing Custom HyperIntelligence Cards Using the Calendar with HyperIntelligence for Mobile
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...
Create an alert-based subscription in MicroStrategy Distribution Services on Web Subscription to a report or Report Services document which will be executed when a certain conditional threshold is met based on another executing report. For example, a scheduled report executes which shows the Revenue by day for the past week. If the Revenue on any one day falls below a certain value, a subscription to another report or Report Services document can be triggered and delivered to a recipient. An alert based subscription can only be created directly on a report; however, another report or Report Services document can be delivered when the alert based subscription is triggered. Note: you need a grid report to create an alert and you cannot create if you want to create on a document with text boxes. The following example will walk through the basic steps on how to setup a subscription based on an alert like this: Follow the brief steps bel...
nice..........!
ReplyDeletemicro strategy certification training
msbi course training
spring boot certification course training