1. API reference
  2. Welcome
    1. Component overview
    2. Quick start
    3. System requirements
    4. Troubleshooting
    5. Managing license keys
  3. Connecting to Data Source
    1. JSON
      1. Connecting to JSON
      2. Connecting to JSON using the Data Compressor
      3. Data types in JSON
    2. CSV
      1. Connecting to CSV
      2. Connecting to CSV using the Data Compressor
      3. Data types in CSV
    3. Database
      1. Connecting to SQL databases
      2. Connecting to other databases
      3. Connecting to a database with Node.js
      4. Connecting to a database with .NET
      5. Connecting to a database with .NET Core
      6. Connecting to a database with Java
      7. Connecting to a database with PHP
    4. Microsoft Analysis Services
      1. Connecting to Microsoft Analysis Services
      2. Getting started with the Accelerator
      3. Installing the Accelerator as a Windows service
      4. Referring the Accelerator as a DLL
      5. Configuring the authentication process
      6. Configuring a secure HTTPS connection
      7. Troubleshooting
    5. Pentaho Mondrian
      1. Connecting to Pentaho Mondrian
      2. Getting started with the Accelerator
      3. Configuring Mondrian roles
      4. Configuring username/password protection
      5. Configuring a secure HTTPS connection
      6. Troubleshooting
    6. Elasticsearch
      1. Connecting to Elasticsearch
      2. Configuring the mapping
  4. Security
    1. Security in Flexmonster
    2. Security aspects when connecting to an OLAP cube
      1. The data transfer process
      2. Data security
      3. Data access management
    3. Security aspects when connecting to a database
      1. The data transfer process
      2. Data access management
  5. Configuring report
    1. What is a report
    2. Data source
    3. Slice
    4. Options
    5. Number formatting
    6. Conditional formatting
    7. Set the report for the component
    8. Get the report from the component
    9. Date and time formatting
    10. Configuring global options
    11. Export and print
    12. Calculated values
    13. Custom sorting
  6. Integration with frameworks
    1. Available tutorials
    2. Integration with AngularJS (v1.x)
    3. Integration with Angular
    4. Integration with React
    5. Integration with Webpack
    6. Integration with ASP.NET
    7. Integration with jQuery
    8. Integration with JSP
    9. Integration with TypeScript
    10. Integration with RequireJS
    11. Integration with PhoneGap
  7. Integration with charts
    1. Integration with Highcharts
    2. Integration with Google Charts
    3. Integration with FusionCharts
    4. Integration with any charting library
  8. Customizing
    1. Customizing toolbar
    2. Customizing appearance
    3. Customizing context menu
    4. Localizing component
  9. Updating to the latest version
    1. Updating to the latest version
    2. Release notes
    3. Migration guide from 2.6 to 2.7
    4. Migration guide from 2.5 to 2.6
    5. Migration guide from 2.4 to 2.5
    6. Migration guide from 2.3 to 2.4
    7. Migration guide from 2.2 to 2.3
    8. Documentation for older versions
Table of contents

Troubleshooting

Welcome to our troubleshooting page. Here you can find an explanation of errors that you might experience while working with Flexmonster Pivot, as well as simple instructions on how to fix them.

This page has three sections:

  1. Installation troubleshooting
  2. Issues with license keys
  3. Issues with data source
Installation troubleshooting

If you are facing any problems with the embedding of the component, in your browser go to the page where Flexmonster should be displayed and open the browser’s console to check if there are any errors in the console. In this section, you can find the errors that you may see in the console. If you cannot find your error in the list below, post a question to our Help Forum.

