EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB482886: Error message "The connection to the database failed." appears when users open Dossier (Connect Live) or republish dataset (In-Memory) after uploading mstr file


Lisha Ma

Senior Cloud Support Engineer III • MicroStrategy


Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
SYMPTOM:
After importing mstr file, when users open the Dossier (Connect Live) or republish dataset (In-Memory) in Dossier, the error message appears as below.


The connection to the database failed. Please check the connectivity information and try again

 

ka0PW0000001JWHYA2_0EM44000000gO3h.jpeg

CAUSE:
Opening Dossier (Connect Live) or republishing dataset (In-Memory) is a process of setting up connections to data sources and fetching data, while Strategy converts the connection strings when importing .mstr files, during when there are some custom parameters discarded. The most common method to handle these failures is to check the connection string of DB instances.
Here's a typical example of Impala:
When users import a .mstr file created from an SSL-Enabled Impala source.
The original connection string should be like below.


DRIVER=Strategy Impala ODBC Driver Client;ALLOWHOSTNAMECNMISMATCH=1;ALLOWSELFSIGNEDSERVERCERT=1;AUTHMECH=3;AUTORECONNECT=1;CHECKCERTREVOCATION=1;DESCRIPTION=Simba Impala Driver;DELEGATEKRBCREDS=0;ENABLESIMULATEDTRANSACTIONS=0;ENCRYPTEDPWD=******;HOST=******;KRBFQDN=_HOST;KRBSERVICENAME=impala;PORT=21050;ROWSFETCHEDPERBLOCK=10000;SSL=1;SCHEMA=default;SOCKETTIMEOUT=30;STRINGCOLUMNLENGTH=32767;TSASLTRANSPORTBUFSIZE=1000;TRUSTEDCERTS=C:\Program Files\MicroStrategy\Workstation\odbc\Impala\cacerts.pem; USEKEYTAB=0;USENATIVEQUERY=0;USEONLYSSPI=1;USESASL=1;USESQLUNICODETYPES=0;USESYSTEMTRUSTSTORE=0;

After Strategy converting the connection string, it is as below.

DRIVER=Strategy Impala ODBC Driver;AUTHMECH=3;KRBFQDN=_HOST;KRBSERVICENAME=impala;SCHEMA=default;HOST=******;PORT=21050;

Key parameters "ALLOWHOSTNAMECNMISMATCH","ALLOWSELFSIGNEDSERVERCERT","SSL" and"TRUSTEDCERTS" are discarded because Strategy doesn't set these custom settings on behalf of customers.
ACTION:
Edit the data souse and add the connection string manually.

ka0PW0000001JWHYA2_0EM44000000gO3m.jpeg

 
KB482886


Comment

0 comments

Details

Knowledge Article

Published:

February 21, 2019

Last Updated:

March 21, 2024