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

KB42483: "Data source name not found and no default driver specified Connection String: DSN=xxx;UID=xxx" error appears when running a FreeForm SQL report after migrating it from a project with a different primary DB Instance in Developer 9.4.x-10.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This knowledge base article documents why "Data source name not found and no default driver specified Connection String: DSN=xxx;UID=xxx" error appears when running a FreeForm SQL report after migrating it from a project with a different primary DB Instance in Developer 9.4.x-10.x

SYMPTOM:
Consider the scenario in which a FreeForm SQL report is set up in an environment A.  It is configured to use database instance A (also set as the project primary DB instance) which in turn uses DSN A.
Now assume that the FFSQL report is migrated to environment B using Object Manager.  Environment B uses DB instance B as it's project primary, which in turn uses DSN B.  After the migration, the FFSQL report is edited to ensure that DB Instance B is selected.  The report is saved, closed, and then run, but the error message "Data source name not found and no default driver specified Connection String: DSN=A;UID=xxxx" appears.
Note that the error message states that the report is trying to use DSN A even though the FFSQL report DB Instance was changed to DB Instance B.
 
CAUSE:
This can be cause by performing a FFSQL report migration without updating the schema in the destination project afterward.
 
ACTION:
Update the schema in the destination project and re-edit the FFSQL report to ensure that it is using DB Instance B.  Save and close the report and run again.


Comment

0 comments

Details

Knowledge Article

Published:

June 6, 2017

Last Updated:

June 6, 2017