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

KB19443: “Connection mapping is ambiguous for the user. Error Code= -2147204459.” error occurs when executing a report in MicroStrategy


Community Admin

• Strategy


SYMPTOM:
When running a in Strategy Web the following error occurs:

ka04W000000OeZoQAK_0EM440000002BEi.gif


Error in report results

Your request could not be processed. Please try again. If the problem persists, contact the Administrator.

(QueryEngine encountered error: DSSDatabaseConnectionMap: Connection mapping is ambiguous for the user. Error in Process method of Component: QueryEngineServer, Project XXX, Job XXX, Error Code= -2147204459.)

 

A similar error appears when running the report in Strategy Developer:

ka04W000000OeZoQAK_0EM440000002BEq.jpeg

 


Status: Execution failed

Error: SQL Generation Complete. QueryEngine encountered error: DSSDatabaseConnectionMap: Connection mapping is ambiguous for the user. Error in Process method of Component: QueryEngineServer, Project xxx, Job xxx, Error Code=-2147304359.


 
This error can even occur when sending a report using Strategy Narrowcast Server. The following error can be found in the System Message Viewer or DELog file:

Information source got result for with error: Report execution failed for segment job ServiceExecutionID with error: -2147207171 - QueryEngine encountered error: DSSDatabaseConnectionMap: Connection mapping is ambiguous for the user. Error in Process method of Component: QueryEngineServer, Project XXX, Job XXX, Error Code= -2147204459.

 
CAUSE:
The user executing the report belongs to two or more user groups, each with a different connection mapping pointing to different database login objects. At execution time the Query Engine does not know which of the connection mappings should be used so it returns an errors.

ka04W000000OeZoQAK_0EM440000002BEj.jpeg
ka04W000000OeZoQAK_0EM440000002NZN.jpeg

 
ACTION:
There are three methods for resolving this issue:

  • Edit the user and make sure that they belong to only 1 of the groups which has a connection mapping defined.
ka04W000000OeZoQAK_0EM440000002BEn.jpeg
  • Edit the connection mappings and remove all but one of the groups.
ka04W000000OeZoQAK_0EM440000002BEr.jpeg
  • Explicitly add the user to the connection mapping.
ka04W000000OeZoQAK_0EM440000002BEl.jpeg

Comment

0 comments

Details

Knowledge Article

Published:

June 2, 2017

Last Updated:

June 2, 2017