This error means that flexmonster.js was not loaded successfully. Please specify the correct path to the flexmonster.js file. This file is located in flexmonster/ folder inside of the package you have downloaded from the site.

Getting this error means that new Flexmonster() API call was used to embed the component but flexmonster.js was not loaded successfully. Please include flexmonster.js into your HTML page. This file is located in flexmonster/ folder inside the package you have downloaded from the site.

This error indicates that an attempt to embed Flexmonster failed because flexmonster.js was not loaded successfully. Please include this file into your project. flexmonster.js is located in flexmonster/ folder inside the package you have downloaded from the site. The other option is to include the file from our CDN:

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

This error is thrown if container parameter is missing in new Flexmonster() API call. This parameter is important because it sets the selector of the HTML element which will be a container for the component. For the example how container should be specified, please refer to step 3 of the Quickstart guide.

Such error indicates that <div> container for the component was not created. Please, add container to your HTML page the following way:

<div id="pivotContainer">The component will appear here</div>

Such error means that the content of the flexmonster/ folder was not loaded successfully. Please add componentFolder parameter to new Flexmonster() (for more details about this parameter refer to new Flexmonster() API call).

This error means that the component is located in a folder other than flexmonster/. Please specify componentFolder parameter (for more details about this parameter refer to new Flexmonster() API call).

Getting such error indicates that you specified componentFolder parameter incorrectly. Please make sure that componentFolder contains the URL of the component’s folder (with flexmonster.css and all other necessary files).

This error means theme/assets/ folder is missing from the component’s folder. Please add this folder, which can be found in flexmonster/ folder inside the package you have downloaded from the site.

Getting such error indicates toolbar/ folder is missing from the component’s folder and toolbar: true was specified when embedding the component. Please add this folder, which can be found in flexmonster/ folder inside the package you have downloaded from the site.

This error means lib/ folder is missing from the component’s folder. The error is also possible if d3.min.js file was manually removed from lib/ folder. d3.min.js library is necessary for using 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 console (only when the component needs these libraries). To get rid of such errors, please add lib/ folder to the component’s folder. lib/ folder can be found in flexmonster/ folder inside the package you have downloaded from the site.

Please verify that the domain name shown in your error message (e.g. example.com) matches the domain name of your project for which you requested the key. In case they are different, you should contact our client service team.

For our existing customers, we recommend replacing the trial license key with the development license key or with the production license key. If you are evaluating our component, please contact our client service team and request the special trial key.

In case you are updating from the previous major version to 2.3 or higher, the new license keys are required. If your maintenance is active – please request new license keys for free.

This message indicates that the development license key is used. It is applicable to localhost environment only. To get the production key for the production environment (e.g. example.com), please contact our support team.

This message is shown if your license key has expired. To renew your annual subscription please contact our sales manager.

This message means your trial license key has expired. To carry on the evaluation of our component please contact our sales team.

Please copy the license key you received after the purchase and use it in your project. Also, check that the license key version is the same as the component’s version. For example, the license key for version 2.3 would not work with previous versions.

This message means that you have not specified any license key. Please specify your license key. For the instructions how the license key should be specified, please refer to step 3 of the Quickstart guide.

This message means that you have probably copied only a part of the key. Please open the message you received after the purchase and copy the license key once more.

This message may refer to one of the reasons below:

• There is no file with such name on the server. Please make sure the filename is correct.
• The browser requires more privileges to load the data. By default, cross-domain requests from JavaScript are blocked. Please enable CORS to make such requests. You may refer to enable-cors.org to resolve the issue.
• Internal server error — please open browser’s console and check the errors there.

Each license key is bound to a data source. Please check that data source type for your license key, the type of the downloaded package and the data source type you actually use correspond to each other. In case you want to test some other data source, which is not included in your licensing plan, leave a request via Contact Us form.

Each license key is bound to a data source. Please check that data source type for your license key, the type of the downloaded package and the data source type you actually use correspond to each other. In case you want to test some other data source, which is not included in your licensing plan, leave a request via Contact Us form.

Each license key is bound to a data source. Please check that data source type for your license key, the type of the downloaded package and the data source type you actually use correspond to each other. In case you want to test some other data source, which is not included in your licensing plan, leave a request via Contact Us form.

Each license key is bound to a data source. Please check that data source type for your license key, the type of the downloaded package and the data source type you actually use correspond to each other. In case you want to test some other data source, which is not included in your licensing plan, leave a request via Contact Us form.

This message means that your edition is Pivot Table for SQL/CSV/JSON Basic. Such edition has 5 MB limitation on data size and your file exceeds this limitation. For uploading bigger files you should upgrade to the SQL/CSV/JSON edition. For further details please contact our client service team.

This error means one of the following:

• There is no Internet connection. Please reestablish the connection.
• You provided the wrong path to proxy URL to the OLAP data source (Microsoft Analysis Services, Mondrian or icCube). Please check whether the URL is correct.
• There is an issue with the access to the data — please make sure that current user has enough privileges.
• Some server error occurred — please check whether you have any errors in the browser’s console.

Check catalog and cube names you entered for connection to the cube once more. To get the exact names please use our OLAP connection tool from the toolbar. Click 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 the Data Source Info and 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. Please try opening the browser’s console and checking there.

Please check the following points:

• Check that your filename/path to proxy URL to the OLAP data source/catalog and cube names exist and the current user has enough rights to access them.
• Make sure that cross-domain requests are allowed. Find additional information on this resource: enable-cors.org.
• Open console in your browser and check for internal server errors.
• Check your Internet connection.
• If you are using MSAS via XMLA protocol, please enable cross-origin resource sharing for Internet Information Services (IIS). Check out our detailed step-by-step guide. Also, we suggest trying our special server-side proxy Accelerator instead of XMLA (read more).