Troubleshooting

Welcome to the troubleshooting page for Flexmonster Pivot. To troubleshoot Flexmonster CLI, Flexmonster Data Server, or Flexmonster Accelerator, refer to the following guides:

In this guide, 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. If your error is not listed here, contact our technical support.

This page has three sections:

Installation troubleshooting
Issues with license keys
Issues with data source

Installation troubleshooting

If you are facing any issues while embedding the component, access your browser’s console on the webpage with Flexmonster. In the console, check if any errors appear and if so, have a look at this section.

Console error: 'GET (any URL)/flexmonster.js 404 (Not Found)'

The flexmonster.js file was not loaded successfully. Ensure that the correct path is specified to flexmonster.js:

For the npm package

<script src="node_modules/flexmonster/flexmonster.js"></script>

For CDN

<script src="https://cdn.flexmonster.com/flexmonster.js"></script>

For the download package

<script src="flexmonster/flexmonster.js"></script>

Console error: 'Uncaught ReferenceError: Flexmonster is not defined'

The new Flexmonster() API call was used to embed the component but the flexmonster.js file was not loaded successfully. Make sure that you have included flexmonster.js in your HTML page:

For the npm package

<script src="node_modules/flexmonster/flexmonster.js"></script>

For CDN

<script src="https://cdn.flexmonster.com/flexmonster.js"></script>

For the download package

<script src="flexmonster/flexmonster.js"></script>

Console error: 'SCRIPT5009: Flexmonster is undefined'

The ES6 version of the component is used in Internet Explorer. Since IE does not support the ES6 standard, use the ES5 version of the component (the flexmonster.es5.js file) for this browser. It is available:

Through the CLI and npm (along with the flexmonster.es5.full.js file)
On CDN
In the download package (inside the flexmonster/ folder)

Console error: 'ERROR TypeError: Flexmonster is not a constructor'

Flexmonster embedding failed since the flexmonster.js file was not loaded successfully. Make sure that flexmonster.js is successfully loaded in your project:

For the npm package

<script src="node_modules/flexmonster/flexmonster.js"></script>

For CDN

<script src="https://cdn.flexmonster.com/flexmonster.js"></script>

For the download package

<script src="flexmonster/flexmonster.js"></script>

Console error: 'ERROR TypeError: window.Flexmonster is not a function'

Flexmonster embedding failed because the flexmonster.js file was not loaded successfully. To resolve this error, include flexmonster.js in your project:

For the npm package

<script src="node_modules/flexmonster/flexmonster.js"></script>

For CDN

<script src="https://cdn.flexmonster.com/flexmonster.js"></script>

For the download package

<script src="flexmonster/flexmonster.js"></script>

Pop-up alert and console errors: 'Flexmonster: Unable to create the component. DOM element is null.'

The container parameter is missing from the new Flexmonster() API call. This parameter is necessary because it sets the selector of the HTML element which serves as the container for the component. For details on how the 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.'

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.'

The content of the flexmonster/ folder was not loaded successfully. Add the componentFolder parameter to the new Flexmonster() call. For more details on this parameter, refer to the documentation about new Flexmonster().

Console error: 'GET (any URL)/flexmonster/flexmonster.css 404 (Not Found)'

The component is located in a folder other than flexmonster/. Specify the componentFolder parameter. For more details on this parameter, refer to the documentation about new Flexmonster().

Console error: 'GET (any URL)/(your componentFolder parameter)/flexmonster.css 404 (Not Found)'

The componentFolder parameter is specified 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)'

The theme/assets/ folder is missing from the component’s folder. Find flexmonster/theme/assets/ inside the download package and copy it to the folder with Flexmonster files.

Console error: 'GET (any URL)/(your componentFolder parameter)/lib/d3.min.js 404 (Not Found)'

The d3.min.js file is missing from the lib/ folder. The d3.min.js library is necessary for using Flexmonster Pivot Charts, so the error will be shown when switching to charts.
Similar errors may appear in the console if the lib/ folder is missing from the folder with Flexmonster files or any other file was removed from lib/.
To get rid of such errors, find flexmonster/lib/ inside the download package and copy it to the folder with Flexmonster files.

Console warning: 'Flexmonster: CSS version mismatch'

flexmonster.css and flexmonster.js versions do not match. This can happen if flexmonster.css has not been updated along with other Flexmonster files.
Check which JavaScript and CSS versions are specified in the warning’s text. Alternatively, you can check flexmonster.css and flexmonster.js versions by viewing these files through the Sources tab in your browser’s developer tools.

See how the version is specified in CSS and JavaScript files

flexmonster.css:

:root {
    --fm-version: "<version>"
}

flexmonster.js:

/** 
 * Flexmonster Pivot Table & Charts
 * <version>
*/

If flexmonster.css and flexmonster.js versions are not the same, follow the steps below:

Update flexmonster.css and flexmonster.js to the same version.
Clear your browser cache to make sure the browser does not load cached Flexmonster files.
In the browser, check if flexmonster.css and flexmonster.js versions match.

If the warning persists, contact our technical support.

Pop-up alert error: 'Can't enter fullscreen'

The fullscreen feature is blocked by the Feature-Policy fullscreen directive sent from your server. To permit fullscreen, add your project’s domain name to the directive’s allow list. For example:

Feature-Policy: fullscreen https://example.com

License keys

This section lists solutions to errors that may occur with license keys.

Current key is applicable only to 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 your project’s domain name. If they are different, contact our team.

