cancel
Showing results for 
Search instead for 
Did you mean: 

ODBC error - DSN contains an architecture mismatch between the Driver and Application

florencialimongi
Participant
0 Kudos

Hi,

I'm getting the following error when trying to create a webi report:

"ODBC Driver Manager

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

IES 10901"

The steps followed are:

1. I've converted the eFashion universe from unv to unx

2. created a unx connection to MS Access 2010 ==> ODBC

3. created a Data Foundation table, select two tables, connect them with the ID, select primary key, and check integrity

4. create a semantic layer

5. check integrity

6. published the connection

7. change the connection of the Data Foundation to the published one

8. check integrity

9. publish the semantic layer

10. enter Platform BI

11. create a webi with the universe created in the previous steps

12. create a query and refresh it.

The Error arose. (see picture)

We have Bo 4.0

ODBC 64 bit (deleted it and created it again)

Any idea what i'm missing?

Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

You do not have a 64bit driver or DSN on BI4 server with the samename as in client machine.

install the drivers, create a dsn, it will work.


Thanks,

Avinash

florencialimongi
Participant
0 Kudos

Thanks all for your responses.

I read the links, but I can't use the 32 bits ODBC because the machine runs on 64 bit.

I'm using 64 bit both in the server and in the client, and same driver, same ODBC, same name.

I have other eFashion universes pointed to the database taht are working ok.

Maybe it's a universe problem? what could it be happening?

Henry_Banks
Product and Topic Expert
Product and Topic Expert
0 Kudos

please read the links again .  there are 2 places where you can maintain DSN, even on a 64 bit platform.

I'd recommending checking this article :

Note 1803970 - Errors: IES 10901, WIS 10901 and "The specified DSN contains an architecture mismatch between the Driver and Application" if generating Web Intelligence report in SAP BusinessObjects BI Platform 4.0

Regards,

H

florencialimongi
Participant
0 Kudos

Hi Henry,

Thanks for yor reply.

Do you have the link to the article?

former_member188911
Active Contributor
0 Kudos

Hi Florencia

the link is http://service.sap.com/sap/support/notes/1803970 you need a S user account

Resolution


  1. Run <WINDOWS_INSTALL_DIR>\sysWOW64\odbcad32.exe, not
    <WINDOWS_INSTALL_DIR>\system32\odbcad32.exe
  2. Create the other System DSN and point it to the Data provider i.e. "SBOP DSN
    64-bit"
  3. Run Information Design Tool as the Administrator
  4. Change the Data Source Name in the Data foundation's connection into "SBOP
    DSN 64-bit" has been created
  5. Ensure it works by clicking Test Connection, Click Finish
  6. Click Save to save the connection change
  7. Publish the connection to the repository overwriting the existing shortcut,
    that the Data foundation uses
  8. Double click the Data foundation, select Connections tab, click Change
    connection
  9. In the window has opened set checkmark in the connection's shortcut, click
    OK
  10. Click Save to save the Data foundation change
  11. Publish the UNX Universe to the repository

Note 1: In a Microsoft Windows Server 2008

environment the following rules are applicable:


  • 32-bit System DSNs do not show up in the 64-bit ODBC Data Sources
    Administrator (<WINDOWS_INSTALL_DIR>\sysWOW64\odbcad32.exe) and when
    64-bit client applications ask for all available DSNs, the 32-bit DSNs cannot be
    used by a 64-bit client application and ODBC Data Sources Administrator
  • 64-bit System DSNs do not show up in the 32-bit ODBC Administrator
    (<WINDOWS_INSTALL_DIR>\system32\odbcad32.exe) and when the 32-bit SAP
    BusinessObjects BI Platform 4.0 Сlient applications ask for all available DSNs,
    the 64-bit DSNs can be used
  • 32-bit User DSNs show up in the 64-bit ODBC Data Sources Administrator
    (<WINDOWS_INSTALL_DIR>\sysWOW64\odbcad32.exe) and when the 32-bit SAP
    BusinessObjects BI Platform 4.0 Сlient applications ask for all available DSNs

Note 2 from MSDN: To manage a data source that connects to a
32-bit driver under 64-bit platform, use c:\windows\sysWOW64\odbcad32.exe. To
manage a data source that connects to a 64-bit driver, use
c:\windows\system32\odbcad32.exe. If you use the 64-bit odbcad32.exe to
configure or remove a DSN that connects to a 32-bit driver you will receive this
message.

Answers (2)

Answers (2)

Former Member
0 Kudos

On the server it uses 64 bit ODBC DSN format so you should create 64 bit ODBC with the same name as your local 32 bit ODBC.

If client and server running on same machine make sure same ODBC exists in 32 bit and 64 bit drivers.

-- Gopal

florencialimongi
Participant
0 Kudos

Hi,

We're using a relational connection with OLAP structure (star): (eFashion universe)

The steps followed were:

1. Database relational oracle.

2. Did a relational connection

3. Used an STAR scheme as a un.

Can i visualize this in explorer?

Does it work this way? or do we have to use an relational scheme?

former_member189638
Active Contributor
0 Kudos

Try creating another ODBC System DSN with 64 bit driver on the BI Server with the same name used for 32bit driver

florencialimongi
Participant
0 Kudos

Hi Rakesh, thanks for your reply.

We've never used a 32 bit driver.

We have created another ODBC System DSN with 64 bit driver on the BI Server with the same name but we still get the same error.

former_member189638
Active Contributor
0 Kudos

I think that is the issue then . You are using 64 bit trying to connect 32 bit.

Below link might help you. 

http://msdn.microsoft.com/en-us/library/ms712362(v=vs.85).aspx

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