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

KB44110: "Data source name is longer than 32 characters" error message appears in the Microsoft ODBC Administrator for a DSN that was created in MicroStrategy Connectivity Wizard 9.x and 10.x.


Community Admin

• Strategy


The MicroStrategy Connectivity Wizard does not limit the number of characters in a data source name for certain drivers. However, the Microsoft ODBC Data Source Administrator is not compatible with DSNs that are longer than 32 characters.

SYMPTOM:
In Microsoft ODBC Data Source Administrator, data source names created in Strategy Connectivity Wizard may not be visible for removal/deletion. When attempting to open the System DSN tab, an error appears referencing that DSN:
 

ka04W000001MKvwQAG_0EM440000002HLK.png

 


"Data source name is longer than 32 characters: xxxData_Source_Namexxx"  

 
CAUSE:
The Strategy Connectivity Wizard does not limit the number of characters in a data source name for certain drivers. However, the Microsoft ODBC Data Source Administrator is not compatible with DSNs that are longer than 32 characters.
 
ACTION:
The name of the DSN needs to be manually shortened to less than 32 characters.
On Unix/Linux machine, the data source information is recorded in the ODBC.ini file, which resides in Strategy install directory. On Windows machines, it is kept in a register file:
For 32 bit system, the path is:
HKEY_LOCAL_MACHINE\SFTWARE\ODBC\ODBC.INI\ODBC Data Sources
 
For 64 bit system, the path is:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources
All ODBC DSNs are stored in this registry folder. Right-click on the problematic DSN and select 'Modify', then adjust the listed Value name to anything shorter than 32 characters. Hit 'OK'. The user will now be able to access and remove this DSN using the Microsoft ODBC Data Source Administrator without error.
 
Registry Modification:
WARNING:
Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of Microsoft Windows NT. Any edit of the registry is done at the user`s own risk. Since these are user-initiated changes, they are not covered by any Strategy warranty. If using Microsoft Windows NT, the user should backup the registry and/or update an Emergency Repair Disk (ERD) prior to alterations.


Comment

0 comments

Details

Knowledge Article

Published:

April 3, 2017

Last Updated:

April 3, 2017