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

KB292975: "The specified DSN contains an architecture mismatch between the Driver and Application" error appears in MicroStrategy Repository Translation Wizard 10.0 and above.


Community Admin

• Strategy


"The specified DSN contains an architecture mismatch between the Driver and Application" error appears in MicroStrategy Repository Translation Wizard 10.0 and above.

SUMMARY:
This document describes an issue that occurs in Strategy Repository Translation Wizard 10.0 and above, where an error is thrown when selecting the Data Source Name to export or import the translations from.
 
SYMPTOM:
When selecting the Data Source Name to connect to the Translation Database, the following error appears in Strategy Repository Translation Wizard 10.0 and above:

ka04W000000OdVdQAK_0EM440000002C22.jpeg

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
STEPS TO REPRODUCE:

  1. Open Strategy Repository Translation Wizard.
  2. Select the Project Source Name and specify the Strategy User.
  3. Choose the project and the languages to be exported.
  4. Select the Data Source Name to connect to the Translation Database. In the drop-down list, only 64-bit DSNs will appear as well as the connections created to Access databases.This is due to the fact that Strategy drivers are all 64-bits starting in version 10.0.
  5. When pressing the "Connect" or "Next" buttons, the error will appear.

 
CAUSE:
This is a known issue in Strategy Repository Translation Wizard 10.0 and higher, which is currently under investigation.
 
ACTION:
Contact Strategy Technical Support for an update on the status of this issue.
 
WORKAROUND:
There are two possible workarounds that can be applied:

  1. Use an Access database to import/export the translations.
  2. Create two identical Data Source Names to connect to the translation database using both the 32-bit and 64-bit drivers.

 
This issue internal reference number is DE19816


Comment

0 comments

Details

Knowledge Article

Published:

April 13, 2017

Last Updated:

April 13, 2017