MicroStrategy Web

Compatibility and interoperability

MicroStrategy Web 10.x should be connected only to a MicroStrategy Intelligence Server of the same version or later for production purposes. For the complete MicroStrategy Platform Compatibility and Interoperability specification, see Compatibility and Interoperability.

Installing MicroStrategy Web

For steps to install MicroStrategy Web, see the Installation and Configuration Guide.

Review your environment to ensure compliance with supported operating systems, application servers, web servers, Java Development Kits, Java servlet engines, and hardware and software requirements. For steps to deploy MicroStrategy Web on specific operating systems or application servers, see the Deploying MicroStrategy Web chapter of the Installation and Configuration Guide.

  • Windows Installer 3.0 or later is required to install MicroStrategy products on a Windows platform.

  • You can download the software from the MicroStrategy download site.

  • The MicroStrategy Knowledge Base includes technical notes that document the history of changes to MicroStrategy Web files between various MicroStrategy releases. To find and review this information, search the knowledge base using a keyword.

If you encounter problems during the installation procedure, see the Troubleshooting appendix in the Installation and Configuration Guide. If you require additional assistance, contact Technical Support.

Directory structure

JSP interface: The following table lists folders and files of interest that are included in the default directory structure after deploying your MicroStrategy Web WAR file:



\assets Supporting files
\html Supporting files
\images All image files
\import Sample files for Data Import analysis
\javascript Interface JavaScript files
\jsp Interface JSP code files
\plugins Plug-in files for customizations
\resBundles Flash descriptor files
\style Interface style files
\swf Supporting files for widgets
\VisFramework Supporting files for visualizations

Configuration information for MicroStrategy Web

ASP.NET interface: The following table lists folders and files of interest that are included in the default directory structure after an installation of MicroStrategy Web.



\asp .Net files
\bin binary files
\images All image files
\javascript Interface JavaScript files
\plugins Plug-in files for customizations
\resBundles Flash descriptor files
\style Interface style files
\swf Supporting files for widgets
\VisFramework Supporting files for visualizations
\WEB-INF Configuration information for MicroStrategy Web

Upgrading MicroStrategy Web

To benefit from the latest functionality available in this version of MicroStrategy Web, an administrator must upgrade the system:

  • MicroStrategy 9.3.x, 9.4.x, and 9.5.x products can be upgraded directly to MicroStrategy 10.

Before upgrading, see the Upgrade Guide for important information about preparing for the upgrade, the order in which to upgrade products, and tasks to perform after upgrading.

Uninstalling MicroStrategy Web

For details about uninstalling MicroStrategy Web, see the "Adding or Removing MicroStrategy Components" chapter of the Installation and Configuration Guide.

Resolved Issues

For a list of all the known and resolved issues in this MicroStrategy release, consult the Knowledge Base technical note TN295609.


Troubleshooting known issues

