Could Not Read Chunk Size: an Existing Connection Was Forcibly Closed by the Remote Host Solved

When a build fails it's not e'er easy to identify the root cause of the failure. This post contains How-To troubleshoot your ain build failure and popular build errors.

Yous can search (Ctrl+F) this article for errors or search like errors past build stages.

Topics:

1. How-To Troubleshoot your build failure
   1. Accumulative or Schema Changes builds introduction
   2. Troubleshooting Finalization stage time
   3. Troubleshooting ODBC driver
2. Useful Articles
3. Common errors in Importing information stage
4. Common errors in Custom SQL stage
5. Mutual errors in Initialization phase
6. Common errors in Finalization stage

Quick Troubleshooting and general introduction

ElastiCube builds can be carve up into to three main stages:

one) Data Import

two) Custom SQL (Table\ Column)

three) Initializing/Finalizing

a) Initializing - Cosmos of a proper structure for the data to be stored in the local environment. Something fundamental is failing → restart services

b) Finalization - Arranging metadata and swapping the procedure with new data available for user's queries

Accumulate build and Schema Changes are more fragile and disk consuming than Total build operations. If time allows, ever go with Full build ('Delete existing data') as an immediate recovery.

In Accumulative or Schema Changes builds, the Initializing and Finalizing stages comprise the following operations:

• Initializing - Fill-in existing data folder to the _Alternative information folder to keep _Alternative available for querying during the Accumulative build of the main folder
• Finalizing - Copying all newly accumulated/imported data from the main folder to the _Alternative folder then they're both upwards to date

Troubleshooting Finalization stage time:

During finalizing stage Sisense removes the previous completed build and repoints the process to the new 1. It requires additional resources of Disk Drive which can be longer so expected.

Please ensure that Disk drive organization works fine. Have disk defragmentation to the Disk Drive where cubes are located.

Troubleshooting ODBC driver:

1. Testing your ODBC driver with ODBCTest tool -Microsoft offers a connectivity examination tool for ODBC connector. By running the ODBC Test tool y'all volition be able to connect and query the underlying dataset. Download ODBCTest tool through Microsoft website

Useful Articles

Important Notation:When submitting a ticket to support, add every bit much information as possible, such every bit build stage, data source, screenshot of the error message, and adhere relevant logs:

• Build Process logs: %ProgramData%\SiSense\PrismServer\ElastiCubeProcessLogs\<YourElastCubeName>
• ElastiCube Server Logs: %ProgramData%\Sisense\PrismServer\PrismServerLogs

Importing data

Error message:Naming bug

"Invalid object name" Or "Could not find server '{S1}' in '{S2.S3}'. Verify that the correct server name was specified"

Build stage:Importing data from a datasource

Note:Schema name contains ane or 2 dots (For instance: Schema.Name.BP or Schema.Proper noun)

Troubleshooting:

