Skip to main content

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:

https://community.microstrategy.com/s/article/KB307710-How-to-uninstall-MicroStrategy-Analytics-Enterprise?language=en_US

How to use this Tool

  1. 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)
  2. Restart the machine.
  3. Copy cleanup.exe to this machine.
  4. Right click and "Run as Administrator" to execute. This will do the following things:
    1. Back up the entire registry to "reg_backup_<timestamp>.reg" file (this file will get created in the same folder where the executable resides)
    2. 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
    3. Stop MicroStrategy related services
      • RemoteRegistry
      • Spooler
      • W3SVC
    4. 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)
    5. Rename the leftover folder C:\Program Files (x86)\MicroStrategy to C:\Program Files (x86)\MicroStrategy_<timestamp>
    6. Rename the leftover folder C:\Program Files (x86)\Common Files\MicroStrategy to C:\Program Files (x86)\Common Files\MicroStrategy_<timestamp>
    7. Prompt "Do you want to import applyCleanup.reg to registry now? (y/n):"
      1. Enter "y", the registry entries in applyCleanup.reg will be removed from system registry
      2. 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
  5. 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.
  6. 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.
2019;11.0;10.11;10.10;10.9;10.8;10.7;10.6;10.5;10.4;10.3;10.2;10.1;10.0;9.5.1;9.4.1;9.3.1
URL Name
KB307710-How-to-uninstall-MicroStrategy-Analytics-Enterprise
Labels:

Comments

Post a Comment

Popular posts from this blog

Best practices for using Distribution Services in Microstrategy

Best practices for using Distribution Services MicroStrategy recommends the following best practices when scheduling Distribution Services subscriptions, in addition to the best practices given above: • For best results, follow the steps listed in  High-level checklist to set up a report delivery system . • PDF, plain text, and CSV file formats generally offer the fastest delivery performance. Performance can vary, depending on items including your hardware, operating system, network connectivity, and so on. • The performance of the print delivery method depends on the speed of the printer. • When sending very large reports or documents: ▫ Enable the zipping feature for the subscription so that files are smaller. ▫ Use bulk export instead of the CSV file format. Details on bulk exporting are in the  Reports  chapter of the  Advanced Reporting Guide . ▫ Schedule subscription deliveries to occur when your Intelligence Server is experiencing low ...
1 comment
Read more

Derived metric based on attribute values

Derived metric based on attribute values Here is how could create and display data correctly on using below simple steps.  Create a report with Category, Subcategory and Revenue. Create New Metric in a report or VI.  Case((Category@ID = 1), Revenue, 0) Booksand Name it as Revenue for  where 2 is Category ID for "Books"  Report will display result as below.  Result for new metric is blank. Now to fix this create a new Derived metric on Category attribute first with formula as  Max(Category) {~ }  and calling Books Now Edit the "Revenue for Books metric and Replace Category@ID with this new Books metric formula would looks like this  Case((Books = 1), Revenue, 0).  Report result would now display as expected as shown below
2 comments
Read more

Prompt-in-prompt(Nested Prompts) in Microstrategy

Prompt-in-prompt(Nested Prompts) in  Microstrategy Nested prompts allows you to create one prompt based on the other and other bases on another, nested prompts allows us to prompt the highest level(Like year) to middle level(like Quarter, then to the low level(like Month). Here you can see how to  create a 3-level deep nested prompt that will prompt the user to select a year, then a quarter within that year, then a month within that quarter. Prompt-in-prompt is a feature in which the answer to one prompt is used to define another prompt. This feature is only implemented for element list prompts . The following procedure describes how to achieve this: Create the highest level filter. This is a filter which contains a prompt on an attribute element list. Create a filter on the attribute "Year." Click "prompt on attribute element list" and click "Next" through the rest of the screens to accept the default values. Do not set any additio...
3 comments
Read more

Microstrategy "Error type: Odbc error. Odbc operation attempted

 "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...
4 comments
Read more

MicroStrategy URL API Parameters

MicroStrategy URL Structure The following table summarizes the root URL structure used for every request to MicroStrategy Web. Environment Main Application URL Administration URL J2EE http://webserver/MicroStrategy/servlet/mstrWeb http://webserver/MicroStrategy/servlet/mstrWebAdmin .NET http://webserver/MicroStrategy/asp/Main.aspx http://webserver/MicroStrategy/asp/Admin.aspx Every request sent to MicroStrategy Web calls a central controller. Parameters are appended to  Main.aspx  or  mstrWeb  (in a .NET and J2EE environment, respectively) to indicate to the controller how the request should be internally forwarded and handled. The following examples show a URL for accessing a MicroStrategy folder when the user does not have an existing session. The URL contains not only the parameters needed to connect to MicroStrategy Web, but also the parameters needed to log on and create a session. J2EE environment: <a href="http:...
2 comments
Read more

Types of prompts in Microstrategy

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...
1 comment
Read more

Microstrategy Release Types and Scheduling

Microstrategy Release Types and Scheduling Organizations that use MicroStrategy have asked for a more frequent and predictable platform release schedule—and we listened! We want you to be able to adopt the latest innovations more regularly while having the ability to budget for your long-term upgrade roadmap. Recently announced by CTO Tim Lang in his newsletter, that’s why we’re adopting an annual cadence for future platform releases. This means that our upcoming platform release (v11.1) hits the streets in Q4 2018, followed by another platform release in Q4 2019. PLATFORM RELEASE Interval:  Annually every twelve (12) months in December Who:  Entire customer base What:  Focus on production level security, stability, and performance defect fixes for all customers. Expectation:  Customer has chosen platform path and wants product stability without new enhancements. Support:  Three (3) years, patches for approved P1 defects, an...
1 comment
Read more

Create an alert-based subscription in MicroStrategy Distribution Services

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...
3 comments
Read more

Microstrategy Document Autotext macros:

Autotext  code/macros in  Microstrategy Document/dashboard This is a list of the available auto text macros that the Report Services Document engine recognizes. The following auto text codes allow you to add  document variable information to your document. These auto text codes are automatically replaced by information about the document. Auto text codes for MSTR document/dashboard:  AUTOTEXT DESCRIPTION   {&PAGE}  Display the current page.  {&NPAGES}  Display the total number of pages.  {&DATETIME}  Display the current date and time.  {&USER}  Display the user name that is executing the Report Services Document.  {&DOCUMENT}  Display the document name.  {&DOCUMENTID}  Display the document ID.  {&DESCRIPTION}  Display the document description.  {&PROJECT}  Display the project name.  {&EXECUTIONTIME}  Dis...
2 comments
Read more

Fiscal Week, Fiscal Month, Fiscal Quarter and Fiscal Year calculations in Microstrategy

Fiscal Week, Fiscal Month, Fiscal Quarter and Fiscal Year calculations in Microstrategy FiscalWeek Returns the numeric position of a week within a fiscal year, for a given  input date. This function is useful in financial reporting when the start of the fiscal year is different than the start of the calendar year. Syntax FiscalWeek< firstWeekDay ,  firstMonth >( Date / Time ) Where: • Date / Time  is the input date or timestamp. • firstWeekDay  (default value is 1) is a parameter that determines which day of the week is considered as the first day of the week. You can type an integer value from 1 to 7, with 1 representing Sunday, 2 representing Monday, and so on until 7 representing Saturday. • firstMonth  (default value is 1) is a parameter that determines which month is considered as the start of the fiscal year. You can type an integer value from 1 to 12, with 1 representing January, 2 representing February, and so on until ...
1 comment
Read more