SYMPTOM
Reports executed from a 2-tier project source on the Intelligence Server machine return errors or different values when compared to a 3-tier connection to the Intelligence Server. The 2-tier project source and the server definition are confirmed to be pointing to the same metadata.
CAUSE
Two DSNs with the same name but different configuration exist on the Intelligence Server machine. One resides in the User data sources and the other in the System data sources under the ODBC Data Source Administration as shown below:
The database instance will point to different DSN in 2-tier and 3-tier even if the configuration is the same.
When connecting in 2-tier, project sources can see DSNs defined in the User and System DSN. If two DSNs are named the same as shown in the example above only the User DSN will be shown as available for the Database Instance Configuration. 3-tier project sources will only see System DSN in the Database Instance Configuration
ACTION
Delete or rename the User DSN to avoid the conflict. Strategy recommends the use of the Connectivity Configuration Wizard to create the DSNs correctly. By default the wizard will place the objects in the System DSN.
