IDT Multi-source excel universe

[Former Member]

Hi All,

I am trying to create a universe based on excel spreadsheets. There are 3 excel spreadsheets, E1 and E2 are in folder A and E3 is in folder B. I am creating this universe as multisource universe. I created 2 odbc connections. Connection 1 using folder A spreadsheets and Connection 2 using folder B spreadsheets.

Connection in the universe works fine. If I create a data foundation using one connection it works fine but when I create data foundation using multi source, it gives error as:

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.

What is the issue?How do I resolve this?

Thanks,

Nisha

[former_member4998]

Hi

To fix the issue you need create DSN in you local machine

and to access the universe and create report you need to maintain DSN on BO servers, once the DSN is maintained.

Basis team /BO Admin team have access to add DSN on BO servers.

[Former Member]

Hi Nisha,

Error: [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified.

- This error message appears because we don’t have system DSN on local
machine.

- To resolve this error message create the identical system DSN on both server machine and client machine.

- Now you can use this System DSN in Information Design tool.

For more information regarding Universe on top of Excel you can review following link :

http://scn.sap.com/thread/1882235

Regards,

Veer S.

[Former Member]

Hi Nisha,

Please review KBA 1828466 - How to Create a Universe Based on MS Office Files (Excel, Access) in BI 4.0 to check whether the configuration has been done correctly or not.

Regards,

Manpreet

[Former Member]

I am not able to access this link. I don't have a smp account.

[Former Member]

Hi Nisha,

Following is the content of the KBA:-

Symptom

When trying to create a universe based on Microsoft Office files (Excel,
Access, etc), the following error may occur:

The specified DSN contains an architecture mismatch between the Driver and Application

Environment

SAP BusinessObjects Business Intelligence 4.0

Cause

The BI 4.0 client tools (UDT, IDT, WebI Rich Client) are 32-bit tools and so
need the 32-bit MS Office ODBC drivers.

The BI 4.0 servers are 64-bit and so need the 64-bit MS Office ODBC
drivers.

However, the 32-bit and 64-bit versions of Microsoft's 2010 Office ODBC
drivers cannot both be installed on the same machine at the same time.

NOTE
Other databases that
do not support having both the 32-bit and 64-bit drivers installed at the same
time:

MySQL

Resolution

The 64-bit ODBC drivers must be installed on the BI server. A dedicated
client machine must be available for the 32-bit ODBC drivers. Once the client
machine has created the necessary connections and universes, the Launchpad WebI
clients as well as the WebI Rich Client can be used to create, edit, and view
reports.

Download the 32-bit and 64-bit MS Office ODBC drivers from Microsoft from
here:  Microsoft Access Database Engine 2010 Redistributable

On the BI Server

1. If necessary, install the 64-bit Office ODBC drivers.
2. Create the
necessary 64-bit ODBC DSN's. There should be one for each of the files used as a
datasource.

On the Separate Client
Machine

1. Install the 32-bit Office ODBC drivers. This requires any 64-bit Office
drivers to be uninstalled - this include MS Office 2010 itself.
2. Create the
necessary 32-bit DSN's. Make sure they're named exactly the same as the 64-bit
ones on the server.

Note: Be sure the 32-bit DSN's point to the same exact files that the
64-bit server ODBC DSN's do. This prevents having to use multiple copies of the
source files, which can lead to data synchronization problems.

3. Use the IDT to create the connections and universes. For details on
creating connections, universes and multisource universes, please see the IDT User Guide.
4. Publish the connections and universes to
the repository.

Create the Report

Once the connections and universes are published to the BI server repository,
any of the WebI clients can access them to create reports.