Resolving Issues with Updating EC2EC Passwords in Elasticube Connections
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.Troubleshooting "BBP Error 1551" in Sisense ElastiCube Builds
Troubleshooting "BBP Error 1551" in Sisense ElastiCube Builds Summary This article provides a comprehensive guide to troubleshooting the "BBP error 1551" that occurs during the build process of ElastiCubes in the Sisense Windows environment. The error typically indicates a discrepancy between the logical schema and the actual result of the ElastiCube, leading to build failures. Main Content Step-by-Step Instructions to Resolve the Issue Identify the Error: The BBP error '1551' indicates a mismatch between the logical schema and the actual data/indexes in the ElastiCube. This is done to prevent inconsistencies. Initial Troubleshooting Steps: Run Build Schema Changes: After creating a Custom Table, run Build Schema Changes. Add the Relationship and run Build Schema Changes again. Run Full Build: Perform a Full Build (Replace All) to ensure all data and indexes are correctly aligned. Check Logs for Detailed Error Information: Build Process Logs: %ProgramData%\SiSense\PrismServer\ElastiCubeProcessLogs\ ElastiCube Server Logs: %ProgramData%\Sisense\PrismServer\PrismServerLogs\ Review these logs to identify any specific issues or patterns that may be causing the build failure. Frequency and Environment Check: Determine how often the scheduled build runs and how frequently it fails with this error. If possible, duplicate the ElastiCube or create a new one for testing purposes and set its schedule to be more frequent. Observe if the issue's frequency increases. Accumulative Build Check: If the error occurs during an accumulative build, consider running a Full Build (Replace All) to reset the schema and data alignment. Troubleshooting Tips and Alternative Solutions No Recent Changes: If no changes have been made to the ElastiCube and the error persists, it may be necessary to investigate any underlying system or environmental changes that could affect the build process. Monitor and Report: Continuously monitor the build process after implementing the above steps. If the issue reoccurs, provide detailed logs and error messages to the support team for further analysis. Check out this related content: Academy Course Sisense Documentation
Resolving the ODBC_Wrapper.dll Error When Connecting Via ODBC
Scenario: A common error when trying to connect via ODBC to a data source is: "Could not load file or assembly 'ODBC_Wrapper.dll' or one of its dependencies..." This error can occur after successfully setting up the ODBC connection in the Windows ODBC Data Source Administrator, when trying to use the ODBC connection in the ElasticubeManager. This error happens due to a missing component in the Windows OS Installation. Solution: Please download and install the following update on your Elasticube server: Microsoft Visual C++ 2015 Redistributable Package (x64). After the installation is complete, restart the Elasticube Manager (and server, if prompted to do so) and try connecting again with your connection string / DSN for the ODBC.RabbitMQ authentication user fix on W2022.3+ version
Symptoms Starting from the W2022.3 version, Sisense uses a non-default authentication user while connecting from any microservices to Sisense RabbitMQ (Sisense.Broker service). In some cases, you may need to manually re-provision the RabbitMQ user. For example: A. RabbitMQ folder was re-created by mistake B. RabbitMQ user creation failed during the Sisense upgrade If microservices do not connect using the "sisense"RabbitMQ user, you may see that Build Logs are not updated on the Data page and will infinitely spin, while showing a "Building "message. Diagnosis 1. Run CMD as Administrator 2. In the command prompt, navigate to the RabbitMQ folder and execute rabbitmqctl list_users: cd "C:\Program Files\Sisense\Infra\RabbitMQ\sbin" rabbitmqctl list_users Example of the correct output (contains "sisense" user) on W2022.3+ version: Example of the incorrect output (please note the output is correct for versions before W2022.3): If you receive the "Error: unable to perform an operation on node 'rabbit@servername'. Please see diagnostics information and suggestions below." error message while running rabbitmqctl commands, copy C:\Windows\System32\config\systemprofile\.erlang.cookie file into C:\Users\<user who runs cmd>\ folder and retry: Solution Step A: Create RabbitMQ User 1. Start CMD as Administrator 2. Navigate to the RabbitMQ folder: cd "C:\Program Files\Sisense\Infra\RabbitMQ\sbin" 3. Run the commands below but remember to replace <password> with your desired value: rabbitmqctl add_user sisense "<password>" rabbitmqctl set_user_tags sisense administrator rabbitmqctl set_permissions -p / sisense ".*" ".*" ".*" 4. Create a new file in the C:\ProgramData\Sisense\RabbitMQ folder. The filename should be "rmq.cred". 5. Use AES Encoding to generate an encoded password. Input: password in plain text from step 2. Example of the output: “QYd1zvhlrLxYvQnWxSmKZQ==". 6. Open "rmq.cred" file in Notepad++ (or other text editor). 7. Enter the encoded password and save the file. Step B: How to make Sisense services use the new RabbitMQ authentication 1. Open cmd as Administrator and navigate to the configuration service module to create a Zookeeper backup file: cd "C:\Program Files\Sisense\app\configuration-service\node_modules\@sisense\sisense-configuration\bin" "C:\Program Files\Sisense\app\NodeJS\v12.7.0\node.exe" sisense-conf export -p 2. Create ZK Backup folder if it is missing: mkdir C:\ProgramData\Sisense\Backup mkdir C:\ProgramData\Sisense\Backup\Configuration 3. Copy created backup to the standard backup folder: copy sisenseConfiguration.json C:\ProgramData\Sisense\Backup\Configuration\manual-zookeeper-backup-2022-05-25.json 4. Open the copied JSON file in Notepad++. 5. Replace all occurrences of "connectionString": "amqp://127.0.0.1:5672" with: For a single node: "connectionString": "amqp://sisense:[email protected]:5672" For a multi-node: "connectionString": "amqp://sisense:[email protected]:5672,amqp://sisense:[email protected]:5672" where "Jb9c8SGq43" - plain text password from step A.2, "10.20.30.1" and "10.20.30.2" - IPs of servers where Sisense.Broker is running. 6. Save the file. 7. Open http://localhost:3030, click five times on the Sisense logo, and navigate to the Backups tab. Select manual-zookeeper-backup-2022-05-25.json file and click the Restore button to import the manually created Zookeeper backup. 8. Restart Sisense.ECMS & Sisense.ECMLogs services. 9. At localhost:3030, click the Restart services button. If you are using a workaround with ?frameMax=0 for any of the microservices, at step B.6, you will also need to replace "connectionString": "amqp://127.0.0.1:5672?frameMax=0" with "connectionString": "amqp://sisense:[email protected]:5672?frameMax=0". If you need assistance with any of the steps above, please get in touch with Sisense Support.