Console error: 'GET (any URL)/flexmonster.js 404 (Not Found)'
This error means that flexmonster.js was not loaded successfully. Ensure that the correct path is specified to the flexmonster.js file. This file is located in the flexmonster/ folder inside the package that you downloaded from the site.
Console error: 'Uncaught ReferenceError: Flexmonster is not defined'
Getting this error means that the new Flexmonster() API call was used to embed the component but flexmonster.js was not loaded successfully. Make sure that you have included flexmonster.js in your HTML page. This file is located in the flexmonster/ folder inside the package that you downloaded from the site.
Console error: 'ERROR TypeError: window.Flexmonster is not a function'
This error indicates that an attempt to embed Flexmonster failed because flexmonster.js was not loaded successfully. To resolve this error, include this file in your project. flexmonster.js is located in the flexmonster/ folder inside the package that you downloaded from the site. The other option is to include the file from our CDN:
<script src="https://cdn.flexmonster.com/flexmonster.js"></script>
Pop-up alert and console errors: 'Flexmonster: Unable to create the component. DOM element is null.'
This error is thrown if the container parameter is missing in the new Flexmonster() API call. This parameter is necessary because it sets the selector of the HTML element which will be the container for the component. For an example of how container should be specified, refer to step 3 of our Quick start guide.
Pop-up alert and console errors: 'Flexmonster: Unable to create the component. DOM element with id 'pivotContainer' is not found.'
Such an error indicates that the <div> container for the component was not created. Add a container to your HTML page like so:
<div id="pivotContainer">The component will appear here</div>
Pop-up alert error: 'Flexmonster: Pivot cannot be drawn.'
This error means that the content of the flexmonster/ folder was not loaded successfully. Add the componentFolder parameter to the new Flexmonster() call. For more details about this parameter refer to the new Flexmonster() API call.
Console error: 'GET (any URL)/flexmonster/flexmonster.css 404 (Not Found)'
This error means that the component is located in a folder other than flexmonster/. Specify the componentFolder parameter. For more details about this parameter refer to the new Flexmonster() API call.
Console error: 'GET (any URL)/(your componentFolder parameter)/flexmonster.css 404 (Not Found)'
This error indicates that you specified the componentFolder parameter incorrectly. Make sure that componentFolder contains the URL of the component’s folder (with flexmonster.css and all other necessary files).
Console error: 'GET (any URL)/(your componentFolder parameter)/theme/assets/flexmonster-icons.woff 404 (Not Found); GET (any URL)/(your componentFolder parameter)/theme/assets/flexmonster-icons.ttf 404 (Not Found)'
This error means that the theme/assets/ folder is missing from the component’s folder. Add this folder, which can be found in the flexmonster/ folder inside the package that you downloaded from the site.
Console error: 'GET (any URL)/(your componentFolder parameter)/toolbar/flexmonster.toolbar.js 404 (Not Found)'
This error indicates that the toolbar/ folder is missing from the component’s folder and that toolbar: true was specified when embedding the component. Add this folder, which can be found in the flexmonster/ folder inside the package that you downloaded from the site.
Console error: 'GET (any URL)/(your componentFolder parameter)/lib/d3.min.js 404 (Not Found)'
This error means that the lib/ folder is missing from the component’s folder. The error is also possible if the d3.min.js file was manually removed from the lib/ folder. The d3.min.js library is necessary for using any charts functionality, so the error will only be shown when switching to charts. If any other file was removed from lib/ folder, the same error will appear in the console (only when the component needs these libraries). To get rid of such errors, add the lib/ folder to the component’s folder. The lib/ folder can be found in the flexmonster/ folder inside the package that you downloaded from the site.
License keys

This section explains the meaning of the error pop-ups you may experience if a problem occurs with license keys.

Current key is only applicable for example.com. You are trying to use the following key: XXXX-XXXX-XXXX-XXXX-XXXX
Verify that the domain name shown in your error message (e.g. example.com) matches the domain name of your project for which you have the key. If they are different, contact our client service team.
Integration with third-party charting libraries is not available in the trial version.
For our existing customers, we recommend replacing their trial license key with a development license key or with a production license key. If you are evaluating our component, please contact our client service team and request a special trial key.
Your license key is outdated and will not function with the current version. Please contact our support team to find out about upgrade options.
If you are updating from the previous major version to 2.3 or higher, new license keys are required. If your maintenance is active – please request a new license key for free.
You are trying to use a developer's key on a real domain (example.com). You are trying to use the following key: XXXX-XXXX-XXXX-XXXX-XXXX
This message indicates that a development license key is used which is applicable to a localhost environment only. To get the production key for the production environment (e.g. example.com), please contact our support team.
Your license period has expired. You are trying to use the following key: XXXX-XXXX-XXXX-XXXX-XXXX
This message is shown if your license key has expired. To renew your annual subscription please contact our sales manager.
Your trial period has expired. You are trying to use the following key: XXXX-XXXX-XXXX-XXXX-XXXX
This message means your trial license key has expired. To continue the evaluation of our component please contact our sales team.
Invalid license key. You are trying to use the following key: XXXX-XXXX-XXXX-XXXX-XXXX
Copy the license key you received after purchase and use it in your project. Also check that the license key version is the same as the component’s version. For example, a license key for version 2.3 will not work with previous versions.
License key not found.
This message means that you have not specified a license key. Please specify your license key. For instructions on how the license key should be specified, please refer to step 3 of the Quick start guide.
License key is corrupted.
This message means that you have probably copied only a part of the key. Please open the message you received after purchase and try copying the license key again.
Serial number not found.
This message means that you have not specified a license key. Please specify your license key. For instructions on how the license key should be specified, please refer to step 3 of the Quick start guide.
Serial number is corrupted.
This message means that you have probably copied only a part of the key. Please open the message you received after purchase and try copying the license key again.
Data source

