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

KB422055: "Data source name not found and no default driver specified" error occurs when attempting to create DSNLess database connection to a MS Access database on a shared location using MicroStrategy Web data import 9.3.x and above


Community Admin

• Strategy


DESCRIPTION
 
When using Strategy Web Data Import functionality in Strategy 9.3.1 or above, in order to connect to a Microsoft Access database located in a shared folder on a network location, users receive the following error message when they attempt to connect to the database instance created:
 

ka04W000000OaheQAC_0EM440000002HJW.png

 
 


Database error <5>: Connect failed. %0d%0aError type: Odbc error. Odbc operation attempted: SQLDriverConnect. Data source name not found and no default driver specified

 
 
STEPS TO REPRODUCE
 
1. Place MS Access database into shared folder that is accessible by Strategy Intelligence Server.
 

ka04W000000OaheQAC_0EM440000002HJY.png

 
2. In Strategy Web open the Data Import Wizard, then select database and click the icon "New Connection".
 

ka04W000000OaheQAC_0EM440000002HJV.png

 
3. Complete the required database connection information and provide the path to the shared location where the Access database has been stored.
 

ka04W000000OaheQAC_0EM440000002HJS.png

 
4. Attempt accessing the newly created database connection and observe the error message.
 

ka04W000000OaheQAC_0EM440000002HJX.png

 
 
CAUSE
 
This is a known issue with Strategy 9.3.1. and above.
 
ACTION
 
Contact Strategy Technical Support for an update on this issue.
 
 
WORKAROUND
 
This issue only affects shared locations that are not on the Intelligence Server machine itself. To work around the issue, share a folder on the Intelligence Server machine and copy the Access database to that location before creating a new database connection.
 
Alternatively, an administrator user can create a new DSN on the Intelligence Server machine pointing to the Access MD on the shared location using Connectivity Wizard and Strategy Developer.
 
 This issue is being tracked by internal reference number 821403. 
KB422055


Comment

0 comments

Details

Knowledge Article

Published:

May 16, 2017

Last Updated:

January 1, 2019