Troubleshooting the Accelerator

Error: Your current version of Flexmonster Pivot Table & Charts is not compatible with Flexmonster Accelerator. Please update the component to the minimum required version: X.XXX

This error means that the versions of Flexmonster Accelerator and Flexmonster Pivot are not compatible. To fix this error, update both products to the latest available version. Refer to the Updating to the latest version guide for more details.

Error: Your current version of Flexmonster Accelerator is not compatible with Flexmonster Pivot Table & Charts. Please update the Accelerator to the minimum required version: X.XXX

This error means that the versions of Flexmonster Accelerator and Flexmonster Pivot are not compatible. To fix this error, update both products to the latest available version. Refer to the Updating to the latest version guide for more details.

Console error: "Please try to use another port in flexmonster.config file"

This error occurs when the Accelerator cannot bind to the specified port. Even if the port is free, Windows may have reserved it at the system level.

To diagnose the issue, run the following command:

netsh int ipv4 show excludedportrange protocol=tcp

If the port you specified in flexmonster.config falls within one of the listed ranges, it is reserved by the system and cannot be used. Change the port to one outside the reserved range.

Console error: "Exception of type 'System.OutOfMemoryException' was thrown"

This error may be caused by one of the following:

• If caching is enabled (CACHE_ENABLED=true), it can accumulate data over time and consume all available memory. Set a memory limit using the CACHE_MEMORY_LIMIT property. 
• If the server does not have enough RAM or the Accelerator process is constrained by OS-level memory limits, it may also run out of memory. Consider increasing the available RAM or raising the OS-level memory limit for the Accelerator process.

Console error: "The '<cube name>' object was not found"

This error occurs when the Accelerator cannot find the specified cube and can be caused by one of the following:

• The dataSource.cube property has the wrong name. Check if the name exactly matches the one in SSAS.
• SSAS returns an empty cube collection. For example, if the account under which the Accelerator runs does not have access to the database in SSAS, the Accelerator cannot find the cube by name. Check if the service account has the necessary permissions in SSAS.

Console error: "The query result is too large"

This error is caused by a limitation or misconfiguration in SSAS. To handle this scenario on Flexmonster’s side, we recommend reducing the amount of returned data. This can be done by:

• Applying filters in the report before loading the data.
• Using the subquery to limit the amount of loaded data by the MDX query condition.

Using filters allows switching between different subsets of data that were not initially loaded, while a subquery cuts off part of the data entirely and prevents it from being loaded at all.

Pop-up alert error: "Unauthorized"

This error may be caused by the incorrect WINDOWS_AUTH configuration:

• If WINDOWS_AUTH=false, the Accelerator connects to SSAS under its service account. If this account is not an SSAS administrator and is not added to any cube role, SSAS rejects the connection. To fix this, either add the service account to a role in SSAS or change the account under which the Accelerator service runs in services.msc.
• If WINDOWS_AUTH=true and the app is hosted on a different server, requests may be failing due to CORS restrictions. Make sure ALLOW_ORIGIN in flexmonster.config is set to the exact origin of your application (not *), and that dataSource.withCredentials is set to true. For more details, refer to Configuring the authentication process.

Issue: Flexmonster displays old data after a database update

By default, caching is enabled in the Accelerator. When the underlying database changes, Flexmonster may still display old data because the cache is no longer up to date. It is possible to disable the cache with the CACHE_ENABLED parameter in the flexmonster.config file:

CACHE_ENABLED = false

Access flexmonster.config through the Flexmonster Accelerator Manager.

Still need help?

Try the following steps:

1. Search for related information on our website.
2. Look through the search results. If your topic is already covered in the documentation or support cases, check out the suggested solutions.

If you still need additional help, collect the flexmonster.log file, the saved report configuration, and the Accelerator version, and contact our technical support.