This section explains the meaning of errors you may experience if a problem occurs with the data source.

Unable to open file 'yourfile'. It seems that this file doesn't exist or 'Access-Control-Allow-Origin' header is absent in the requested resource.
This message may refer to one of the reasons below:
  • There is no file with this name on the server. Make sure the filename you are trying to use is correct.
  • The browser requires more privileges to load the data. By default, cross-domain requests from JavaScript are blocked. Enable CORS to make such requests. Refer to enable-cors.org for more details on how to resolve this issue.
  • Internal server error — please open the browser’s console and check the errors there.
CSV, OCSV, and JSON support is not available in the current edition.
Each license key is bound to a data source. Check that the data source type for your license key, the type of the downloaded package, and the data source type you are using are the same. If you want to test a data source that is not included in your licensing plan, leave us a request via Contact Us form.
MS OLAP support is not available in the current edition.
Each license key is bound to a data source. Check that the data source type for your license key, the type of the downloaded package, and the data source type you are using are the same. If you want to test a data source that is not included in your licensing plan, leave us a request via Contact Us form.
Elasticsearch support is not available in the current edition.
Each license key is bound to a data source. Check that the data source type for your license key, the type of the downloaded package, and the data source type you are using are the same. If you want to test a data source that is not included in your licensing plan, leave us a request via Contact Us form.
Mondrian support is not available in the current edition.
Each license key is bound to a data source. Check that the data source type for your license key, the type of the downloaded package, and the data source type you are using are the same. If you want to test a data source that is not included in your licensing plan, leave us a request via Contact Us form.
icCube support is not available in the current edition.
Each license key is bound to a data source. Check that the data source type for your license key, the type of the downloaded package, and the data source type you are using are the same. If you want to test a data source that is not included in your licensing plan, leave us a request via Contact Us form.
File is too large.
This message means that your Flexmonster edition is Pivot Table for SQL/CSV/JSON Basic. This edition has a 5 MB limitation on data size and your file exceeds this limitation. To upload bigger files, upgrade to the SQL/CSV/JSON edition. For further details please contact our client service team.
Error opening URL. Please check your Internet connection.
This error means one of the following:
  • There is no Internet connection. Reestablish this connection.
  • You provided the wrong path to the proxy URL to the OLAP data source (Microsoft Analysis Services or Mondrian). Check that the URL is correct.
  • There is an issue with accessing the data — make sure that current user has enough privileges.
  • A server error occurred — check whether you have any errors in the browser’s console.
Invalid datasource or catalog. Please check.
Check the catalog and cube names that you entered for the connection to the cube. To get the exact names, use our OLAP connection tool from the Toolbar. Click the Connect tab, select To OLAP (XMLA), enter your Proxy URL, and click Connect. Select Data Source Info from the drop-down list. The list of available catalog names will be right under Data Source Info. After choosing the catalog name, the list of cube names will be shown.
Another possible cause of this error message is an internal server error. Try opening the browser’s console and checking there.
Stream error occurred while loading example.com
Check the following points:
  • Check that either your filename (for CSV and JSON data sources) or the proxy URL path, catalog, and cube names (for SSAS and Mondrian data sources) exist and that the current user has sufficient rights to access them.
  • Make sure that cross-domain requests are allowed. Additional information on this resource can be found here: enable-cors.org.
  • Open the console in your browser and check for internal server errors.
  • Check your Internet connection.
  • If you are using SSAS via XMLA protocol, enable cross-origin resource sharing for Internet Information Services (IIS). Check out our detailed step-by-step guide. We also suggest trying our special server-side proxy called Flexmonster Accelerator instead of XMLA (read more).