Model import returns success but the ElastiCube does not appear (ECM importElasticubeSchema 500 / BaseError)
Applies to: Sisense Linux · ElastiCube / Live model import/export
Category: Import / Export Model
Symptoms
You import a model export (.smodel) using the UI (Import Model) or the import API.
The import API returns a success (200) response, but the newly imported cube does not appear in the Data page.
In the browser developer tools (Network tab), the ecm/ request fails on the importElasticubeSchema operation. The ECM GraphQL response looks like this:
{ "errors": [ { "error": { "message": "Unexpected error value: { timestamp: \"2026-09-30T09:54:30.137+00:00\", status: 500, error: \"Internal Server Error\", path: \"/api/v1/internal/live_connecto...\" }", "name": "BaseError", "code": 1000, "innerErrors": [ {} ] }, "locations": [ { "line": 2, "column": 3 } ], "path": [ "importElasticubeSchema" ] } ], "data": { "importElasticubeSchema": null } }Key markers: name: "BaseError", code: 1000, path: ["importElasticubeSchema"], data.importElasticubeSchema: null, and a wrapped status: 500 / Internal Server Error on an internal connector path (/api/v1/internal/live_connecto…).
Cause
The exported model definition references a data connector that is not installed on the target environment. The import call itself succeeds (the model metadata is written), but when Sisense resolves the model's schema it cannot load the missing connector. The internal connector endpoint returns a 500, ECM surfaces it as the Baseerror on importElasticubeSchema above, and the cube never finishes materializing — so it does not appear in the UI.
This is a configuration mismatch between the source and target environments, not a defect in the import itself.
Resolution
Identify the connector(s) used by the model. On the source environment, open the model and note every data source / connector it uses (for example, a specific JDBC driver, native connector, or custom connector).
Check the target environment. Confirm each of those connectors is installed and available on the environment you are importing into. A connector present on the source is not guaranteed to exist on the target, especially across different environments or builds.
3nstall the missing connector on the target environment so it matches the source, then restart the relevant services if the connector requires it.
Re-run the import. With the connector in place, the schema resolves correctly and the cube appears in the Data page.
How to confirm you've hit this specific case
The import API response is 200/success, yet the cube is absent from the UI.
The ecm/ request shows the BaseError on importElasticubeSchema with data.importElasticubeSchema: null (see JSON above).
The wrapped error points at an internal connector path (/api/v1/internal/live_connecto…) with status: 500.
The source and target environments differ in installed connectors (verify by comparing the connector lists on both sides).
Prevention
Before migrating or importing models between environments, compare the installed connectors on source and target and install any that are missing on the target first.
Keep connector sets aligned across environments that exchange model exports (dev → prod, old build → new build).
