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

KB18847: ‘Key is not unique in collection’ error occurs when trying to modify or create a Database Instance in MicroStrategy Desktop 9.4.1 - Developer 10.x in 3-tier pointing to a MicroStrategy Intelligence Server Universal running on UNIX/Linux


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This article describes error ‘Key is not unique in collection’ when trying to modify or create a Database Instance in MicroStrategy Desktop 9.4.1 - Developer 10.x in 3-tier pointing to a MicroStrategy Intelligence Server Universal running on UNIX/Linux

SYMPTOM:
In Strategy Desktop 9.4.1 - Developer 10.x, the following error occurs when trying to modify or create a Database Connection object from the Database Instances editor, as shown below:
 

ka02R000000kbkuQAA_0EM440000002EpZ.jpeg

 
'Key is not unique in collection.'
This error only occurs when using a 3-tier project source that is pointing to a Strategy Intelligence Server Universal running on UNIX/Linux.
 
CAUSE:
The error occurs because the ODBC.ini file, which stores all of the data source name connection information, has too many connections listed or is corrupted.
 
ACTION:
Edit the ODBC.ini file in the HOME directory where Strategy Intelligence Universal was installed. Clean up the file by removing all of the connections that are no longer required. After saving the file, restart the Strategy Intelligence Server Universal, and this will reload the information in the ODBC.ini file.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 9, 2017

Last Updated:

June 9, 2017