Edit the query in the ElastiCube and wrap the schema proper name in double-quotes (SELECT * FROM "Schema.Proper name".[table]

Error message: 403:unauthorized error

Build stage:Importing data from some other ElastiCube

Troubleshooting:

This error happens if the user credentials used for logging to the server don't belong to an admin user, every bit simply admin users are allowed through the Sisense ElastiCbue connector.

Fault message:Naming bug

"Import failed - error 500 "Query could non be compiled" [field_name] is ambiguous between 'table_name.field_name' "

Build stage:Importing data from some other ElastiCube

Troubleshooting:

If both tabular array name and field name are the same - change one of them in source cube rebuild the cube and retry to import data again

Mistake bulletin:"Exception while reading from stream"

Build stage:Importing data from Redshift

Troubleshooting:

Go to "C:\Plan Files\Sisense\DataConnectors\DotNetContainer\Connectors\Redshift\Sisense.Connectors.RedshiftConnector.dll.config" file and change the timeout value from "0" to "3000".After saving the change delight restart the Sisense.CLRConnectirsContainer Service and attempt to run the build once more.

Fault message : "There was no endpoint listening at cyberspace.pipe://localhost/CloudManagementService that could take the message. This is oftentimes caused by an incorrect accost or SOAP activity. See InnerException, if present, for more than details."

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

Notes : Tends to be desultory.

Troubleshooting :

1. Ostend that the ElastiCube Server is up and running
2. If and then, delight endeavor to restart services:
   ElastiCubeManagmentService (Sisense Version 7.1 and below)
   Sisense.ECMS (Version 7.two and after)
   Sisense.ECMServer (Version vii.2 and later)
   Sisense.Repository
   Sisense.Oxygen
3. Restart IIS by running 'iisreset' as an Administrator in the control prompt

Fault message: "Could not go connector for XXX database."

Build stage:Importing data from a datasource

Troubleshooting:

Sisense.CLRConnectorContainer (For Sisense Connectors with Framework - JVM) or Sisense.JVMConnectorsContainer (For Sisense Connectors with Framework -.Internet)

Build phase:Importing data from a datasource

Note:The "Data-import chunk size" setting in the ElastiCube Server Preferences windows is fix to a value larger than the bachelor retentivity.

Troubleshooting:

1. Go to SiSense Server Console
2. Click on server preferences
3. Click on "More than Settings..."
4. Set "Data-import chunk size" to a value smaller than the max available memory. The default value of this setting is 100000.

Error bulletin: "Index is out of range" Or "Memory allocation has failed…"

Build stage:Importing information from MongoDB

Troubleshooting:

A full general approach to this issue would be to decrease/minimize the amount of columns generated for that table. There are a few ways to achieve this:

1. If you did non select the virtual tables (containing  _VT_ in their name), try selecting the virtual table instead
2. If the mistake persists even while selecting a virtual table in that location are 2 options:
   1. In the ODBC driver configuration, hide columns that are not necessary for the reporting.
      • Open up the ODBC Data Source Administrator from the windows offset menu and configure the MongoDB commuter
      • Select Schema definition and and so Edit Schema file
      • Check the columns you desire to hide, click save, tha lot or documentsen close the dialog
      • Click on "Upload Metadata" to update the schema definition.
      • In the Elasticube manager, delete the previously generated table and bring in the newly generated table, with the less columns.
   2. Alternatively, in the Elasticube manager, when you select the tables to bring in, instead of bringing in the table as is, edit the SQL query so that you bring in simply those columns needed
   3. Instructions on how to practise so can exist found here.

                                   Rebuild Elasticube.

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

Build phase:Importing data from a datasource

Note:Affects several connectors in Sisense Version vi.6 and later, including Redshift, PostgreSQL, and Oracle

Troubleshooting:

1. For Redshift and PostgreSQL:
   • This issue manifests on Sisense half dozen.vi and was resolved on Sisense half-dozen.7
2. For Oracle:
   • This result manifests on Sisense half-dozen.six and was resolved on Sisense 7.0. Information technology occurs when importing data with more than than 26 digits of precision. Apart from upgrading, the data can be cast/truncated/rounded in a manual query.

Error message: "Mistake [HY000] [Simba][Back up](50090) Conversion from … failed"

Or y'all see a field in the MongoDB but that field does not exist in the table generated in the Elasticube Manager

Build phase:Importing data from MongoDB

Note: The MongoDB ODBC driver automatically generates the schema definition based on data sampling. Since the MongoDB schema is dynamic it is possible that documents that were not sampled had a differentdatatype or construction.

Troubleshooting:

Better sampling volition resolve this upshot.

1. Open upward the ODBC Data Source Administrator through the windows offset carte
2. Select the Mongo driver and click on "Advanced Options"
3. In the documents to sample, increase the number of documents to sample. Yous can also set it to 0 and sample all documents to get the most accurate schema, withal this may have some time, especially if there are a lot or documents:
4. Click OK
5. Click Schema Definition
6. Click Generate All (this may take some time if you sample all documents!)
7. Click Upload Metadata
8. Bring in the new table generated into the Elasticube
9. Rebuild the Elasticube

Event: New CSV files placed in a binder are non picked upwardly in the build process

Build stage:Importing information from a folder of CSV files

Troubleshooting:

1. Open up C:\ProgramData\Sisense\PrismServer\ElastiCubeConfiguration.xml
2. Add a new tag with the following text:<UseDotNetCsvConnector>true</UseDotNetCsvConnector>
3. Restart the ElastiCubeManagement (Sisense Version 7.1 and earlier) or the Sisense.ECMS service and Sisense.ECMServer (Sisense Version 7.2 and later).

Error bulletin: "Retention allocation has failed for {ElastiCube name}. Delight verify yous take sufficient RAM and endeavor to rebuild."

Build stage:Importing information from data source tables

Troubleshooting:

1. Review the retention usage on the server at the build time. If it's well-nigh maxed out, try to reduce the number of rows or increment the car 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 utilize a custom import query to only import necessary fields.

Mistake message: "ERROR [28000][Snowflake][ODBC](11570) Required credential settings are missing:{[PWD]}.

ERROR [08001][Snowflake][ODBC](10380) Unable to establish a connection with information source. Missing settings:{[PWD]}"

Build phase:Importing information from a datasource using an ODBC connector

Note:If yous are trying to setup a new Elasticube using the Snowflake ODBC connection functionality, but continue getting a countersign related connection error, there might be a need to difficult lawmaking the credentials in the Windows Registry.

Co-ordinate to the Snowflake documentation this is a safety precaution by Windows: "The Password field accepts a value, merely does not shop the value. This is a security precaution to ensure passwords are never stored directly in the driver."

Troubleshooting: Hard lawmaking the credentials in the Windows Registry. To do so, please follow the steps below:

1. Open up the Registry Editor (Windows key + R and then type regedit).
2. Once it'south open, navigate toReckoner\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\{Snowflake driver name}​
3. In the right paw pane, right-click on the screen and selectNew > Cord value.
4. Name this valueuid.After adding, right-click on the newly created object and in theEdit String window, enter in theValue data cell the Snowflake login name.
5. Repeat step 3.
6. Name the new valuepwd and repeat footstep iv) but enter the Snowflake countersign.

