1791522 - Visual Intelligence: Error "Could not validate the query" while creating document on a BI universe.

• An error is thrown when trying to preview or acquire data from an MS Access based universe.
• Error: "Could not validate the query. Database error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified. (IES 10901)"

• The issue is not seen when using the sample universe 'efashion.unv' which is based on SQL Server.

• SAP Visual Intelligence 1.0 SP07 
• BI Platform 4.0 SP04 on Windows
• Relational RDBMS database via ODBC

1. Create "New document"
2. Select "Universe"
3. Enter "Credentials"
4. Click "Connect"
5. Select the Universe from list, and click "Acquire"

• The middleware driver used by the ConnectionServer hasn't been installed on the BIPlatform, and/or the ODBC datasource name (DSN) hasn't been created on the BI server.

• Typically, on a BI Client Tools workstation, 32-bit middleware drivers are installed, and 32-bit ODBC Data Source Names (DSN) are defined to point to a database. Universe authors do this to publish connections from Universe Designer or Information Design Tool to the CMS repository.
• To avoid an architecture mismatch on the BI 4.0 Platform server, both 32-bit DSN (%WINDIR%\SysWOW64\odbcad32.exe) and 64-bit DSN (%WINDIR%\System32\odbcad32.exe) need to be administered - in duplicate, with the same DSN name - to enable the dynamic switching between 32-bit and 64-bit Connection Server libraries (i.e. 'ConnectionServer32' service for XI3.1 Universe Designer .UNV; and 'ConnectionServer' service for Information Design Tool 4.0 .UNX, respectively) in order to make a single data source work seamlessly across all BI Client Tools and BI Platform Server processes. (i.e. WebI Rich Client Desktop application vs. BILaunchPad WebI applet.)
• In the case of Microsoft Access drivers, these can be downloaded from here: http://www.microsoft.com/en-us/download/details.aspx?id=13255

• Please note that other local IT infrastructure restrictions between client and server, such as firewalls, proxy settings and port forwarding can also cause similar errors.

, KBA , BI-LUM-DIS , Lumira Desktop/Discovery , Problem