Build Errors and Solutions

Comments

31 comments

  • Avatar
    Joe McClure

    The given key was not present in the dictionary.

    5
    Comment actions Permalink
  • 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.

    2
    Comment actions Permalink
  • Avatar
    Yugandhar Boddati

    Error message: "Build Ended"

    When we are trying to Build any elastic cube we are getting the same error when we build the same cube in server it is working. 

    Note: We haven't done any changes in the server or any version up-gradation, it happened all of a sudden while we are working.  

    We are unable to build any cube from any user(even super admin access)

    Please check the below screenshot for reference. 

     

    2
    Comment actions Permalink
  • 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

    1
    Comment actions Permalink
  • 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

    1
    Comment actions Permalink
  • Avatar
    Andrey Razumovsky

    we are having the following issue when building a table with 30M rows on Linux.

     

    Error message:

    java.sql.SQLNonTransientConnectionException: Connection to server lost! (mserver5 still alive?). Build failed: Unable to connect to Monet

     

    Build Stage: importing data

     

    currently no idea why this fails. utilization shows that there is enough resources.

    1
    Comment actions Permalink
  • Avatar
    Jon Green

    Trying to build a new elasticube on top of an imported spreadsheet, no issues previously but now getting the error 'instance must be started before calling this method' on one of the tables

    1
    Comment actions Permalink
  • Avatar
    Hendri Tan

    Hi All,

    Don't know whether you guys solved this or not, but I also getting the same error and it works after I restart these services :

    - Sisense.ECMLogs 

    - Sisense.ECMS

    - Sisense.ECMServer

    reference : https://support.sisense.com/hc/en-us/articles/360011753314-Identifying-Sisense-Services 

    Good luck!

    1
    Comment actions Permalink
  • 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.

    0
    Comment actions Permalink
  • 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

    0
    Comment actions Permalink
  • 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

    0
    Comment actions Permalink
  • 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)

    0
    Comment actions Permalink
  • 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

    0
    Comment actions Permalink
  • 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

    0
    Comment actions Permalink
  • 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)

    0
    Comment actions Permalink
  • 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.

    0
    Comment actions Permalink
  • 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

    0
    Comment actions Permalink
  • 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.
     
    0
    Comment actions Permalink
  • 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!

    0
    Comment actions Permalink
  • 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.

     

     

    0
    Comment actions Permalink
  • 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

    0
    Comment actions Permalink
  • Avatar
    Marianna Shapira

    Good Morning!

    We encountered the following problem for the second time in a week. Last time it just was solved on it's own, we did nothing:

    Elasticube Buid Failed:

    Insufficient System Resources Insufficient Space on INSTALLATION Drive Only 832 KB available, minimum required is 131,072 KB

    Any ideas how to fix this situation are welcome, as all our dashboards are unavailable right now.

     

    Thank You!

     

    0
    Comment actions Permalink
  • Avatar
    Susan McKeever

    I have a rest api connection to a domino database.  the table has been building successfully and now I get the error Build Failed on SQL Execution Exception in DirectCommand.ExecuteReader():DirectCommand.ExecuteReader failed: Query number 0: SELECT: no such table 'aAnBXwAaAttendance'.'

    The table name is actually AnBAttendance.  If I delete and rebuild the table I will get the same error but on another table??

    Thank you for your help.

    0
    Comment actions Permalink
  • Avatar
    Delsaran Bigglesworth

    Error message: "error: A step in Task "Task_for_FooBar" failed: Cannot read property 'assertQueue' of undefined"

    Build stage: Error message is displayed at the very end of the task build log, but I can't find where it actually happens.

    0
    Comment actions Permalink
  • Avatar
    Eloy Meira

    Hi,

    After upgrading to version 8.1.1.10190 we are not able to build the Elasticube anymore that is connected

    to AWS Aurora (postgre).

    It doesn't even start and the system shows the following Error in the build process window:

    Unable to show build details due to a communications error, please contact your administrator.

     

    The build works fine in version 7.2 but it doesn't even start in version 8.1. Nothing

    else has been done to the system or design other that the upgrade.

     

    0
    Comment actions Permalink
  • Avatar
    Michael Becker

    Eloy,

    it would mean that probably you have syntax error in one of your Custom SQL. I'm assuming you are working on shared ECube.

    0
    Comment actions Permalink
  • Avatar
    Chris Kerrison

    I also am receiving this error building a brand new elasticube after upgrading from 7.3 to 8.1.1.   It worked fine building it from the Server console but the web portal still doesn't think the cube has been built.  I also have 2 other existing cubes that are now failing for various reasons,  (failed importing and failed allocating memory for custom table)

    0
    Comment actions Permalink
  • Avatar
    Paul Furman

    This error comes up very consistently, can we get a resolution, please?  It existed in 8.0.x and now in 8.2.1

     

    0
    Comment actions Permalink
  • Avatar
    Yosuke Kanii

    We are also experiencing the error "Unable to show build details due to a communications error, please contact your administrator".  This began to happen once we restored a backup onto a new installation of Sisense.  

    WebSocket traffic doesn't seem to indicate any failure, and it continues to send a single number (e.g. "2") back and forth from the client to server, even after the error is displayed.  

    What can we check to troubleshoot this issue?

    0
    Comment actions Permalink
  • Avatar
    Eloy Meira

    There was an problem with the version that was resolved with 8.1 and beyond. 

    This doesn't mean we are trouble free but at least the one we suffered (resulting in DDIC corruption) is not happening anymore.

    0
    Comment actions Permalink

Please sign in to leave a comment.