Architecture Mismatch

Hi Experts,
I have Windows 7 OS which is 64 bit OS. I trying to make a connectivity b/w Oracle & crystal 11.5 I am getting this "architecture mismatch between ODBC driver and application"
How do I resolve this issue?
O/S Windows 7 64-bit
Oracle 11g 64-bit on Windows 7
Crystal 11.5
Regs

Same way you did if for the 64 bit ODBC Administrator only go into the 32 bit ODBC administrator to create a System DSN.
from the start search line type in odbc and it should list both, if XP then go into the 32 bit Control panel
Also requires the 32 bit Client for your DB to be installed.
Don

Similar Messages

64-bit ColdFusion 9 ODBC drivers confusion? (architecture mismatch)

Hi all - I'm having problems setting up ColdFusion ODBC sources in a pure 64-bit environment. Server specs:
Windows 2008 R2 (64-bit)
ColdFusion 9.01 (251028) Enterprise, 64-bit
I have 64-bit ODBC drivers for all of my database sources:
64-bit SQL Server (bundled with Windows 2008 R2)
64-bit MS Access 2010 (with 64-bit Access ODBC driver from Office 2010 64-bit install)
64-bit ODBC drivers for Sybase SQL Anywhere 11 (from SyBase)
Using the (64-bit) ODBC Administrator, I can create system DSNs and they test out perfectly. (From my test Access database, I can use these DSNs to pull data from SQL Server and from SQL Anywhere.) Since this is working, I'm pretty confident that my drivers are all 64-bit and that everything is happy.
Now for ColdFusion...
When I try to create a new data source in the ColdFusion Administrator and I use, the "ODBC Socket" option, I am presented with a drop-down list of my 64-bit ODBC system DSNs (good!), but whenever I select one and save, I invariably get an "architecture mismatch" error like below:
Connection verification failed for data source: MSSQLtestDatabase
java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application
The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application
I am well aware that "architecture mismatch" errors mean that you're trying to mix 32-bit drivers with a 64-bit application (or vice-versa), but I'm pretty sure that everything in my environment is 64-bit.
As a further test, I created a few 32-bit ODBC system DSNs and the ColdFusion Administrator does not present them as options in the drop-down list of ODBC DSNs (good!). So, it seems like the Administrator is smart enough to show only the 64-bit DSNs, but whenever you try to connect to one, it gets confused and kicks up an "architecture mismatch" error.
So is there any obvious configuration error here? Is there a 32-bit subcomponent to ColdFusion (JDBC, etc.) that's confusing things? (I ran the ColdFusion_9_WWE_win64.exe setup downloaded from Adobe's site.) Is 64-bit ColdFusion ready for prime time? Any suggestions would be greatly appreciated. Thanks, Joe

