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:
-
If rebuilding ElastiCube doesn't fix the issue, manually reload each failed table.
-
Open the Sisense ElastiCube Manager application in the BI server.
-
Open the QS_ElastiCube (or your custom elastic cube, if you have one).
-
Click ElastiCube and then click Change Connectivity Settings.
-
Make sure the correct QualiInsight database is selected.
-
Scroll down until you find the bad table, hover over it and click the Change source provider button on the right.
-
In the Connect to Server dialog box, select the database and then select the bad table.
-
In the Change Source Provider Wizard, select the Database type.
-
In the Connect to SQL Server dialog box, click Select Database and choose the database and click OK.
-
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".
-
Repeat steps a-j to reload all the bad tables.
-
Rebuild ElastiCube as explained in Build the Insight ElastiCube.
-