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

KB18120: ‘Driver’s SQLAllocHandle on SQL_HANDLE_ENV failed’ error is given when trying to connect to MicroStrategy Developer 9.4.x - 10.x.


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This technical note describes an error that occurs when trying to connect to the Intelligence Server.

SYMPTOM:
When any user tries to connect to Strategy Intelligence Server via Strategy Developer, including the Strategy 'Administrator' user, the following error occurs:
 

ka02R000000kW9kQAE_0EM440000002C4J.jpeg

 


'QueryEngine encountered error: Connect Failed. Error type: Odbc error. Odbc operation attempted: SQLDriverConnect. Driver's SQLAllocHandle on SQL_HANDLE_ENV failed
 Error in Process of method Component: QueryEngineServer, Project XXXX, Job 68, Error Code =-2147212544'

 
Another symptom includes that if the user tries to connect to the metadata via Strategy ODBC Test Tool, then the following error occurs:
 

ka02R000000kW9kQAE_0EM440000002C4H.jpeg

 


'Error connecting to DSN: XXXXX
 Connect Failed. Error type: Odbc error. Odbc operation attempted:
 SQLDriverConnect. Driver's SQLAllocHandle on SQL_HANDLE_ENV failed.'

 
CAUSE:
One of the causes for this issue is that the Strategy Intelligence Server is a Universal installation that resides on a UNIX operating system and there is a missing entry for an ODBC driver instance in the Strategy odbc.sh file. This ODBC driver instance is in turn used by a data source name (DSN) to connect to the metadata. Since this entry is missing along with its respective configuration, Strategy Developer and Strategy ODBC Test Tool cannot connect to the metadata when using a data source name (DSN) that uses this ODBC driver.
 
Note: The Strategy odbc.sh file is located at <HOME_PATH>/env, where <HOME_PATH> is the directory specified as the Home Directory during the installation of Strategy Intelligence Server Universal.
 
ACTION:
The user needs to manually add the entry for the ODBC driver instance and its respective configuration relative to the database type that the user wants to connect to in the Strategy odbc.sh file. After the entry has been added the Strategy Intelligence Server needs to be restarted. Once these steps have been performed, the user will now be able to connect to the metadata via Strategy Developer or Strategy ODBC Test Tool.
 


Comment

0 comments

Details

Knowledge Article

Published:

May 1, 2017

Last Updated:

May 1, 2017