Integration with third-party charting libraries is not available in the trial version.

A trial license key does not support integration with third-party charting libraries. Contact our team to request a special trial key.
For our customers, we recommend replacing the trial key with their development or production license key.

Your license key is outdated and will not function with the current version. Please contact our team to find out about upgrade options.

The license maintenance on the key you’re using has expired. Contact our team for assistance.

You are trying to use a development key on a real domain (example.com). You are trying to use the following key: XXXX-XXXX-XXXX-XXXX-XXXX

A development license key is used on a real domain. Such a key is applicable to localhost environments only. To get the production key for the production environment or the development key for the real domain (e.g., example.com), contact our team.

Your license period has expired. You are trying to use the following key: XXXX-XXXX-XXXX-XXXX-XXXX

Your license key has expired. To renew your annual subscription, contact our team.

Your trial period has expired. You are trying to use the following key: XXXX-XXXX-XXXX-XXXX-XXXX

Your trial license key has expired. To continue the evaluation of our component, contact our team for trial extension.

Invalid license key. You are trying to use the following key: XXXX-XXXX-XXXX-XXXX-XXXX

This error may be caused by one of the following reasons:

Only a part of the license key has been set in the component. Open the email you received after purchase and copy the license key again.
The license key is not compatible with your version of Flexmonster. Contact our team to request another license key.

You are trying to use a template license or trial key: "XXXX-XXXX-XXXX-XXXX-XXXX". Please replace "XXXX-XXXX-XXXX-XXXX-XXXX" with an actual key.

A key placeholder is used instead of a real license or trial key. Replace "XXXX-XXXX-XXXX-XXXX-XXXX" with your actual key. If you don’t have a license key, contact our team.

License key not found.

A license key is not specified. For instructions on how the license key should be specified, refer to our license keys guide.

License key is corrupted.

Only a part of the license key has been set in the component. Open the email you received after purchase and copy the license key again.

Serial number not found.

A license key is not specified. For instructions on how the license key should be specified, refer to our license keys guide.

Serial number is corrupted.

Only a part of the license key has been set in the component. Open the email you received after purchase and copy the license key again.

Data source

Here you can find solutions to errors that you may face when connecting to the data source or loading data into Flexmonster.

Unable to open the FileName file.
Check the following points to resolve the issue:
- make sure the file exists
- make sure the 'Access-Control-Allow-Origin' header is present in the requested resource
- check the browser console for any errors

This message may be caused by one of the following:

There is no file with this name on the server. Make sure you are using the correct filename.
Note that if you are trying to connect to a local file, the filename property will not work since JavaScript has no access to the filesystem.
To open a local file, use the dataSource.browseForFile property or the Connect Toolbar tab. Alternatively, you can upload the file to a server and refer to it in the filename property.
Your 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.

Error opening URL. Please check your Internet connection.

This error may be caused by one of the following:

There is no Internet connection. Reestablish the connection.
There is an issue with accessing the data — make sure that the current user has enough privileges.
A server error occurred — check whether you have any errors in the browser’s console.
You provided the wrong path to Microsoft Analysis Services proxy URL. Ensure that the URL is correct.

The data source or catalog is invalid. Please check the connection details.

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:

Choose the Connect tab and select To OLAP (XMLA).
Enter your Proxy URL and click Connect.
Select the data source from the Data source info drop-down list.
Choose the catalog from the Catalog drop-down list.
Select the cube name from the Cube drop-down list.

Another possible cause of this error message is an internal server error. Check your browser’s console for any errors.

A stream error occurred while loading example.com

Check the following points:

Ensure 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. Refer to enable-cors.org for more details.
Check your browser’s console 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).

Unable to connect to the Elasticsearch endpoint 'XXX'.
Check the following points to resolve the issue:
- make sure that the URL is correct
- enable CORS
- check the browser console for any errors

This message may be caused by one of the following:

Incorrect URL to your Elasticsearch endpoint. Ensure that you have specified the correct URL in the dataSource.node property.
Cross-domain requests from JavaScript are blocked. Enable CORS to allow such requests.
Internal server error. Check for errors in your browser’s console.
No Internet connection. Reestablish it.

no such index [XXX]

The specified Elasticsearch index does not exist on your server. Make sure you have specified the correct index in the dataSource.index property.

[1:122] [date_histogram] unknown field [calendar_interval], parser not found

Starting from version 2.9.26, Flexmonster applies the mapping.calendar_interval property to the date fields in the slice by default. The calendar_interval is not available in Elasticsearch versions before 7.2.
If your version of Elasticsearch is older than 7.2 and you are using dates in the slice, specify the mapping.interval property explicitly to fix the error. For example:

report: {
	dataSource: {
		type: "elasticsearch",
		// other configs
		mapping: {
			"YourDateField": {
				interval: "day"
			}
		}
	}
}

[1:122] [date_histogram] unknown field [fixed_interval], parser not found

You are using the mapping.fixed_interval property, which is not supported in your version of Elasticsearch. The fixed_interval was added to Elasticsearch in version 7.2 and is not available in older versions.
To fix the error, specify the mapping.interval property instead of fixed_interval. For example:

report: {
	dataSource: {
		type: "elasticsearch",
		// other configs
		mapping: {
			"YourDateField": {
				interval: "3h"
			}
		}
	}
}

CSV and JSON support is not available in the current edition.

Your license key does not cover the use of CSV and JSON data sources. Ensure that the data source type of your license key and the data source type you are using are the same.