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.
Custom number formatting symbols If none of the built-in number formats meet your needs, you can create your own custom format in the Number tab of the Format Cells dialog box. Select Custom as the Category and create the format using the number format symbols listed in the table below. Each custom format can have up to four optional sections, one each for: Positive numbers Negative numbers Zeros Text Each section is optional. Separate the sections by semicolons, as shown in the example below: #,###;(#,###);0;"Error: Entry must be numeric" For more examples, see Custom number formatting examples . To jump to a section of the formatting symbol table, click one of the following: Numeric symbols Character/text symbols Date and time symbols Text color symbols Currency symbols Conditional symbols Numeric symbols For details on how numeric symbols apply to the Big Decimal data type, refer to the Project Design Guide . ...
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 ...
Differences between OLAP cubes and Super cubes OLAP Super Version Existed before MicroStrategy 10.0 New in MicroStrategy 10.0 Data Volume In 9.x, limited to 2 billion rows Each partition can have up to 2 billion rows ...
Reduce Intelligent Cube Size By Finding Intelligent Cube Objects Which Are Not In Use If the i-cubes can potentially be reduced in size an audit can be performed on the cube objects to see which cube objects are not being used by any of the view reports, documents, or dossiers. The below are examples for a few of the common metadata database platforms . NOTE: To perform this audit, queries are run against the MicroStrategy metadata database. Ensure a metadata backup is taken prior to performing the below actions. Steps: 1) Identify the object ID of the Intelligent cube to be audited by checking the objects Property window 2) Identify the object ID of the project this cube exists within by opening the Project Configuration Sample Cube ID = CFAF1E9B4D53990698C42E87C7AF2EB5 Sample Project ID = B7CA92F04B9FAE8D941C3E9B7E0CD754 3) Run the below SQL against the metadata database by replacing the Cube ID and Project ID within the respective ...
Scheduling a report or document to be sent to an FTP server You can have a report or document automatically delivered to a location on your FTP server on a specific schedule. To do so, you must subscribe to the report or document, as described in the steps below. You can customize your subscription by typing macros in the File Name , Sub-folder , or Zip File Name fields. These macros are automatically replaced with the appropriate text when the report or document is delivered. For example, you create a subscription to a document. If you type {&Project} in the File Name field, the name of the project in which the document is saved is displayed in the name of the document when it is delivered. • This procedure assumes that an administrator has already added your FTP server as a new device in Developer. Steps to do so are included in the System Administrator Help . To send a report or document to an FTP server on a schedule ...
Compound key attribute A compound key attribute is an attribute whose primary key is made up by the combination of two or more columns. The multiple columns are joined with other attributes, typically in a many-to-many relationship . To create a compound key, users must create multiple attribute forms, group them together and set the form group as the key for the attribute. Use the same steps as specified in the help menu: Open attribute editor (right-click on attribute and select 'Edit') Select the forms that will make up the compound key From the 'Edit' menu, choose 'Group' NOTE: Modifying the key form will trigger required updates when saving. This may make related application objects (reports, filters and metrics) unusable. Click on 'Yes' to continue, when prompted, in a dialog box, to confirm this action Save the changes. Choose 'Update Schema' from the Schema menu
Update the data on an Intelligent Cube without having to republish the entire cube in MicroStrategy MicroStrategy has introduced a feature known as, Incremental Refresh Options, which allow Intelligent Cubes to be updated based on one or more attributes, by setting up incremental refresh settings to update the Intelligent Cube with only new data. This can reduce the time and system resources necessary to update the Intelligent Cube periodically versus a full republish. For example, if a user has an Intelligent Cube that contains weekly sales data, the user may want this Intelligent Cube to be updated at the end of every week with the sales data for that week. By setting up incremental refresh settings, he can make it so that only data for one week is added to the Intelligent Cube, without affecting the existing data and without having to reload all existing data. Users can select t...
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...
Removing sections that do not have metric data This is an interesting feature which might not be explored by many of us and it comes us handy. A cross join between datasets can result in rows or Group Header/Footer sections that do not have metric data. For example, a document contains two datasets. Dataset 1 contains Year and Revenue, with data for three years (2007-2009). Dataset 2 contains Year and Profit, filtered to return data for only two years (2008 and 2009). If you place Year and Profit in the Details and execute the document, it displays three rows, although no profit data exists for 2007. This is a product of the cross join between the two datasets. You do not want to see the blank line for 2007 since it does not give you any data for profit. You can select the Trim sections for which no metric value data is available check box. This removes the row for 2007, since no metric data for Profit is available for 2007. The results are shown below: ...
Create a transaction services photo uploader 1. Create a new table "photo_upload" in Tutorial warehouse database (the default location: C:\Program Files\MicroStrategy\Tutorial Reporting\TUTORIAL_DATA_7200.mdb), as shown below: 2. The 'photo_upload' table has to be pre-populated with *exactly* 10 rows of data, the values for the 'ID' column should be 1-10 and the values for the 'uploaded' column should all be 0 3. In MicroStrategy Desktop, create a freeform report "R1" based on the new table "photo_upload" in Tutorial data created at step 1, as shown below: SELECT Location, Description, ID, uploaded, numbers FROM PHOTO_UPLOAD 4. Create another table for transaction insert SQL. Make sure to create an 'autonumber' type ID as primary key for this table, or auto_increment ID for different DBs. 5. Create...
nice..........!
ReplyDeletemicro strategy certification training
msbi course training
spring boot certification course training