Skip to main content
Version: 2023.3

ElastiCube Table Build Error: "key already exists in the collection"

Error Message​

Connection Failed
The key __<keyName>__ already exists in the collection.

Description​

While building ElastiCube, one or more tables fail with the above error.

For example:

.

Clicking Continue results in a failed build of the Quali Insight database.

Solution​

To resolve the issue:

  1. Build the Insight ElastiCube.

  2. If rebuilding ElastiCube doesn't fix the issue, manually reload each failed table.

    1. Open the Sisense ElastiCube Manager application in the BI server.

    2. Open the QS_ElastiCube (or your custom elastic cube, if you have one).

    3. Click ElastiCube and then click Change Connectivity Settings.

    4. Make sure the correct QualiInsight database is selected.

    5. Scroll down until you find the bad table, hover over it and click the Change source provider button on the right.

    6. In the Connect to Server dialog box, select the database and then select the bad table.

    7. In the Change Source Provider Wizard, select the Database type.

    8. In the Connect to SQL Server dialog box, click Select Database and choose the database and click OK.

    9. In the Change table with Tables/Views dialog box, select the bad table and click Change.

      If you see multiple instances of the table, select the one that has Scheme Name "dbo".

    10. Repeat steps a-j to reload all the bad tables.

    11. Rebuild ElastiCube as explained in Build the Insight ElastiCube.

Minimum Requirements for CloudShell Servers and Clients