Build Errors and Solutions

Comments

18 comments

  • Avatar
    Sam Ovenshine (Edited )

    Error message: "ElastiCube <Name> is having difficulties closing."

    Build Stage: Finalizing Build

    Note: This should be reduced in Sisense 6.7 or later

    Troubleshooting

    Modify C:\ProgramData\Sisense\PrismServer\ElastiCubeConfiguration.xml

    -Increase <AbacusDbFarmGraceFulTimeoutInSeconds>300</AbacusDbFarmGraceFulTimeoutInSeconds> to 300

    -Increase <AbacusDbFarmForceFulTimeoutInSeconds>1200</AbacusDbFarmForceFulTimeoutInSeconds> to 1200

    After the updates, save the file and restart the ElastiCubeManagementService.

  • Avatar
    Sam Ovenshine

    Error message: "Accumulative Changes Log Creation Failed Error Create Patch [The requested operation could not be completed due to a file system limitation ]"

    Build Stage: Initializing Build

    Note: Occurs only on accumulative builds. It is a Windows OS issue in some cases.

    Troubleshooting: 

    1. Check that there is adequate disk space

    2. Sisense saves temporary copies of the ElastiCube during the build in C:\ProgramData\Sisense\PrismServer\Patches. To move this location to another drive, modify C:\ProgramData\Sisense\PrismServer\ElastiCubeConfiguration.xml:

    - Add on the second-to-last line (just before the </ElastiCubeConfiguration> closing tag), the following text: <DefaultPatchesDirectory>D:\</DefaultPatchesDirectory>, where D:\ is the new patches location

    - Restart the ElastiCubeManagementService

    3. If that doesn't resolve it, navigate to the Sisense Server Console preferences and uncheck Compress on build (https://support.sisense.com/hc/en-us/articles/115013989107-Server-Console-Preferences-Configuration)

    4. Alternatively, defragment the affected drive

  • Avatar
    Sam Ovenshine (Edited )

    Error message: "There was no endpoint listening at net.pipe://localhost/CloudManagementService that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details."

    Build Stage: In the build process or when interacting with ElastiCubes in the ElastiCube Manager

    Notes: Tends to be sporadic.

    Troubleshooting:

    1. Confirm that the ElastiCube Server is up and running

    2. If so, please try to restart services:

    ElastiCubeManagmentService
    Sisense.Repository
    Sisense.Oxygen
    Restart IIS by running 'iisreset' as an adminstrator in the command prompt

  • Avatar
    Sam Ovenshine

    Error message: "Exception in DirectCommand.ExecuteReader(): DirectCommand.ExecuteReader failed: Query number 0: MALException:algebra.join:GDK reported error.
    ERROR: bunfastins: bat too large"

    Build Stage: During the build on a table/field

    Notes: May have multiple root causes

    Troubleshooting:

    1. Typically caused by a problematic join in the ElastiCube Manager

    2. Review the last table/column mentioned in the build log for any incorrect joins (massive cross joins/not specifying a join ON clause, joining tables/fields incorrectly)

  • Avatar
    Sam Ovenshine

    Error message: "The ElastiCube failed to complete query request (Connection lost)"

    Build Stage: Building a custom field or custom SQL expression table

    Note: Can occur on cubes that previously built successfully as the volume of data grows. Less common on later versions of Sisense.

    Troubleshooting:

    1. Review the build logs for the last mentioned column or table

    2. Review the SQL query for that field/table. The error indicates that Sisense is having trouble performing the SQL query used to create the field or column.

    3. Multiple date/time functions, complex operations, large joins, repeated use of UNION, nested CASE statements, and others are often the culprit.

    4. Try to rewrite or restructure the query in a simpler way to test

  • Avatar
    Sam Ovenshine

    Error message: "Import failed - Specified Cast is not valid"

    Build stage: Importing data from a datasource

    Note: Affects several connectors in 6.6 and later, including Redshift, PostgreSQL, and Oracle

    Troubleshooting:

    For Redshift and PostgreSQL:

    - This issue manifests on Sisense 6.6 and was resolved on Sisense 6.7

    For Oracle:

    - This issue manifests on Sisense 6.6 and was resolved on Sisense 7.0. It occurs when importing data with more than 26 digits of precision. Apart from upgrading, the data can be cast/truncated/rounded in a manual query.

  • Avatar
    Sam Ovenshine (Edited )

    Error message: "UNSUPPORTED_CLIENT: TLS 1.0 has been disabled in this organization. Please use TLS 1.1 or higher when connecting to Salesforce using https."

    Build stage: Importing data from Salesforce

    Note: Please see https://support.sisense.com/hc/en-us/articles/115000534227-Salesforce-Connector-Updates for more information

    Troubleshooting:

    1. Update to Sisense 6.5 or later.

    2. Refresh the connectivity settings for existing builds that connect to Salesforce

    3. Confirm the Sisense.CLRConnectorsContainer service is running

    4. Confirm that files exist at C:\Program Files\Sisense\DataConnectors\DotNetContainer\Connectors\Salesforce. If not, repair the Sisense installation

    5. Move out the files at C:\Program Files\Sisense\DataConnectors\DotNetContainer\Connectors\Salesforce. Download the new connector files here and place them in that location. Restart the Sisense.CLRConnectorsContainer and Sisense.Discovery services. Reopen the ElastiCube Manager and try again.

    6. If needed, disable the requirement to use TLS 1.1 on your Salesforce side

  • Avatar
    Sam Ovenshine

    Error message: "Import Failed ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified."

    Build stage: Importing data from using an ODBC connector

    Troubleshooting:

    1. Confirm you have set up the DSN with ODBC Data Sources (64-bit) (%windir%\system32\odbcad32.exe)

    2. Confirm you have set up the DSN as a System DSN rather than User DSN

    3. Test the DSN to confirm you can connect successfully before attempting to build

  • Avatar
    Sam Ovenshine

    Error message: Updating BBP for 'xxxx' failed. Capacity<Count (xxx < yyy).

    Build stage: Creating custom SQL expression tables/fields

    Troubleshooting:

    1. Upgrade to Sisense 6.6 or later

    2. Perform a full build, rather than a schema changes build

    3. Review and/or rewrite the custom SQL expression the build is failing on

  • Avatar
    Sam Ovenshine

    Error message: Exception in DirectCommand.ExecuteReader(): DirectCommand.ExecuteReader failed:  Query number 0: SQLException:int:conversion of string '...' failed

    Build stage: Creating custom SQL expression tables joined to existing tables

    Troubleshooting:

    1. Copy your new Custom SQL expression and save it somewhere

    2. Remove the custom table and all indexes on the existing table

    3. Recreate the new table with your stored expression but don't join it to your existing table

    4. Perform a Schema Changes build

    5. Re-add the relationship between the new and the existing table

    6. Perform a Schema Changes build

  • Avatar
    Sam Ovenshine

    Error message: "Connection Timeout: The request channel timed out while waiting for a reply after 00:02:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout."

    Build stage: Initial, as soon as the build is started

    Note: Error message comes up in a window in the ElastiCube Manager. This error may be coupled with other erratic or incorrect build behavior. The cause is that some Sisense files have been corrupt.

    Troubleshooting:

    1. Record any ElastiCube Manager scheduled build settings set up to back them up

    2. Stop the ElastiCubeManagementService

    3. Go to C:\ProgramData\Sisense\PrismServer

    4. Rename ElastiCubeCatalog to ElastiCubeCatalog0

    5. Restart the ElastiCubeManagementService. The service restart may take longer than usual.

    6. Re-create your scheduled build settings in the ElastiCube Manager (they may be deleted in the troubleshooting process)

  • Avatar
    Sam Ovenshine

    Error message: "Memory allocation has failed for {ElastiCube name}. Please verify you have sufficient RAM and try to rebuild."

    Build stage: Importing data from data source tables

    Troubleshooting:

    1. Review the memory usage on the server at the build time. If it's nearly maxed out, try to reduce the number of rows or increase the machine hardware.

    2. If the memory is not heavily in use, review the number of columns in the source table. Uncheck 'Import' on unneeded fields, or use a custom import query to only import necessary fields.

  • Avatar
    Sam Ovenshine (Edited )

    Issue: New CSV files placed in a folder are not picked up in the build process

    Build stage: Importing data from a folder of CSV files

    Troubleshooting:

    1. Open C:\ProgramData\Sisense\PrismServer/ElastiCubeConfiguration.xml

    2. Add a new tag with the following text:

    <UseDotNetCsvConnector>true</UseDotNetCsvConnector>

    For example:

    3. Restart the ElastiCubeManagement service

  • Avatar
    Aaron Vickery
     
    We keep getting these errors even though we know this file doesn't exist and we have re-imported new data.
     
    Error Message: Query Error - Query could not be compiled. Table '[HN_GL_APR.csv]' is not declared. 
     
    Build Stage: Trying to view data in cube (nothing populates in the data set)
     
    Trouble Shooting: We are confirming all the file and data set names match. Not sure what else to do.
     
  • Avatar
    Joe McClure

    The given key was not present in the dictionary.

  • Avatar
    Kate Scheer

    I am getting the error message "Specified cast is not valid" and the above troubleshooting is not helpful at all...

    Anyone else here able to help me figure out why this is happening when I try to build my cube? Thanks!

  • Avatar
    OJ Chakrabarti

    I am getting 'Contacting Elasticube Server' and nothing.

    I have checked manage servers and the elasticube has the spinning icon but I cannot stop or start the elasticube.

     

     

  • Avatar
    James Corvus (Edited )

    The following error occurs when importing a large fact view.  Take out the fact table and the cube can build fine.  Need help solving this issue.

    Error message: Import Failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

    Build Stage: During the build on a table/field

Please sign in to leave a comment.