Issues that have a prefix of S (S#####) are customer cases that can be tracked through MicroStrategy Technical Support. Those that are prefixed with T (T#####) are MicroStrategy internal issues. Internal issue numbers do not correlate to customer case numbers.


  • Office-enabled export only works for Report Services documents opened in a stand-alone Excel instance rather than within the context of Internet Explorer (T211409). To do so, open Internet Explorer and select Tools, and then Folder options. Click on the File Types tab, select XLS, and click the Advanced button. Under the Edit File Type dialog, select the Open action and clear the check box to 'Browse in same window.' Click OK to save your changes.
  • Microsoft Internet Explorer users might encounter small fonts on the report or Design mode page if the browser cache settings are set to 'Automatic'. To resolve this problem, set the option in Tools > Internet Options > Temporary Internet File Settings to 'Every visit to the page'.
  • Hitting the browser Stop button or <escape> sometimes does not halt a user action if DHTML usage is enabled. The browser does not handle the request and continues with the last requested action. To resolve this issue, use the Cancel button provided through the MicroStrategy Web feedback dialog (T140679).


  • Japanese graphs using any custom styles display incorrect characters such as squares. The workaround is to apply non-custom styles or manually apply Japanese fonts (T220941).
  • Report Services documents exported to Excel in traditional Chinese include a wrong file name. The workaround is to manually rename the file (T209991).
  • Japanese currency is displayed as "\" when exporting grids to an English version of Excel. The workaround is to modify the value of the parameter 'excelDirectExport' to true in the web.xml file (T158473).
  • Japanese/Korean - problems exporting attribute elements formatted with w-byte-specific font (starting with @) to PDF. A font name with a "@" before it means 90 degree rotation for each character (T298214).
  • The current version of the PDF exporting feature doesn't support the orientation for each character, and uses the font name with "@" before it to search for a font file. Such a font file doesn't exist, so a default font is used to replace the "@..." font. This causes the Japanese string to be displayed incorrectly, or to not be displayed at all. A small modification has been made to let the PDF Exporter ignore "@" character before any font name. Thus, the Japanese string will be displayed with the correct font, but without the 90 degree rotation. Another issue has been logged for PDF to support character orientation.
  • The calendar control and date format for reports in grid view use the English US date format (mm/dd/yyyy) instead of the French date formatting (dd/mm/yyyy) if Intelligence Server runs on an English machine. This makes date prompt reports fail when they are executed. When a French Intelligence Server (on Windows) is used, date formatting is correct.


  • Symptom: During the installation of a MicroStrategy product, this error is displayed: "An error occurred during the data transfer process-106" and the install does not finish successfully.

    • Resolution: The official description for this error code is "Unable to decompress a file". The source of this error is a weak network during installation. A file was not completely copied to the target machine because of network congestion, causing this error in InstallShield. Copy the install files locally or wait until the network response time improves.
  • Symptom: When going to the MicroStrategy Web page, an error is displayed with the following code: (<%@ Page Language="vb" AutoEventWireup="false" Codebehind="Main.aspx.vb" Inherits="ASPxMSTRWeb.Main" %>)

    • Cause: The .aspx application mapping in IIS is improperly configured.
    • Resolution: Go under the IIS manager, right-click the MicroStrategy virtual directory, click Properties, and then select Configuration. You should see a list of extensions and their DLL execution paths. Verify that both .aspx and .asp are listed here (if not, add them), and that they map to the aspnet_isapi.dll under C:\WINNT\Microsoft.NET\Framework\v1.1.4322.
  • Symptom: When going to the MicroStrategy Web page, an error appears is displayed in line 86 (<system.diagnostics>) of the MicroStrategy web.config file.

    • Cause: There could have been some problems while setting certain security permissions on files during the installation.
    • Resolution: Make sure that the ASPNET user account has full permissions on the log folder under C:\Program Files\MicroStrategy\Web ASPx\WEB-INF. Also make sure that the ASPNET user account has read and execute privileges on all the Web*.jar files under C:\Program Files\Common Files\MicroStrategy\. Restart IIS, and you should now be able to access the MicroStrategy Web page.

Application server-specific issues

Supporting IIS as a web server for MicroStrategy Web

If you plan to use IIS as the web server for MicroStrategy Web, you must ensure that some IIS options are enabled before installing MicroStrategy. The procedure below describes how to enable the options that are required to support IIS as a web server for MicroStrategy Web.

The third-party products discussed below are manufactured by vendors independent of MicroStrategy, and the steps to configure these products are subject to change. See the appropriate Microsoft documentation for steps to configure IIS.

  1. On a Windows machine, open the Control Panel.

  2. Double-click Programs and Features.

  3. Click the Turn Windows features on or off task. The Windows Features dialog box opens.

  4. Expand Internet Information Services, and select the following options:

    1. Expand Web Management Tools and select:

      • IIS Management Console
      • IIS Management Scripts and Tools
      • IIS Management Service
    2. Expand World Wide Web Services, then expand Application Development Features, and select:

      • .NET Extensibility
      • ASP.NET
      • ISAPI Extensions
      • ISAPI Filters
    3. Within World Wide Web Services, expand Common Http Features, and select:

      • Default Document
      • Static Content
    4. Expand Security, and select:

      • Request Filtering
      • Windows Authentication
  5. Click OK to save your changes.


  • Symptom: Graphs are not displayed when using Tomcat and IIS re-direction, but they display correctly when using Tomcat in isolation of IIS (T155159).

    • Cause: Web uses the servlet by default to display graph and other binary data. Using a JSP page for the same purpose for binary data results in similar problems when running Sun ONE (iPlanet) Web application servers.
    • Resolution: When using Tomcat with IIS re-direction, you will need to change the pageconfig.xml file to indicate that MicroStrategy needs to use the JSP file instead of the servlet for graph display. The change needs to be done to all pages which show the graph. Currently it is the name="reportGraph" and name="print". You have to remove the attributes for that page which read as binary-display="xyz". Removing this attribute altogether will ensure that MicroStrategy uses the JSP for graphs.
  • Symptom: Authentication is not working properly when I connect to the mstrWebAdmin page. I cannot connect to the Administrator page when using Tomcat and IIS redirection, but it works when using Tomcat directly.

    • Cause: This happens because the Jakarta virtual directory created for the IIS/Tomcat integration is set to use the NT authentication by default.
    • Resolution: Unselect the Windows NT security for that virtual directory.


  • Symptom: Graphs can not be exported to Excel if cookies are disabled.

    • Cause: If the MicroStrategy Administrator specifies to disable cookies through the Web Administrator page, and if the client browser does not accept cookies, then graphs cannot be exported to Excel without making some changes to the Session Management.
    • Resolution: For WebSphere environment to work correctly, the setting for "Enable URL Rewriting" should be enabled on the WebSphere Admin Console. The setting is found under Default Server -> Services -> Session Manager Service -> Enable URL Rewriting (should be selected).


  • Symptom: Receive the following error: com.microstrategy.web.app.WebAppConfigurationRun-timeException System preferences File not found at: null

    • Cause: MicroStrategy Web was deployed as a WAR file on WebLogic. In that mode, that application does not know where to physically copy certain initialization files on the disk. This files are critical for the application to function correctly.
    • Resolution: You will need to update the web.xml file contained under the .war file to include absolute paths for multiple initialization parameters. Follow the steps in the Installation and Configuration Guide for more detailed instructions.
  • Symptom: When exporting graphs to Excel or HTML using WebLogic as application server, graphs are displayed as a broken image.

    • Cause: This is happening because of the WebServer configuration in the web.xml file. On the source of the image, the application path was not included.
    • Resolution: This can be solved by adding the application path in the web.xml file. You can do this by following these steps:

      1. Open the web.xml file from the \WEB-INF folder.
      2. Locate the ConfigServletPath section in the code and add the following value in the param-value: <param-value>http://IP address/servlet-path</param-value> The servlet-path is the path of your application.
      3. Save the file.

Oracle Application Server

  • Symptom: General stability problems or exceptions when running Oracle Application Server.

    • Cause: The XML parser shipped with Oracle Application Server causes this issue.
    • Resolution: Add <web-app-class-loader search-local-classes-first="true" /> into orion-web.xml for the Web application. This is a per application setting, which will override the parent class loader, to search the class first in application path. While this is the optimal way to fix the problem as it only affects the Web application, but not any other applications which might be running under the Application Server. This method causes the following error: oracle.sysman.emSDK.util.jdk.EMException: Timeout has been reached to be generated during application startup. This issue has been logged with Oracle Tech support. The TAR number is TAR 3079126.999. Thus the only recourse the user is left with is to replace the versions of xerces.jar and xalan.jar under the jdk\jre\lib\ext folder on the Oracle Application Server with those shipped with Web. This makes them the java platform's extension and loaded before Oracle loads its own classes. However, this approach will affect all applications on this server.

General troubleshooting

  • Symptom: The map markers of a Map widget included in a document are displayed as all the same color, rather than the colors that should be displayed due to threshold formatting.

    • Cause: In MicroStrategy 9.3, the thresholds for map markers apply colors based on the fill color of the threshold. In previous releases, these thresholds applied colors based on the font color of the threshold.
    • Resolution: After upgrading to MicroStrategy 9.3.x, you must modify map marker thresholds to use the fill color to define the color of map markers.
  • Symptom: The system is slow the first time a user hits a page.

    • Cause: The very first time a page is accessed by a user after deployment, the application server will compile the JSP code involved in that page execution. This is a one-time cost only.
    • Troubleshooting: It is possible to pre-compile all JSPs during the application deployment. For more information, see the MicroStrategy Installation and Configuration Guide or your application server documentation.
  • Symptom: The system is slow overall.

    • Cause: Ineffective system configuration.
    • Troubleshooting: While it is not possible to provide a check-list of everything that could be wrong, MicroStrategy recommends that you first make sure that you have taken a minimum of steps to optimize the application server/web server system. This includes: increasing the java heap, disabling (or greatly relaxing) the servlet/JSP auto-reload and configuring the web server to handle all static files request (images, css and javascript files). For more information, see the Installation and Configuration Guide or your application server documentation
  • Symptom: Timeout issues occur when large documents are edited.

    • Resolution: To edit a document with a very large number of objects, you may need to set the MicroStrategy API timeout, the ASP.NET timeout and the IE timeout appropriately:

      1. The ASP.NET timeout is 90 seconds by default. It can be found in the machine.config file under C:\Winnt\Microsoft.Net\Framework\v1.1.4322\config (look for the string '<httpRuntime executionTimeout="90"'). After modifying it, restart IIS.
      2. The MicroStrategy API timeout is 180 seconds by default. To modify it, you will need to go under the MicroStrategy Web Administrator page, click on Default Properties under Intelligence Servers and look for the Request Timeout parameter.
      3. Finally, the Internet Explorer browser has a five minute timeout. To change it, you must add the following registry value: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]”ReceiveTimeout”=dword:00124f80. This registry sets the timeout to 20 minutes since 00124f80 is the hexadecimal equivalent of 1,200,000.
  • Symptom: Problems occur when large documents are manipulated; manipulations are lost or a login page appears.

    • Cause: The maximum request header length used by ASP.NET by default (4096Kb) may not be enough when manipulating documents with a very large number of objects. This can result in an error page because the state of the document was incomplete, or even a login page because the session state was lost.
    • Resolution: To increase the maximum request header length setting for the ASP.NET infrastructure, you will need to edit machine.config file under C:\Winnt\Microsoft.Net\Framework\v1.1.4322\config (look for the string '<httpRuntime maxRequestLength="4096"'). After modifying it, you will need to restart IIS.
  • Symptom: Web re-prompts the user for a login/password after 20 minutes of idle time even if the Web user session idle time was set higher.

    • Cause: MicroStrategy Web 7.5 and above saves the Intelligence Server session information in a session object on the .NET side. This infrastructure provides its own session management and, in particular, defines a timeout after which the session object is released if it has not been accessed after a certain time (to free up some memory).
    • Resolution:

      1. Modify the timeout for the session object inside the .Net infrastructure and make it the same as the session idle timeout for Web. For this, you can edit the machine.config file under C:\WINNT\Microsoft.Net\Framework\v1.1.4322\CONFIG, and find the timeout attribute for the sessionState. It is set to timeout="20" by default which means 20 min. Modify it accordingly, and restart the ASP.NET process.
      2. Alternatively, it is also possible to save the session information in temporary cookies, but this is less recommended. In order to do that, go under the security tab in the MicroStrategy Web Administrator page, and select the checkbox 'store MircoStrategy Intelligence Server session...' in the cookies security level.
  • Symptom: Export to PDF returns a blank page.

    • Cause: This can happen if Internet Explorer is unable to save the PDF on the client machine for display
    • Resolution: From the Tools menu in Internet Explorer, select Internet Options and click on the Delete Files button for the Temporary Internet Files. Select the check box to delete all offline content and proceed. After this is done, try to export to PDF again.
  • Symptom: Problems occur when accessing the MicroStrategy Web Administrator Page.

    • Background: If you are not logged in as an Administrator on the Web server machine, you get a login dialog box. If you do not provide an Administrator login, you receive Error 401.1 Unauthorized: Logon Failed.
    • Resolution: To solve this problem, contact your administrator who can provide you with Administrator privileges and the necessary login information.
  • Symptom: Double-byte fonts aren't available in the Formatting dialog box.

    • Cause: Incorrect XML files are being used.
    • Resolution: Check under the WEB-INF/xml/config directory, and look for fontNamesPicker_ja.xml (Japanese), fontNamesPicker_ko.xml (Korean), fontNamesPicker_zh.xml (Simplified Chinese), and fontNamesPicker_zh_tw.xml (Traditional Chinese). The administrator needs to backup the original fontNamesPicker.xml and remove the file suffix so the file is named fontNamesPicker.xml instead of the out of the box file.
  • Symptom: Problems occur when document objects are run in double-byte languages.

    • Resolution: When creating document objects, you should be aware that there are XSLs for single-byte languages and special XSL files used only for double-byte languages. The single-byte XSLs are stored in the XSL directory under Developer. The double-byte XSLs are stored in the XSL\db directory under Developer.
  • Symptom: When you run a document, the following error occurs: "Unable to open the Document's HTML template file. DSSDocumentSenderTask::Run(): Error generating the Document HTML output, job 96, HR=-2147468892."

    • Resolution: If you are sure that the HTML file is correct and in the right place, MicroStrategy Intelligence Server probably cannot access the HTML file. If MicroStrategy Intelligence Server is running as an application, ensure that the network/local login on that server machine has access to the directory containing the HTML files. If MicroStrategy Intelligence Server is running as a service, ensure that the service is running under a network/local account that has access to the directory with the HTML files.
  • Symptom: Users cannot see any folders or reports.

    • Resolution: Check user permissions and privileges to ensure that the appropriate security access to the folders and reports has been set up.
  • Symptom: 'Document XSL cannot be found' error when running a document.

    • Cause: One or more of the document XSL files used to generate the report are no longer located in the same place.
    • Resolution: Make sure that the network/local login on that the server machine has access to the directory where the HTML / XSL files are placed. If Intelligence Server is running as a service, make sure that the service is running under a network/local account, that has access to the directory where the HTML / XSL files are placed.