OK, just did a little Googling for you about this, Josie (and others). There seem to be a few alternative solutions, each with pros and cons.
The easiest, though, may be to simply use the 32-bit (instead of default 64bit) ODBC control panel, and then again use the MS Access driver in the CF Admin (not the ODBC socket one) to point to that. This is discussed here:
http://www.cfexecute.com/post/access-dsns-in-64bit-coldfusion
There's also a little more that may help at the bottom of this:
http://www.zidsoft.com/x64.html
MS also covers the topic here:
http://msdn.microsoft.com/en-us/library/ms712362%28VS.85%29.aspx
Other CF-specific solutions include:
- run CF instead in 32-bit mode (even on the 64-bit machine). See discussion at http://www.houseoffusion.com/groups/cf-talk/thread.cfm/threadid:60467
- if you have 2 boxes available, you could run CF in 32-bit mode on one box (just for providing access to the 32-bit Access driver), then "proxy" the DSN setup from the 64-bit CF machine to access the DSN on the 32-bit machine (See http://www.coldfusionmuse.com/index.cfm/2009/4/7/MS.Access.Proxy)
- get an alternative jdbc driver for Access (HXTT), mentioned in the threads above
- did you happen to try the "microsoft access with Unicode" driver option in the CFAdmin? That is quite different from the one that is not "with Unicode", so worth a try if nothing else works for you.
Let us know if any of these suit you.
Also, I appreciate the annoyance of those who would think this should "just work" without workarounds. I think I have clarification there.
First, the CF9 System Requirements page is unclear on this. While its systems support matrix lists 32 and 64 but windows (among others), those don't list what DBs are supported on each. Instead, there's a database support matrix at the bottom, which does indicate that Access is supported, but it doesn't break it down per OS, let alone bit-level of each OS.
But I just found a clarificaiton in a devnet article (by an Adobe engineer) that does seem to put the nail in the coffin:
"Most of the functionality and features of ColdFusion run just fine on 64-bit platforms, however, certain features like ColdFusion COM interoperability, ColdFusion Delphi interoperability, and Microsoft Access database connectivity do not work on a ColdFusion 64-bit platform. A few other features, such as ColdFusion .NET integration services and database drivers currently run in 32-bit mode." (http://www.adobe.com/devnet/coldfusion/articles/64_bit_print.html)
I think most haven't noticed this or made much of it simply because Access has been eschewed by so many for so long.
/charlie
Providing CF troubleshooting services at carehart.org/consulting
[email protected]

SSRS 2012 ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

I have a SSRS installation, I have deployed my connections to, but they fail with title message. The drivers and ODBC on the box are setup and work fine with 32 bit ODBC conn manager.
When I run or configure my connections on the site, via the browser, I get errors connecting.
I tried to find which app pool http://server/ReportServer application used, but I am not finding that, so my first ?
How do I find in IIS what app pool SSRS application is using?
I have 2008 server, running SQL 2012 V.S. 2010 and I think I need to enable my app pool to use 32 bit, but cannot figure out which one it uses? I see default set to 32 bit = true, which I thought would be it.
Can I set my SSRS project to use x86, platform? Like I did with SSIS?
If so, how? SSRS and SQL 2012 somewhat new for me. Thanks
Developer MS Reporting Services

Hi DCady,
To manage a data source that connects to a 32-bit driver under 64-bit platform, we use C:\Windows\SysWOW64\odbcad32.exe. To manage a data source that connects to a 64-bit driver, we use C:\Windows\System32\odbcad32.exe.
Generally, if we use the 64-bit odbcad32.exe (C:\Windows\System32\odbcad32.exe) to configure or remove a DSN that connects to a 32-bit driver, for example, Driver do Microsoft Access (*.mdb), we will receive the following error message:
The specified DSN contains an architecture mismatch between the Driver and Application
To resolve this error, we need to use the 32-bit odbcad32.exe (C:\Windows\SysWOW64\odbacad32.exe) to configure or remove the DSN.
Besides, please make sure there are no DSN using the same name in both 64-bit and 32-bit ODBC Data Source Administrator.
Reference:
Managing Data Sources
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

MySQL ODBC driver (32 bit) linked server, architecture mismatch

Hello,
I am trying to create a linked server in SQL 2012 Management Studio with a MySQL external server. I have used the 32bit ODBC driver as instructed by the developer, following this rule:
To manage a data source that connects to a 32-bit driver under 64-bit platform, use c:\windows\sysWOW64\odbcad32.exe.
My connection is fine using the ODBC connector, but when I try to create the linked server I get an architecture mismatch error: The specified DSN contains an architecture mismatch between the Driver and Application Error 7303.
Can someone help?
Best regards
Kostas
Kostas Backas-Systemgraph Technologies

Hello,
What's the bit verison of the SQL Server ?
Based on your description, you create a DSN connect to MySQL database with 32 bit MySQL ODBC driver under 32bit ODBC Administrator tool (sysWOW64\odbcad32.exe).
When you create linked server on SQL Server instance, it will use 64 bit Microsoft OLE DB Provider for ODBC Drivers if the bit version of SQL Server is 64 bit. That may cause the error you received. In that case, please download 64bit MySQL ODBC driver and
create a DSN with 64 bit ODBC Administrator tool.
Reference: http://dev.mysql.com/downloads/connector/odbc/
If I have any misunderstanding, please correct me.
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Architecture Mismatch IM014

Architecture Mismatch when connecting a 64Bit ODBC (.accdb file) to crystal report for visual studio 2013 database expert.

Hello,
For issues regarding crystal report, i suggest that you could post it to:
http://scn.sap.com/community/crystal-reports
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Architecture mismatch between ODBC driver and application

Hi,
I have Windows 2008 server R2 OS which is 64 bit OS. I have created an SQL Server ODBC connections for my CMC database. I am trying to install Crystal Reports Server 2008 V1 SP3 but I am getting this "architecture mismatch between ODBC driver and application" error while choosing the ODBC datasource for CMS.
I thought CRS 2008 version would easly be installed on Windows 2008 server as it mentioned on the installation guide.
How do I resolve this issue?

Moved to BOE Admin forum.
CRS 2008 is a 32 bit app so all attachments, Printers, DB clients, etc. must all be 32 bit or support 32 bit applications.
Use the 32 ODBC administrator in \windows\syswow64 folder.
Thank you
Don

UCCX 10.1 - Linked Server - Copying HR data to external SQL Server for reporting

I have a customer that is migrating from UCCX 7 to UCCX 10. They currently have a 2008 SQL Server R2 that they use for custom reports. They have a package that runs nightly to copy relevant data from UCCX 7 to the their server and then run reports daily against that database.   Pretty easy when everything is in MS SQL.  My plan was to set up a linked server in SQL 2008 to the UCCX server. This would allow me to easily run a query against Informix and move the data over as before. However, I am having problems adding the linked server.
I have installed the Informix drivers (both 32 and 64 bit) during the troubleshooting.
The DSN is created and connects to UCCX just fine.
When I attempt to add the linked server using 64 bit driver DSN I get the following:
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "UCCX101".
OLE DB provider "MSDASQL" for linked server "UCCX101" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "UCCX101" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "UCCX101" returned message "[Informix][Informix ODBC Driver][-11302] Insufficient Connection information was supplied". (.Net SqlClient Data Provider)
When I attempt to add the linked server using the 32 bit driver DSN I get the following:
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "32UCCX101".
OLE DB provider "MSDASQL" for linked server "32UCCX101" returned message "[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application". (Microsoft SQL Server, Error: 7303)
It appears to me there is a 32/64 bit conflict no matter route I go.
Can anyone tell me what I am missing?
Is there a better approach to take to achieve the ultimate goal?
Any suggestions are greatly appreciated.
TIA
John

I have created linked servers on an SQL2K box that points back to CCX. First off, you have to set the password for the UCCX HR user to some known value.
exec sp_dropserver 'fonccx9_01', 'droplogins'
EXEC sp_addlinkedserver
@server='fonccx9_01', -- Name of the Linked Server, when it is created.
@srvproduct='Microsoft OLE DB Provider for ODBC', -- OLE DB Provider.
@provider='MSDASQL', -- Provider_name.
@datasrc ='fonccx9-01', -- DSN Name of the ODBC Data Source.
@provstr= -- ODBC Connection String.
'Driver={IBM Informix ODBC};Server=fonccx9_01_uccx;Database=db_cra; Uid=uccxhruser; Pwd=Some-Password;'
EXEC sp_addlinkedsrvlogin
    @rmtsrvname = 'fonccx9_01',
    @useself = 'FALSE',
    @rmtuser = 'uccxhruser',
    @rmtpassword = 'Some-Password'
Note that the server name is "fonccx9-01", but the dash is an illegal character in the server name, so you have to change that to an underscore. You still have to manually build the ODBC data source on the box where you are trying to create the linked server.

Re: 32 Bit ODBC Driver for Oracle 11g 11.2.0.1.0

Hi,
Were you able to resolve the problem with these troubleshooting measures ?
Please let me know since i am facing similar issues like yours.
I am using a Windows 7 64 bit and from QTP installed on this machine , i am trying to connect to Oracle database.
Now initially i installed a 64 bit ODBC for Oracle . But when i did that and ran the Script below :
Set objDatabase = CreateObject("ADODB.Connection")
Set rs=createobject("adodb.recordset")
objDatabase.open "DRIVER={Oracle in OraClient11g_home1} ; DATA SOURCE=Oracle; SERVER= xyz ; DATABASE=abc1; UID=abc ; PASSWORD= abc123;"
rs.Open "select * from tablename", objDatabase
'result1 = objDatabase.Execute("select * from tablename")
'msgbox result1
Do while not rs.eof
print rs.fields("columnname")
rs.movenext
Loop
print rs.fields("columnname")
it gives me an error
“[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application”
So i am assuming that i need to install the 32 bit ODBC drivers for Oracle as well in addition to the already installed 64 bit drivers ..
Any thoughts on this ?

64 bit apps need 64 bit Oracle client software.
32 bit apps need 32 bit Oracle client software.
You should be able to tell the bit-ness of the app by checking the Process tab in task manager to see if it has *32 next to it.
You can install both 32 bit and 64 bit Oracle client software on the same box, but you need to do it into different homes, and different oracle_base should also be used.
There isnt an Oracle client install bundle that installs both, you'll need to do each separately.
Hope it helps,
Greg

64bit CR-Enterprise wont talk with 32bit data source, 32bit IDT wont use 64bit connection for universe. How do I connect them.

Hi.
I installed the full suite of tools as I am involved with a company intended to become a partner and reseller so we are trying to get everything working.
SAP Crystal Server 2013 SP1
BusinessObjects Business Intelligence platform
SAP Crystal Reports for Enterprise
SAP HANA
SAP Crystal Reports 2013 SP1
SAP BusinessObjects Explorer
SAP Crystal Dashboard Design 2013 SP1
Crystal Server 2013 SP1 Client Tools
SAP BusinessObjects Live Office 4.1 SP1
.NET SDK
I found out that BI was needed only after I installed all the others but I installed it without problem.
My issue is that the Information Design Tool (IDT) which creates my universes successfully, and even lets me open and see the dada no problem. Is using a 32bit (ODBC connected to SQL Server 2008) data source.
However, I am unable to load the .UNX in crystal reports (CR) 2011, so I used CR Enterprise (CRE) to connect to my universe. Now when I try to open the universe I start getting the following error:
[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
When I do searches online I get very generic information relating to setting up data sources. While I believe the problem is indeed with the data source, I don't believe it is setup wrong.
When I access the universe using the IDT (which uses the 32bit version of the data source to build its connection, it wont let me use a 64bit) I can load a table under the "result objects for query #1" press refresh, I get a list of data.
When I access the same universe using CRE (which "Seems" to use a 64bit data source, but I am not sure), and follow the same process as above. I get the above error.
If I cancel the process, when CRE lists the fields for the report I can later manually map these fields to an ODBC connection. But if I have to do this what is the point of using the universes at all as the end user has full access to all the various DB's available in the data source.
Thanks in advance for any help you can provide.

On the server where Crystal Reports Server is installed, create a 64-bit ODBC connection with the same name as the 32-bit connection. CRS will then automatically use the 64-bit version of the connection.
-Dell

Fail to create an instance of Job

I try to create a data source with a BO XI 4.1 Universe.
My Universe works with WEBI but whenever I try to use it in Design Studio, I get an error message.
Caused by: com.businessobjects.dsl.services.dataprovider.DataProviderException: Fail to create an instance of Job :
    at com.businessobjects.dsl.services.dataprovider.impl.QuerySpecDataProvider.refresh(QuerySpecDataProvider.java:651)
    at com.businessobjects.dsl.services.dataprovider.impl.DataProviderServiceImpl.run(DataProviderServiceImpl.java:131)
    at com.sap.ip.bi.bics.dataaccess.resource.impl.dsl.resultset.DslResultSet.getData(DslResultSet.java:119)
    at com.sap.ip.bi.bics.dataaccess.resource.impl.dsl.query.DslQuery.getResultSet(DslQuery.java:223)
    at com.sap.ip.bi.bics.dataaccess.resource.impl.dsl.query.DslQuery.getResultSet(DslQuery.java:1)
    at com.sap.ip.bi.bics.dataaccess.provider.relational.impl.rel2queryview.resultset.RelResultSet.refresh(RelResultSet.java:132)
    at com.sap.ip.bi.bics.dataaccess.provider.relational.impl.rel2queryview.Rel2QueryView.getResultSet(Rel2QueryView.java:175)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.ResultSet.getData(ResultSet.java:571)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsResultSetManager.getResultSet(RsResultSetManager.java:234)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsResultSetManager.getResultSet(RsResultSetManager.java:168)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsResultSetManager.getResultSet(RsResultSetManager.java:56)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QueryView.getResultSet(QueryView.java:731)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.pivot.manager.PivotTableManager.checkResultSetState(PivotTableManager.java:282)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.pivot.manager.PivotTableManager.validateDataset(PivotTableManager.java:226)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.pivot.manager.PivotTableManager.buildVirtualMatrix(PivotTableManager.java:189)
    at com.sap.ip.bi.webapplications.ui.items.analysis.control.AcPivotTableExport.buildVirtualMatrix(AcPivotTableExport.java:217)
    at com.sap.ip.bi.webapplications.ui.items.analysis.control.AcPivotTableInteractive.buildUrTree(AcPivotTableInteractive.java:319)
    at com.sap.ip.bi.webapplications.ui.items.analysis.control.AcPivotTableInteractive.renderComposite(AcPivotTableInteractive.java:1231)
    at com.sap.ip.bi.zen.rt.components.crosstab.impl.CrosstabComponent.renderComponentContent(CrosstabComponent.java:535)
    at com.sap.ip.bi.ui.nonur.zen.renderer.ZenComponentOutputWriter.writeComponentOutput(ZenComponentOutputWriter.java:109)
    at com.sap.ip.bi.ui.nonur.zen.renderer.ZenComponentOutputWriter.<init>(ZenComponentOutputWriter.java:34)
    at com.sap.ip.bi.zen.rt.components.crosstab.impl.CrosstabComponent.renderComponent(CrosstabComponent.java:527)
    at com.sap.ip.bi.zen.rt.components.base.ZenUiContainer.renderChildren(ZenUiContainer.java:366)
    at com.sap.ip.bi.zen.rt.components.abslayout.impl.AbsoluteLayoutComponent.renderComponentContent(AbsoluteLayoutComponent.java:130)
    at com.sap.ip.bi.ui.nonur.zen.renderer.ZenComponentOutputWriter.writeComponentOutput(ZenComponentOutputWriter.java:109)
    at com.sap.ip.bi.ui.nonur.zen.renderer.ZenComponentOutputWriter.<init>(ZenComponentOutputWriter.java:34)
    at com.sap.ip.bi.zen.rt.components.base.ZenUiContainer.renderComponent(ZenUiContainer.java:383)
    at com.sap.ip.bi.webapplications.ui.items.UiItem.render(UiItem.java:492)
    ... 54 more
Caused by: com.sap.tools.commons.exception.NestedException: Fail to create an instance of Job :
    at com.sap.tools.commons.exception.NestedException.create(Unknown Source)
    at com.sap.sl.edp.dataprovider.relational.fetcher.AbstractRelationalFetcher.open(AbstractRelationalFetcher.java:130)
    at com.sap.sl.edp.dataprovider.relational.RelationalDataProvider.getResultNode(RelationalDataProvider.java:171)
    at com.businessobjects.dsl.services.dataprovider.impl.QuerySpecDataProvider.refresh(QuerySpecDataProvider.java:645)
    ... 81 more
Caused by: com.sap.connectivity.cs.core.CSError: Fail to create an instance of Job :
    at com.sap.connectivity.cs.remoting.conversion.ErrorHelper.newInstance(ErrorHelper.java:46)
    at com.sap.connectivity.cs.remoting.conversion.ErrorSetHelper.fetch(ErrorSetHelper.java:31)
    at com.sap.connectivity.cs.remoting.corba.proxy.CORBARepositoryJob.createRemoteJob(CORBARepositoryJob.java:93)
    at com.sap.connectivity.cs.remoting.corba.proxy.CORBARepositoryJob.<init>(CORBARepositoryJob.java:54)
    at com.sap.connectivity.cs.remoting.corba.proxy.RepositoryJob.<init>(RepositoryJob.java:39)
    at com.sap.connectivity.cs.remoting.corba.proxy.ConnectionServer.getJob(ConnectionServer.java:438)
    at com.sap.connectivity.cs.core.ConnectionServer.CreateJob(ConnectionServer.java:73)
    at com.sap.connectivity.cs.api.trace.EnvironmentLogger.CreateJob(EnvironmentLogger.java:1395)
    at com.businessobjects.mds.services.relational.Job.createSafeJob(Job.java:168)
    at com.businessobjects.mds.services.relational.Job.create(Job.java:145)
    at com.businessobjects.mds.services.relational.CsService.createJob(CsService.java:689)
    at com.sap.sl.edp.dataprovider.relational.RelationalDataProvider.createJob(RelationalDataProvider.java:219)
    at com.sap.sl.edp.dataprovider.relational.fetcher.AbstractRelationalFetcher.open(AbstractRelationalFetcher.java:93)
    ... 83 more
!ENTRY com.sap.ip.bi.web.uiitem 4 0 2014-04-03 11:06:47.992
!MESSAGE BI exception with class "BIBaseRuntimeException" and message "Error while generating HTML". See default trace for log ID "69592a5d-3033-4690-a31c-5b7a3b88bd98".
!ENTRY com.sap.ip.bi.web.runtime 4 0 2014-04-03 11:06:48.007
!MESSAGE Details of critical error in BI application added to log with ID "69592a5d-3033-4690-a31c-5b7a3b88bd98"; see SAP Notes 937697 and 948490. Context of BI application:
{VALIDATION_DATA=false, SAP_BW_NAVIGATION_CONTEXT=, DESIGN_MODE=TRUE, CHECK_POPUP_BLOCKER=, Query String (Current Browser Request)=ACCEPT=image%2Fjpeg%2C+image%2Fgif%2C+image%2Fpjpeg%2C+application%2Fx-ms-application%2C+application%2Fxaml%2Bxml%2C+application%2Fx-ms-xbap%2C+*%2F*&APPLICATION=Ad87txRJmRlPpbjl2wYeKJE&DYNAMIC_MIME_URL_PREFIX=%2Faad%2F&MIME_REPOSITORY_HANDLER=int.do%3FREQUEST_TYPE%3DMIME%26&MODIFIED_SINCE=&MYSAPSSO2=830c701b-b7d0-4195-9daf-947aad58ba2a-6ee89176-bcc1-4fb2-adf0-7f3dfc129b72-fd577942-2cf7-4247-8685-eee60ed63520-7eb0087a-2b31-43de-9dcb-1c6fed0ae2b5-9749b478-f71e-453e-bf82-2a113defb1d2-c2888b52-d27a-4555-a9c2-a58fe52f123a&REQUEST_URL=http%3A%2F%2Flocalhost%3A52593%2Faad%2Fint.do&SAP_EXTERNAL_SID=V0lEMTM5NjUxNTk4NjU0MQ%3D%3D&SAP_NODE_ID=10.10.210.55&SESSION_ID=10hf2y1y0ymv91axl9235ewslk&STATIC_MIME_URL_PREFIX=%2Faad%2F&URL_PREFIX=%2Faad%2Fint.do&USER_AGENT=Mozilla%2F5.0+%28compatible%3B+MSIE+9.0%3B+Windows+NT+6.1%3B+WOW64%3B+Trident%2F6.0%29&USER_NAME=UNKNOWN&USE_SNIPPETS=X, SAP_BW_USE_TAR_TITLE=, BROWSER_TYPE=ie6, FORCED_SERVER_COMMAND_PROCESSING=false, NAVIGATION_NODE_LAUNCHER_URL=, DEBUG_LEVEL=0, COUNTRY=BE, DEBUG_MESSAGES=false, RTL=false, BICS_USE_RFC_BUNDLE=DEFAULT, ALLOW_MULTI_DP_RESET=DEFAULT, ACCESSIBLE=false, CACHE=true, PROFILING=false, EXPORT_STRATEGY=-1, Template (Main)=AD87TXRJMRLPPBJL2WYEKJE, LANGUAGE=fr, CLIENT=ZEN, Template (Main Object)=BTMP AD87TXRJMRLPPBJL2WYEKJE, TRACE500_SCENARIO=, User=UNKNOWN (UNKNOWN), SHOW_TYPE=, Master System Alias=local, CONTENT_PADDING=true, BI Support Information=<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<BI_SUPPORT_INFORMATION>
<WEB_APPLICATION>
<PAGE_CONTEXT>
<USER>UNKNOWN (UNKNOWN)</USER>
<TIME>Thu Apr 03 11:06:48 CEST 2014</TIME>
<QUERY_STRING_INITIAL_BROWSER_REQUEST>ACCEPT=image%2Fjpeg%2C+image%2Fgif%2C+image%2Fpjpeg%2C+application%2Fx-ms-application%2C+application%2Fxaml%2Bxml%2C+application%2Fx-ms-xbap%2C+*%2F*&APPLICATION=Ad87txRJmRlPpbjl2wYeKJE&DYNAMIC_MIME_URL_PREFIX=%2Faad%2F&MIME_REPOSITORY_HANDLER=int.do%3FREQUEST_TYPE%3DMIME%26&MODIFIED_SINCE=&MYSAPSSO2=830c701b-b7d0-4195-9daf-947aad58ba2a-6ee89176-bcc1-4fb2-adf0-7f3dfc129b72-fd577942-2cf7-4247-8685-eee60ed63520-7eb0087a-2b31-43de-9dcb-1c6fed0ae2b5-9749b478-f71e-453e-bf82-2a113defb1d2-c2888b52-d27a-4555-a9c2-a58fe52f123a&REQUEST_URL=http%3A%2F%2Flocalhost%3A52593%2Faad%2Fint.do&SAP_EXTERNAL_SID=V0lEMTM5NjUxNTk4NjU0MQ%3D%3D&SAP_NODE_ID=10.10.210.55&SESSION_ID=10hf2y1y0ymv91axl9235ewslk&STATIC_MIME_URL_PREFIX=%2Faad%2F&URL_PREFIX=%2Faad%2Fint.do&USER_AGENT=Mozilla%2F5.0+%28compatible%3B+MSIE+9.0%3B+Windows+NT+6.1%3B+WOW64%3B+Trident%2F6.0%29&USER_NAME=UNKNOWN&USE_SNIPPETS=X</QUERY_STRING_INITIAL_BROWSER_REQUEST>
<QUERY_STRING_CURRENT_BROWSER_REQUEST>ACCEPT=image%2Fjpeg%2C+image%2Fgif%2C+image%2Fpjpeg%2C+application%2Fx-ms-application%2C+application%2Fxaml%2Bxml%2C+application%2Fx-ms-xbap%2C+*%2F*&APPLICATION=Ad87txRJmRlPpbjl2wYeKJE&DYNAMIC_MIME_URL_PREFIX=%2Faad%2F&MIME_REPOSITORY_HANDLER=int.do%3FREQUEST_TYPE%3DMIME%26&MODIFIED_SINCE=&MYSAPSSO2=830c701b-b7d0-4195-9daf-947aad58ba2a-6ee89176-bcc1-4fb2-adf0-7f3dfc129b72-fd577942-2cf7-4247-8685-eee60ed63520-7eb0087a-2b31-43de-9dcb-1c6fed0ae2b5-9749b478-f71e-453e-bf82-2a113defb1d2-c2888b52-d27a-4555-a9c2-a58fe52f123a&REQUEST_URL=http%3A%2F%2Flocalhost%3A52593%2Faad%2Fint.do&SAP_EXTERNAL_SID=V0lEMTM5NjUxNTk4NjU0MQ%3D%3D&SAP_NODE_ID=10.10.210.55&SESSION_ID=10hf2y1y0ymv91axl9235ewslk&STATIC_MIME_URL_PREFIX=%2Faad%2F&URL_PREFIX=%2Faad%2Fint.do&USER_AGENT=Mozilla%2F5.0+%28compatible%3B+MSIE+9.0%3B+Windows+NT+6.1%3B+WOW64%3B+Trident%2F6.0%29&USER_NAME=UNKNOWN&USE_SNIPPETS=X</QUERY_STRING_CURRENT_BROWSER_REQUEST>
<QUERY_STRING_CURRENT_SERVER_REQUEST>ACCEPT=image%2Fjpeg%2C+image%2Fgif%2C+image%2Fpjpeg%2C+application%2Fx-ms-application%2C+application%2Fxaml%2Bxml%2C+application%2Fx-ms-xbap%2C+*%2F*&APPLICATION=Ad87txRJmRlPpbjl2wYeKJE&DYNAMIC_MIME_URL_PREFIX=%2Faad%2F&MIME_REPOSITORY_HANDLER=int.do%3FREQUEST_TYPE%3DMIME%26&MODIFIED_SINCE=&MYSAPSSO2=830c701b-b7d0-4195-9daf-947aad58ba2a-6ee89176-bcc1-4fb2-adf0-7f3dfc129b72-fd577942-2cf7-4247-8685-eee60ed63520-7eb0087a-2b31-43de-9dcb-1c6fed0ae2b5-9749b478-f71e-453e-bf82-2a113defb1d2-c2888b52-d27a-4555-a9c2-a58fe52f123a&REQUEST_URL=http%3A%2F%2Flocalhost%3A52593%2Faad%2Fint.do&SAP_EXTERNAL_SID=V0lEMTM5NjUxNTk4NjU0MQ%3D%3D&SAP_NODE_ID=10.10.210.55&SESSION_ID=10hf2y1y0ymv91axl9235ewslk&STATIC_MIME_URL_PREFIX=%2Faad%2F&URL_PREFIX=%2Faad%2Fint.do&USER_AGENT=Mozilla%2F5.0+%28compatible%3B+MSIE+9.0%3B+Windows+NT+6.1%3B+WOW64%3B+Trident%2F6.0%29&USER_NAME=UNKNOWN&USE_SNIPPETS=X</QUERY_STRING_CURRENT_SERVER_REQUEST>
<REQUEST_URL>http://localhost:52593</REQUEST_URL>
<MASTER_SYSTEM_ALIAS>local</MASTER_SYSTEM_ALIAS>
<TRACE500_SCENARIO/>
<DESIGN_MODE>TRUE</DESIGN_MODE>
<TRACE>X</TRACE>
<IVIEW_ID_AVAILABLE>false</IVIEW_ID_AVAILABLE>
<BROWSER_SUPPORT_AJAX>true</BROWSER_SUPPORT_AJAX>
<TRAY_TYPE>PLAIN</TRAY_TYPE>
<ALLOW_MULTI_DP_RESET>DEFAULT</ALLOW_MULTI_DP_RESET>
<CONTENT_PADDING>true</CONTENT_PADDING>
<CACHE>true</CACHE>
<BROWSER_IN_BUSINESS_CLIENT>false</BROWSER_IN_BUSINESS_CLIENT>
<DEBUG>false</DEBUG>
<BICS_USE_RFC_BUNDLE>DEFAULT</BICS_USE_RFC_BUNDLE>
<FORCED_SERVER_COMMAND_PROCESSING>false</FORCED_SERVER_COMMAND_PROCESSING>
<NAVIGATION_NODE_LAUNCHER_URL/>
<AI_REDUCE_VISIBLE_SIZE>false</AI_REDUCE_VISIBLE_SIZE>
<SAP_BW_PRODUCER_ID/>
<NAVIGATION_NODE_ACTIVE_IVIEW/>
<RENDER_TYPE>PHX</RENDER_TYPE>
<SAP_BW_IVIEW_ID/>
<DATA_COUNTRY/>
<RTL>false</RTL>
<BICS_TRACE>false</BICS_TRACE>
<EXPORT_STRATEGY_MINCELLS>-1</EXPORT_STRATEGY_MINCELLS>
<CLIENT>ZEN</CLIENT>
<DATA_LANGUAGE/>
<JSCOMP>X</JSCOMP>
<DEBUG_MESSAGES>false</DEBUG_MESSAGES>
<SAP_BW_USE_TAR_TITLE/>
<DESIGN_MODE_OPTIMIZATION>X</DESIGN_MODE_OPTIMIZATION>
<DISPLAY_STACK_TRACE_IN_ERROR_PAGES>true</DISPLAY_STACK_TRACE_IN_ERROR_PAGES>
<EXPORT_STRATEGY>-1</EXPORT_STRATEGY>
<RFC_LANGUAGE/>
<CHECK_POPUP_BLOCKER/>
<BROWSER_TYPE>ie6</BROWSER_TYPE>
<JAVA_STATISTICS_ACTIVE>false</JAVA_STATISTICS_ACTIVE>
<RESULT_SET_TYPE/>
<PROFILING>false</PROFILING>
<LANGUAGE>fr</LANGUAGE>
<COUNTRY>BE</COUNTRY>
<BROWSER_SUPPORT_WEBKIT>false</BROWSER_SUPPORT_WEBKIT>
<ACCESSIBLE>false</ACCESSIBLE>
<SAP_BW_NAVIGATION_CONTEXT/>
<DEBUG_TEXTS>false</DEBUG_TEXTS>
<SHOW_TYPE/>
<WRITE_ERROR_CONTEXT>true</WRITE_ERROR_CONTEXT>
<TRACE500/>
<DEBUG_LEVEL>0</DEBUG_LEVEL>
<VALIDATION_DATA>false</VALIDATION_DATA>
<IGNORE_DIALOG_CUSTOMIZING>false</IGNORE_DIALOG_CUSTOMIZING>
<TEMPLATE_PARAMETERS>
<param name="ABAP_STATELESS" value="X"/>
<param name="BODY_ONLY" value="X"/>
<param name="BOOKMARK_LOADING" value="">
<param name="CLEAR_VARIABLES_SETTING" value="DEFAULT"/>
<param name="CMD_BEFORE_FIRST_REND_SETTING" value="X"/>
<param name="IGNORE_IVIEW_REPORT_PARAM" value=""/>
<param name="VARIABLE_SCREEN_SETTING" value="DEFAULT"/>
</param>
<param name="BROADCASTING_LINK" value=""/>
<param name="CHECK_POPUP_BLOCKER" value="X"/>
<param name="CLEAR_VARIABLES" value=""/>
<param name="COMMAND_PROCESSING" value="SERVER"/>
<param name="DATA_MODE" value="NEW"/>
<param name="DISABLE_DP_XML_RESET" value=""/>
<param name="DISPLAY_VARIABLE_SCREEN" value="DEFAULT"/>
<param name="DOCUMENT_SAVE_LEVEL" value="0"/>
<param name="ERRORS_VISIBLE" value="X"/>
<param name="EXPORT_LAYOUT" value=""/>
<param name="HAS_MAIN_TEMPLATE_OBJECT" value="">
<param name="MAIN_TEMPLATE_OBJECT" value="TEMPLATE_OBJECT_DATA_PROVIDER">
<param name="TEMPLATE_OBJECT_DATA_PROVIDER" value="">
<param name="DATA_PROVIDER_REF" value=""/>
</param>
</param>
</param>
<param name="INFORMATION_VISIBLE" value="X"/>
<param name="ITEMS_STATELESS" value=""/>
<param name="MELT_VARIABLES" value="X"/>
<param name="PATTERN_ALIAS" value=""/>
<param name="REPORT_REPORT_DISPLAY_TARGET" value="X"/>
<param name="RRI_OPEN_MODE" value="OPEN_IN_SEPARATE_WINDOW">
<param name="OPEN_IN_SEPARATE_WINDOW" value=""/>
</param>
<param name="SHOW_PERSONALIZED_VARIABLES" value=""/>
<param name="START_STATELESS_INTERVAL" value="0"/>
<param name="STATELESS" value=""/>
<param name="SYSTEM_MESSAGES_VISIBLE" value="X">
<param name="SYSTEM_MESSAGES_DISPLAY_MODE" value="ALWAYS"/>
</param>
<param name="TEMPLATE_VERSION" value="1"/>
<param name="THEME_NAME" value="aad_mobile"/>
<param name="USE_CONTEXT_MENU_SNIPPETS" value="X"/>
<param name="USE_LAYERED_WINDOWS" value="X"/>
<param name="USE_PERSONALIZATION" value=""/>
<param name="USE_SNIPPETS" value="X"/>
<param name="USE_SPECIFIC_VARIANT_CATALOG" value="X"/>
<param name="USE_TEMPLATE_PERSONALIZATION" value=""/>
<param name="VARIABLE_SCREEN" value=""/>
<param name="VARIABLE_VARIANT" value=""/>
<param name="WARNINGS_VISIBLE" value="X"/>
<param name="WEB_TEMPLATE_ACTIONS" value="">
<param name="ACTION_BEFORE_FIRST_RENDERING" value="">
<param name="INSTRUCTION" value=""/>
</param>
<param name="ACTION_BEFORE_RENDERING" value="">
<param name="INSTRUCTION" value=""/>
</param>
</param>
<param name="WINDOW_MODE" value="modal"/>
</TEMPLATE_PARAMETERS>
<TEMPLATE_CONTEXT>
<TEMPLATE_MAIN>AD87TXRJMRLPPBJL2WYEKJE</TEMPLATE_MAIN>
<TEMPLATE_MAIN_OBJECT>BTMP AD87TXRJMRLPPBJL2WYEKJE</TEMPLATE_MAIN_OBJECT>
</TEMPLATE_CONTEXT>
</PAGE_CONTEXT>
</WEB_APPLICATION>
</BI_SUPPORT_INFORMATION>
, WRITE_ERROR_CONTEXT=true, BROWSER_IN_BUSINESS_CLIENT=false, BROWSER_SUPPORT_WEBKIT=false, RFC_LANGUAGE=, RENDER_TYPE=PHX, Query String (Initial Browser Request)=ACCEPT=image%2Fjpeg%2C+image%2Fgif%2C+image%2Fpjpeg%2C+application%2Fx-ms-application%2C+application%2Fxaml%2Bxml%2C+application%2Fx-ms-xbap%2C+*%2F*&APPLICATION=Ad87txRJmRlPpbjl2wYeKJE&DYNAMIC_MIME_URL_PREFIX=%2Faad%2F&MIME_REPOSITORY_HANDLER=int.do%3FREQUEST_TYPE%3DMIME%26&MODIFIED_SINCE=&MYSAPSSO2=830c701b-b7d0-4195-9daf-947aad58ba2a-6ee89176-bcc1-4fb2-adf0-7f3dfc129b72-fd577942-2cf7-4247-8685-eee60ed63520-7eb0087a-2b31-43de-9dcb-1c6fed0ae2b5-9749b478-f71e-453e-bf82-2a113defb1d2-c2888b52-d27a-4555-a9c2-a58fe52f123a&REQUEST_URL=http%3A%2F%2Flocalhost%3A52593%2Faad%2Fint.do&SAP_EXTERNAL_SID=V0lEMTM5NjUxNTk4NjU0MQ%3D%3D&SAP_NODE_ID=10.10.210.55&SESSION_ID=10hf2y1y0ymv91axl9235ewslk&STATIC_MIME_URL_PREFIX=%2Faad%2F&URL_PREFIX=%2Faad%2Fint.do&USER_AGENT=Mozilla%2F5.0+%28compatible%3B+MSIE+9.0%3B+Windows+NT+6.1%3B+WOW64%3B+Trident%2F6.0%29&USER_NAME=UNKNOWN&USE_SNIPPETS=X, TRACE=X, AI_REDUCE_VISIBLE_SIZE=false, DEBUG=false, TRAY_TYPE=PLAIN, EXPORT_STRATEGY_MINCELLS=-1, DESIGN_MODE_OPTIMIZATION=X, Query String (Current Server Request)=ACCEPT=image%2Fjpeg%2C+image%2Fgif%2C+image%2Fpjpeg%2C+application%2Fx-ms-application%2C+application%2Fxaml%2Bxml%2C+application%2Fx-ms-xbap%2C+*%2F*&APPLICATION=Ad87txRJmRlPpbjl2wYeKJE&DYNAMIC_MIME_URL_PREFIX=%2Faad%2F&MIME_REPOSITORY_HANDLER=int.do%3FREQUEST_TYPE%3DMIME%26&MODIFIED_SINCE=&MYSAPSSO2=830c701b-b7d0-4195-9daf-947aad58ba2a-6ee89176-bcc1-4fb2-adf0-7f3dfc129b72-fd577942-2cf7-4247-8685-eee60ed63520-7eb0087a-2b31-43de-9dcb-1c6fed0ae2b5-9749b478-f71e-453e-bf82-2a113defb1d2-c2888b52-d27a-4555-a9c2-a58fe52f123a&REQUEST_URL=http%3A%2F%2Flocalhost%3A52593%2Faad%2Fint.do&SAP_EXTERNAL_SID=V0lEMTM5NjUxNTk4NjU0MQ%3D%3D&SAP_NODE_ID=10.10.210.55&SESSION_ID=10hf2y1y0ymv91axl9235ewslk&STATIC_MIME_URL_PREFIX=%2Faad%2F&URL_PREFIX=%2Faad%2Fint.do&USER_AGENT=Mozilla%2F5.0+%28compatible%3B+MSIE+9.0%3B+Windows+NT+6.1%3B+WOW64%3B+Trident%2F6.0%29&USER_NAME=UNKNOWN&USE_SNIPPETS=X, Request URL=http://localhost:52593, Time=Thu Apr 03 11:06:47 CEST 2014, SAP_BW_IVIEW_ID=, IGNORE_DIALOG_CUSTOMIZING=false, JAVA_STATISTICS_ACTIVE=false, DATA_LANGUAGE=, BROWSER_SUPPORT_AJAX=true, DISPLAY_STACK_TRACE_IN_ERROR_PAGES=true, BICS_TRACE=false, SAP_BW_PRODUCER_ID=, DEBUG_TEXTS=false, DATA_COUNTRY=, JSCOMP=X, IVIEW_ID_AVAILABLE=false, RESULT_SET_TYPE=, Template Parameters=<parameterList>
<param name="ABAP_STATELESS" value="X"/>
<param name="BODY_ONLY" value="X"/>
<param name="BOOKMARK_LOADING" value="">
<param name="CLEAR_VARIABLES_SETTING" value="DEFAULT"/>
<param name="CMD_BEFORE_FIRST_REND_SETTING" value="X"/>
<param name="IGNORE_IVIEW_REPORT_PARAM" value=""/>
<param name="VARIABLE_SCREEN_SETTING" value="DEFAULT"/>
</param>
<param name="BROADCASTING_LINK" value=""/>
<param name="CHECK_POPUP_BLOCKER" value="X"/>
<param name="CLEAR_VARIABLES" value=""/>
<param name="COMMAND_PROCESSING" value="SERVER"/>
<param name="DATA_MODE" value="NEW"/>
<param name="DISABLE_DP_XML_RESET" value=""/>
<param name="DISPLAY_VARIABLE_SCREEN" value="DEFAULT"/>
<param name="DOCUMENT_SAVE_LEVEL" value="0"/>
<param name="ERRORS_VISIBLE" value="X"/>
<param name="EXPORT_LAYOUT" value=""/>
<param name="HAS_MAIN_TEMPLATE_OBJECT" value="">
<param name="MAIN_TEMPLATE_OBJECT" value="TEMPLATE_OBJECT_DATA_PROVIDER">
<param name="TEMPLATE_OBJECT_DATA_PROVIDER" value="">
<param name="DATA_PROVIDER_REF" value=""/>
</param>
</param>
</param>
<param name="INFORMATION_VISIBLE" value="X"/>
<param name="ITEMS_STATELESS" value=""/>
<param name="MELT_VARIABLES" value="X"/>
<param name="PATTERN_ALIAS" value=""/>
<param name="REPORT_REPORT_DISPLAY_TARGET" value="X"/>
<param name="RRI_OPEN_MODE" value="OPEN_IN_SEPARATE_WINDOW">
<param name="OPEN_IN_SEPARATE_WINDOW" value=""/>
</param>
<param name="SHOW_PERSONALIZED_VARIABLES" value=""/>
<param name="START_STATELESS_INTERVAL" value="0"/>
<param name="STATELESS" value=""/>
<param name="SYSTEM_MESSAGES_VISIBLE" value="X">
<param name="SYSTEM_MESSAGES_DISPLAY_MODE" value="ALWAYS"/>
</param>
<param name="TEMPLATE_VERSION" value="1"/>
<param name="THEME_NAME" value="aad_mobile"/>
<param name="USE_CONTEXT_MENU_SNIPPETS" value="X"/>
<param name="USE_LAYERED_WINDOWS" value="X"/>
<param name="USE_PERSONALIZATION" value=""/>
<param name="USE_SNIPPETS" value="X"/>
<param name="USE_SPECIFIC_VARIANT_CATALOG" value="X"/>
<param name="USE_TEMPLATE_PERSONALIZATION" value=""/>
<param name="VARIABLE_SCREEN" value=""/>
<param name="VARIABLE_VARIANT" value=""/>
<param name="WARNINGS_VISIBLE" value="X"/>
<param name="WEB_TEMPLATE_ACTIONS" value="">
<param name="ACTION_BEFORE_FIRST_RENDERING" value="">
<param name="INSTRUCTION" value=""/>
</param>
<param name="ACTION_BEFORE_RENDERING" value="">
<param name="INSTRUCTION" value=""/>
</param>
</param>
<param name="WINDOW_MODE" value="modal"/>
</parameterList>
, TRACE500=, NAVIGATION_NODE_ACTIVE_IVIEW=}

Thanks for your response, I redevelop my Universe with a MsSQL and I receive this message
com.businessobjects.dsl.services.dataprovider.DataProviderException: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
    at com.businessobjects.dsl.services.dataprovider.impl.QuerySpecDataProvider.refresh(QuerySpecDataProvider.java:651)
    at com.businessobjects.dsl.services.dataprovider.impl.QuerySpecDataProvider.refresh(QuerySpecDataProvider.java:205)
    at com.businessobjects.bimodeler.qp.ui.QueryPanelComposite$26.run(QueryPanelComposite.java:1149)
    at java.lang.Thread.run(Unknown Source)
Caused by: com.sap.tools.commons.exception.NestedException: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
    at com.sap.tools.commons.exception.NestedException.create(Unknown Source)
    at com.sap.sl.edp.dataprovider.relational.fetcher.AbstractRelationalFetcher.open(AbstractRelationalFetcher.java:130)
    at com.sap.sl.edp.dataprovider.relational.RelationalDataProvider.getRelationalResults(RelationalDataProvider.java:338)
    at com.sap.sl.edp.dataprovider.relational.RelationalDataProvider.getResults(RelationalDataProvider.java:273)
    at com.sap.sl.edp.dataprovider.relational.RelationalDataProvider.getResults(RelationalDataProvider.java:1)
    at com.businessobjects.dsl.services.dataprovider.impl.QuerySpecDataProvider.getResultNode(QuerySpecDataProvider.java:692)
    at com.sap.sl.edp.dataprovider.relational.RelationalDataProvider.getResultNode(RelationalDataProvider.java:181)
    at com.businessobjects.dsl.services.dataprovider.impl.QuerySpecDataProvider.refresh(QuerySpecDataProvider.java:645)
    ... 3 more

Installing SAP GUI on 64-bit Windows 7 with 32-bit Office

Until about 6 months ago, 64-bit systems in my environment had 64-bit Office 2010 installed. That caused some problems with other applications, so I made the decision that, going forward, ALL systems would have 32-bit Office 2010 installed.
Apparently, it's taken 6 months, but I finally have a need to Install SAP GUI 7.20 Patch 6 on a 64-bit Windows 7 system with 32-bit Office 2010. It turns out, that doesn't work.
I receive this:
Not all package prerequisits [sic] are fulfilled
Outlook Client extension for the synchronization of SAPoffice calendar with Outlook calendar... No compatible version of Microsoft Outlook found.
I am assuming that since this same installation works on my 32-bit systems, that it is upset about my architecturally-mismatched Office.
Am I correct about the source for this problem? If so, is there anything I can do to make the GUI work in this environment?

Hi John,
Actually, there is no mismatch in having 32-bit Office installed on 64-bit Windows. In fact, this is probably the preferred environment. SAPGUI in general is much happier with 32-bit Office, especially older patches (by the way, 7.20 is no longer in support -- you should upgrade to 7.30).
The errors you're receiving are most probably related to lingering 64-bit components of Office on your workstation. We had the same situation in my office a while back, when we first started rolling out 64-bit Windows to a few users, and the PC techs mistakenly thought that meant they had to install 64-bit Office. That caused lots of problems, since 64-bit Office is incompatible with many things, not just SAPGUI, as you found. Correcting the error by simply reinstalling Office 32-bit resulting in workstations with some 64-bit and some 32-bit components, and that just made things worse. Systems where 32-bit Office was installed from the beginning (on 64-bit OS) had no problems at all.
So, what you're probably going to need to do is to uninstall all Office components (including Outlook, Visio, anything like that, not just Word and Excel), and also uninstall your SAPGUI, then reinstall 32-bit Office (with Outlook) from scratch, then reinstall your SAPGUI. This will probably clear up your problem.
Regards,
Matt

ColdFusion 9 ODBC Connection Issue

I have a 64 bit ODBC (OpenEdge/Progress) driver installed and it works fine in other applications but when I try to register the DSN in ColdFusion it gives me the error listed below. I've tried to research this error and everything I found and tried has not worked. Any ideas on what the issue is or how to resolve it?
java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application
The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application

Never seen the error before, but an "architecture mismatch" would imply you're trying to use a 64-bit driver with 32-bit ColdFusion.
What's the setup of the server?
O.

How to use VBScript to access a 32bit ODBC System DSN (Excel) on a Windows 7 64bit system?

What is the correct way to connect to a 32bit System DSN (Excel) on a Windows 7 64bit system?
I've recently switched from Windows XP Pro x32 to Windows 7 x64. Now, one of my scripts that uses an ODBC connection will no longer work. After a bit of searching, I discovered that Windows 7 x64 does not currently have 64bit Excel drivers. However, you can set up 32-bit connections by running "C:\Windows\SysWOW64\odbcad32.exe". Unfortunately, my script still won't work even though I set up the System DSN exactly like I did on my old computer.  When I run my script, I get the following error:
Quote:
Script:  X\XML_Check.vbs
Line:  212
Char:  3
Error:  [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application.
Code:  80004005
Source:  Microsoft OLE DB Provider for ODBC Drivers
Line 212 contains:
objConnection.Open "DSN=charge_codes_XLS;"
It seemed to me that wscript.exe will only communicate properly with an identical environment (x32 to x32 or x64 to x64, but not x64 to x32 or x32 to x64). With that in mind, I found a way around the error by running my script via the 32bit version of Windows Script Host. I changed the shortcut path from "X:\XML_CHECK.vbs" to "C:\Windows\SysWOW64\wscript.exe X:\XML_CHECK.vbs" and the script appears to function ok.
What I really want to know is if there is a way to run my script via the 64bit version of wscript.exe yet have it connect to the 32bit ODBC subsystem? Is there a specific connection string I can use or am I just out of luck until Microsoft puts out 64bit Excel drivers?

I faced the same issue recently. There was a 32bit MSOffice installed on the 64bit server and the same visual basic code worked from MS Office script debugger, and did not in the cscript/wscript.
It seems that
- the cscript/wscript used 64bit ODBC driver
- the office used 32bit ODBC driver
Excel drivers are installed for 32bit ODBC (because of 32 bit office the ODBC manager 32bit was a full hand of drivers).
Excel drivers are NOT installed for 64bit ODBC manager (because of 32 bit OFFICE) and can not be installed while the 32bit MS OFFICE is installed.
The SQL drivers are installed for 64bit ODBC (so that is why the SQL connection was established well)
The solution would be to run .js .vbs scripts in 32 bit environment:
\windows\SysWOW64\cscript.exe or \windows\SysWOW64\wscript.exe
Search for more with: how do i run a vbscript in 32 bit mode on a 64 bit machine

Excel file upload in ODI 11g

Hi,
I am trying to define new data server in topology manager in order to upload excel file, and when i test the connection i got this error:The specified DSN contains an architecture mismatch between the Driver and Application.
I did all the steps required before this step.
can anyone help me with this error
thanks in advance

You might be using 32 bit driver in a 64 bit operating system. Please download the 64 bit driver and use the same for creating DSN

Unable to Connect, ORA 12154, Setup routine for Microsoft ODBC errors

Hi all,
I have a Windows 7 Enterprise 64bit SP1 system and I wanted to be able to connect to an oracle database server. However, I am facing a problem with ODBC configuration.
I have currently installed both below in ... product\11.2.0\client_1 folder:
1. Oracle Database 11g Release 2 Client (11.2.0.1.0) for Microsoft Windows (x64) - http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html
2. 64-bit Oracle Data Access Components (ODAC) - http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html
I launched ODBC Data Source Administrator and added a User DSN but resulted to two errors:
1. The setup routines for the Microsoft ODBC for oracle ODBC driver could not be found. Please reintall the driver.
2. The specified DSN contains an architecture mismatch between the driver and application.
On top of that, if I go to System DSN tab, and tried to test the connection it give me an error:
1. Unable to connect SQLState = 08004 [Oracle][ODBC][Ora]ORA-12154: TNS: Could not resolved the identifier specified.
Can someone please guide me through this? Thanks in advance!
Edited by: VTech on Feb 26, 2013 2:13 PM

VTech wrote:
Hi all,
I have a Windows 7 Enterprise 64bit SP1 system and I wanted to be able to connect to an oracle database server. However, I am facing a problem with ODBC configuration.
I have currently installed both below in ... product\11.2.0\client_1 folder:
1. Oracle Database 11g Release 2 Client (11.2.0.1.0) for Microsoft Windows (x64) - http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html
2. 64-bit Oracle Data Access Components (ODAC) - http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html
You only need one of these (the second one should suffice).
I launched ODBC Data Source Administrator and added a User DSN but resulted to two errors:
1. The setup routines for the Microsoft ODBC for oracle ODBC driver could not be found. Please reintall the driver."Microsoft ODBC for Oracle" is a different provider than "Oracle ODBC". Make sure you're not using the Microsoft one.
2. The specified DSN contains an architecture mismatch between the driver and application.This can happen if you're mixing 32-bit and 64-bit. There's two ODBC control panels in Windows 7:
- the 64 bit one is the one in control panel
- the 32 bit one is c:\windows\syswow64\odbcad32.exe
Since you're using a 64 bit Oracle driver, you should be using the 64 bit ODBC administrator, and 64 bit applications. If you're trying to use this ODBC connection with a 32 bit application, you'll need to use the 32 bit ODBC (and the 32 bit Oracle driver).
On top of that, if I go to System DSN tab, and tried to test the connection it give me an error:
1. Unable to connect SQLState = 08004 [Oracle][ODBC][Ora]ORA-12154: TNS: Could not resolved the identifier specified.Well that actually means it's loading Oracle correctly, so that's something. You need to add an entry for the server you want to connect to into tnsnames.ora, located in the \network\admin folder inside of your Oracle client installation. Since it sounds like someone else set up the server you want to connect to, your DBA should be able to provide the information that goes into the file.

Architecture Mismatch

Similar Messages

Maybe you are looking for