Error message:"Import Failed Fault [IM002] [Microsoft][ODBC Driver Manager] Information source name not plant and no default driver specified."

Build stage: Importing data from a datasource using an ODBC connector

Troubleshooting:

1. Confirm you lot take ready upwardly the DSN with ODBC Data Sources (64-bit) (%windir%\system32\odbcad32.exe)
2. Confirm you have prepare upward the DSN every bit a System DSN rather than User DSN
3. Test the DSN to confirm you lot can connect successfully before attempting to build

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

Build stage:Importing data from a datasource

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

Troubleshooting:

1. For Redshift and PostgreSQL:
   • This result manifests on Sisense 6.half-dozen and was resolved on Sisense 6.vii
2. For Oracle:
   • This issue manifests on Sisense 6.half-dozen and was resolved on Sisense 7.0. Information technology occurs when importing data with more 26 digits of precision. Apart from upgrading, the information tin be cast/truncated/rounded in a manual query.

Error message: "ORA-12504: TNS:listener Was Not Given The SERVICE_NAME In CONNECT_DATA"

Build stage:Creating custom SQL expression table

Notation: The consequence is that the connectedness string to the Oracle DB is expecting a SERVICE_NAME parameter instead of an SID. The difference betwixt them is that SID is the unique name of the case while the SERVICE_NAME is the alias to the instance

Troubleshooting:

