Resolving Issues with Updating EC2EC Passwords in Elasticube Connections

[vsolodkyi]

Resolving Issues with Updating EC2EC Passwords in Elasticube Connections

Summary

This article addresses the issue of updating EC2EC (Elasticube to Elasticube) passwords in the context of employee off-boarding or password changes. 

Specifically, it covers the scenario where tables do not appear in the source cube after updating the password, preventing the completion of the update.

Main Content

Step-by-Step Instructions to Resolve the Issue

1. Identify the Cube Details:  
   Identify the specific cube you are trying to connect from and to.
2. Verify Connection Specificity:
   
• Determine if the issue affects all EC2EC connections or only specific ones.
• For example, if you can update the connection to one cube (e.g., locationsv2) but not another (e.g., ordersv3), note this discrepancy.
  
  
3. Remove and Re-add the EC2EC Table:
   
• Remove the problematic EC2EC table from the source cube.
• Re-add the table to the source cube.
  
  
4. Check for Hidden Columns:
   
• Ensure that all required columns in the source Elasticube are visible.
• If any required columns are hidden, make them visible.
  
5. Rebuild the Cube:
   
• After making the necessary columns visible. Hidden columns in the source Elasticube can often cause issues with table visibility. Always check column visibility if tables do not appear as expected. 
• Rebuild the cube. 
• Verify that the tables now appear correctly in the source cube.

Feedback and Support:

• If the issue persists, contact support with detailed information about the error and the context of its occurrence.
• Providing feedback on your experience can help improve the support process.

Check out this related content: 

Academy Course

Sisense Documentation