MicroStrategy ONE

Troubleshooting Reference

This reference provides troubleshooting tips for how to handle an unexpected issue when the standard error handling and debugging procedures do not completely resolve the issue. In addition to the miscellaneous tips provided here, see the following sections for background on and other techniques for dealing with error handling and debugging:

Some common problems encountered during customization and deployment are listed below along with possible resolution steps.

Browser displays a blank Web page

  • If the browser displays a blank Web page, check the log files for the Application Server as well as for the MicroStrategy Web application. Some Application Servers also provide a GUI where errors are displayed.

Class cannot be found (Java.lang.NoClassDefFound) error

This error can be displayed when the application cannot find the class definition for a custom class. Make sure you adhere to these guidelines while creating classes:

  • File names, package names and code are case-sensitive in a Java environment. 

  • Never include blank spaces as part of a class’s name or any parent folder beneath the classes folder. Be sure to put the custom class in the proper directory structure to make it conform to its package declaration in the class, itself. 

  • When you call a custom class in a configuration file such as Page Configuration file or a Style Catalog configuration file, use the proper package name. Package names are case-sensitive.

Customization changes not applied

  • If the changes in configuration files do not take effect, make sure you are using the correct values for the parameters. Also refer to the section on Applying customization changes to the application.

Errors displayed 

  • Try including Log.logger.log(Level.ERROR); statements in your code to isolate the portion that generates errors. 

  • Malformed configuration files (such as the Page Configuration file, the Style Catalog Configuration file and so on) can yield a blank page or errors if nodes are not closed appropriately, or if they are inserted in the wrong place.

    For example, if <web-beans>...</web-beans> is followed by another <web-beans>...</web-beans>, the second <web-beans> node is ignored. 

  •  Malformed custom tags can also lead to blank pages or errors. 

  • If you encounter Servlet.init() errors, they will most probably be related to web.xml or a problem with referencing one of the files included in web.xml.

Slow response time

  • If you notice extremely slow response despite having a fast internet connection and a stable MicroStrategy Intelligence Server, check XML files for Intelligence Server. 

  • If one or more Web pages are unusually slow to load, especially when the network connection and speed appears to be in otherwise good or expected shape, try deleting AdminServers.xml.  It might be containing an outdated reference to an Intelligence Server that is not running or available, and this can slow down performance for Web significantly.)