1. Choose Add Data (or ElastiCube > Alter connectivity >  Modify source provider if you're just updating an ElastiCube that started failing).
2. In the Connect to Oracle Database window, uncheck the Use Direct Connectedness checkbox.
3. In theDatabase server location textbox, enter the following:

            (Clarification=(Address=(PROTOCOL=tcp)(HOST=$your_ip)(PORT=$your_port))(CONNECT_DATA=(SERVICE_NAME=$service_name)))          

The variables you lot demand to input are:

                          1                            2                            3                                                                    $your_ip                                            $your_port                            $service_name                                    

     4. Connect to the server and rebuild.

If you need to find out the SERVICE_NAME, yous can practice so by connecting to the Oracle DB and running the following command:

                          ane                                                                    select *                                from                                  global_name;                                    

For more information about the source of the consequence visit the following:

Error message: "Failed to load datasources "

Build phase:Importing data from a datasource

Troubleshooting:

1. Open up the Control Panel > Administrative Tools > Services

ii. Find each of the following services in the list and echo steps three&4. Do this in the following society of services:

• "ElastiCubeManagmentService"
• "Sisense.Repository"
• "SIsense.Oxygen"
• "Sisense.CLRConnectorsContainer"
• "Sisense.JVMConnectorsContainer"
• "SisenseWebExpress" - if you cannot find this service, encounter step 5.

3. Correct-click on the service and select Finish (brand certain the Condition field becomes blank).

4. Right-click on the service again and select Kickoff (brand sure the Status field changes to 'Running').

5. In case SisenseWebExpress is non installed, restart the IIS web server:

1. In your Start card, type 'cmd'.
2. Correct-click the shortcut and select Run as Administrator.
3. In the Command line, type: "iisreset", striking Enter and wait for the IIS server to restart.
4. Close the Command prompt window.

6. Refresh your web browser page.

7. If refreshing the web browser didn't help the upshot, delete browsing data in your spider web browser.

Error message: "Connection is not opened "

Build stage:Importing data from a datasource

Troubleshooting:

1. Open the Control Panel > Administrative Tools > Services

2. Detect each of the following services in the list and repeat steps 3&4. Practise this in the post-obit order of services:

• "Sisense.ECMS"
• "Sisense.CLRConnectorsContainer"
• "Sisense.JVMConnectorsContainer"

3. Right-click on the service and select Stop (make sure the Status field becomes bare).

4. Correct-click on the service again and select Start (make sure the Condition field changes to 'Running').

Custom SQL

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 congenital successfully as the volume of information grows. Less common on afterwards versions of Sisense.

Troubleshooting:

1. Review the build logs for the final 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 cavalcade.
3. Multiple date/time functions, circuitous operations, large joins, repeated use of Spousal relationship, nested Case statements, and others are frequently the culprit.
4. Effort to rewrite or restructure the query in a simpler style to test

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

Build stage:Creating custom SQL expression tables/fields

Troubleshooting:

1. Upgrade to Sisense Version 6.vi or later
2. Perform a total build, rather than a schema changes build
3. Review and/or rewrite the custom SQL expression the build is failing on

Build Stage: During the build on a table/field

Notes: May have multiple root causes

Troubleshooting:

1. Typically acquired by a problematic join in the ElastiCube Manager.
2. Review the final table/column mentioned in the build log for whatever incorrect joins (massive cantankerous joins/not specifying a join ON clause, joining tables/fields incorrectly).

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 salvage it off somewhere else (such as a Notepad certificate).
2. Remove the custom table and all indexes on the existing tabular array.
3. Recreate the new table with your stored expression only don't join it to your existing table.
4. Perform a Schema Changes build.
5. Re-add together the relationship between the new and the existing table.
6. Perform a Schema Changes build.

Initialization

Error message: "Accumulative Changes Log Creation Failed Fault Create Patch[The requested operation could not be completed due to a file arrangement limitation ]" OR "Accumulative Changes Log Creation Failed Fault Create Patch [There is bot enough space on the deejay. ]" OR "Accumulative Changes Log Cosmos Failed"

Build Stage: Initializing Build

Note: Occurs simply on accumulative builds. Tin be acquired by a Windows Os issue in some cases or there is not enough disk space on your Sisense auto.

Troubleshooting:

1. Cheque that there is adequate disk space
2. Sisense saves temporary copies of the ElastiCube during the build in C:\ProgramData\Sisense\PrismServer\Patches. To motion this location to some other bulldoze, modify  C:\ProgramData\Sisense\PrismServer\ElastiCubeConfiguration.xml:
   • Add on the 2d-to-last line (just before the </ElastiCubeConfiguration> closing tag), the post-obit text:<DefaultPatchesDirectory>D:\</DefaultPatchesDirectory>, where D:\ is the new patches location
   • Restart the ElastiCubeManagementService
3. If that doesn't resolve the issue, navigate to the Sisense Server Console preferences and uncheck Compress on build (Run into: Server Console Preferences & Configuration commodity)
4. Alternatively, defragment the afflicted drive (Search for Defragment and Optimize Drives on your server > select the driver that the cubes are saved on > click Optimize)

Error bulletin: "Connexion Timeout: The request aqueduct timed out while waiting for a reply subsequently 00:02:00. Increase the timeout value passed to the phone call to Request or increase the SendTimeout value on the Binding. The fourth dimension allotted to this operation may have been a portion of a longer timeout."

Build stage: Initializing Build

Note: Error bulletin comes upward in a window in the ElastiCube Manager. This error may be coupled with other erratic or incorrect build behavior. This error is probable the result of Sisense files condign corrupted.

Troubleshooting:

1. Record any ElastiCube Director scheduled build settings ready upward to dorsum them upward
2. Stop the ElastiCubeManagementService (on Sisense Version seven.one and earlier) or Sisense.ECMS and Sisense.ECMServer (on Sisense Version 7.2 and afterwards)
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).

Error bulletin: "Elasticube xxxx is already being built" Or build is non starting

Build Stage: Initializing Build

Note: The ElastiCube server service is running on the system business relationship. This issues can be caused past a Microsoft restriction, when the user running the ElasticubeManagement/Sisense.ECMS service doesn't have sufficient credentials (System account by default).

Troubleshooting:

Change the logon properties of the ElastiCube Management Service

Steps:

1. Get toControl Panel >Administrative Tools >Services
2. Find (On Sisense V7.1 and below) ElastiCubeManagementService (on Sisense V7.2 and above) Sisense.ECMS, right-click and selectStop.
3. Find (On Sisense V7.1 and below) ElastiCubeManagementService (on Sisense V7.2 and in a higher place) Sisense.ECMS,  correct-click and selectProperties.
4. Select the Log On tab, selectThis Account then clickBrowse.
5. ClickLocations.
6. Choose your domain (eastward.m., Sisense.local in this example) and clickOK.
7. ClickAdvanced.
8. ClickFind Now, choose the user logged on to the machine and clickOK.
9. The selected user will exist added to the names box, clickOK.
10. Enter and verify the user'south countersign, clickOK.
11. Restart the service.

Error message: "Object reference not gear up to an instance of an object"

Build Stage: Initializing Build (or prior to Initialization)

Note: This error can result from a few dissimilar bug, almost unremarkably for custom columns and custom tables. Information technology is also helpful to retrieve about what changed in the model earlier yous encountered this error.

Troubleshooting:

Verify naming and references of each of the custom SQL expression tables and columns.
Also try a full build of the cube.

Steps:

1. First out with trying a total build of the Elasticube.
2. If yous see this error at the beginning of a build, open up each custom SQL table and parse/preview the expression. Verify table and column names lucifer what is in the model.
3. Try a full build.
4. If you nevertheless see bug, open each custom cavalcade and parse/preview the expression. Verify table and column names match what is in the model.
5. Try some other full build.

Fault bulletin: "Unable to verify the first certificate"

Build Stage: Initializing Build (or prior to Initialization)

Note: T his may indicate that the SSL certificate is non correctly configured (for example, the certificate only has one section, when it should take at least 3)

Troubleshooting: Delight see this post on how to troubleshoot this error

Finalization

Error message:"ElastiCube 30 is having difficulties closing."

Build Phase: Finalizing Build

Notation:This less likely to happen in Sisense V6.7 or subsequently

Troubleshooting:

1. Modify C:\ProgramData\Sisense\PrismServer\ElastiCubeConfiguration.xml
   • Increase <AbacusDbFarmGraceFulTimeoutInSeconds>xxx</AbacusDbFarmGraceFulTimeoutInSeconds> to 300
   • Increase <AbacusDbFarmForceFulTimeoutInSeconds>600</AbacusDbFarmForceFulTimeoutInSeconds> to 1200
2. Later on the updates, save the file and restart the ElastiCubeManagementService (on Sisense Version 7.1 and beneath) or Sisense.ECMS and Sisense.ECMServer (Sisense Version 7.ii and later on)

searsclar1981.blogspot.com

Source: https://support.sisense.com/kb/en/article/build-errors-troubleshooting

Share this post