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.

Similar Messages

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

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]

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

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

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

Crystal Reports Ver 11 Logon Failed IM014 [Microsoft] [ODBC Driver manager

Please help. I am using Crystal Reports Version 11. I have Windows 7 and 64-bit browser. I am receiving the following error message: Details: IM014: [Microcsoft] [ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application.

Hello,
Two issues, CR XI is not support on Windows 7. To get this working upgrade to Cr XI R2 SP 6 for free, use your XI keycode.
https://smpdl.sap-ag.de/~sapidp/012002523100011802732008E/crxir2_sp4_full_build.exe
and then
https://smpdl.sap-ag.de/~sapidp/012002523100013876392008E/crxir2win_sp5.exe
https://smpdl.sap-ag.de/~sapidp/012002523100015859952009E/crxir2win_sp6.exe
Do not run CR between patches, When SP 6 is installed then CR should work.
Next issue is CR is a 32 bit application only and it will run on 64 bit OS's but it will not support any 64 bit third party applications including IE. To connect to your database you must use the 32 bit client.
Run the ODBC Administrator from the \syswow64 folder to create your DSN.
Thank you
Don
Edited by: Don Williams on Nov 4, 2010 10:06 AM

ODBC Issues with SAP Predictive Analytics 2.0 - Automated Analysis

Dear all,
maybe this adds only an aspect to the Infinite Insight OCBC Connection difficulties discussed in
http://scn.sap.com/message/15766247#15766247
but after trying and searching the web for more than a day any help would be appreciated.
This is the situation:
I'm using SAP PA 2.0 Desktop version and would like to upload a flatfile (*csv) to the Data Manager of Automated Analysis. Unfortunately, none of the solutions found by now worked.
It is a SAP PA 2.0 64bit version installed on a Windows 7.0 64 bit P. The installed MS Office version is 32bit as all available drivers. Deinstalling MS Office and reinstalling a 64bit version is not an option. It is not possible to install SAP PA 2.0 32bit version either - the Installation process stops due to the wrong operations system.
The DSN configuration suggested in the SCN discussion mentioned above didn't work, although displayed as data source in the Data Manager data base/file selection Screen. The error message returned is a Microsoft ODBC error [IM014] indicating that for the DSN used, there is an architecture mismatch between driver and application,
The attachments shows screenshots of the error message and the situation in the ODBC adminitrator consoles both for 32bit and for 64bit (in system32 and SysWOW64 shares).
Is there a solution to this problem?
Kind regards
Elisabeth

Hi Elisabeth,
If I understand correcty, you would like to upload your csv file to a database.
What kind of database is it ?
The Automated part of Predictive Analytics supports the following databases:
SAP HANA
Sybase IQ
Oracle
Hive
Teradata
Microsoft SQL Server
MySQL 5
Netezza
IBM DB2
PostgreSQL
Vertica
Greenplum
Your screensot shows ODBC connections to Excel and Text files. It is is not real databases, it cannot execute SQL code.
For more information on configuring a database connection on your machine, you can refer to this document : https://websmp204.sap-ag.de/~sapidb/012002523100001708812015E/pa20_conndb_win_conf_en.pdf
Note that you need a database driver installed on your machine and access to a database (either installed on your machine or on a remote server).
In general, all documentation related to PA2.0 can be found here : SAP Predictive Analytics 2.0 – SAP Help Portal Page.
Hope this helps.
Kind regards,
Armelle

SSRS report using Access database in SharePoint.

Dear All,
I have created SSRS report using Access database. I have successfully deploy SSRS report in SharePoint document library.
When I am opening the same report I am getting following error.
Can anyone please help me how to resolve this issue ?
Error:
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'WOW'. (rsErrorOpeningConnection)
ERROR
[IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an
architecture mismatch between the Driver and Application
Thanks,
Harish P

This seems odbc driver issue ,Plz check the follwoing links for the solution
http://social.technet.microsoft.com/Forums/sqlserver/en-US/a4ddb239-64d8-4074-978c-45c30381c107/ssrs-2012-error-im014-microsoftodbc-driver-manager-the-specified-dsn-contains-an-architecture?forum=sqlreportingservices
http://social.msdn.microsoft.com/Forums/en-US/a4ddb239-64d8-4074-978c-45c30381c107/ssrs-2012-error-im014-microsoftodbc-driver-manager-the-specified-dsn-contains-an-architecture?forum=sqlreportingservices
Please Mark it as answer if this reply helps you in resolving the issue,It will help other users facing similar problem

Signing on error in application server

PeopleTools Release 8.53 (Windows) starting. Tuxedo server is APPSRV(99)/2
PSAPPSRV.3312 (0) [2013-03-20T20:12:23.571](0) Cache Directory being used: D:\PT853\appserv\DB290401\CACHE\PSAPPSRV_2\
PSAPPSRV.3312 (0) [2013-03-20T20:12:24.007](3) File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 8600 - [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application (SQLSTATE IM014) 0
PSAPPSRV.3312 (0) [2013-03-20T20:12:24.076](1) GenMessageBox(200, 0, M): SQL Access Manager: File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 8600 - [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application (SQLSTATE IM014) 0
PSAPPSRV.3312 (0) [2013-03-20T20:12:24.113](0) Database Options: override_connection_reset: 0
PSAPPSRV.3312 (0) [2013-03-20T20:12:24.155](1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database DB290401 with user PTADMIN.
PSAPPSRV.3312 (0) [2013-03-20T20:12:24.209](0) Server failed to start
PSADMIN.3604 (0) [2013-03-20T20:12:32.023](0) End boot attempt on domain DB290401

What's exactly your OS ? Something seems to be wrong in the wordsize (32/64bit).
Please find out more in the note +*[ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application [ID 1477002.1]*+
Nicolas.

32 bit vs 64 bit odbc connection problems

Good morning,
I am trying to connect a powershell script that worked fine on a 32 bit system, but now will not work on a 64 bit system. This script connects to a odbc connection and connects to a remedy ticket system and pulls information to move over to my Outlook
calendar.
The error am getting is:
Exception calling "Open" with "0" argument(s): "ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application"
At C:\Users\Public\Documents\RemedyCRQ.ps1:25 char:17
+ $connection.Open <<<< ()
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException
The code that is running this is below:
$script:showWindowAsync = Add-Type –memberDefinition @”
[DllImport("user32.dll")]
public static extern bool ShowWindowAsync(IntPtr hWnd, int nCmdShow);
“@ -name “Win32ShowWindowAsync” -namespace Win32Functions –passThru
$null = $showWindowAsync::ShowWindowAsync((Get-Process –id $pid).MainWindowHandle, 2)
$connection = New-Object System.Data.Odbc.OdbcConnection
$command = New-Object System.Data.Odbc.OdbcCommand
$command.Connection = $connection
$remedyTickets = @()
$connectionString = "DSN=remedy"
$connection.ConnectionString = $connectionString
$connection.Open()
I would appreciate it if someone had some insight to offer. I've looked around and have created the ODBC connection on the 32 bit odbc version c:\windows\sysWOW64\odbcad32.exe. Doesn't seem to have changed anything. Ive created it both
as a user and system DSN.

Add the below code in to your Script.
if ([environment]::Is64BitProcess -eq $True)
C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -File "script filename"
Exit
Note: The path I used is for Windows 7, you need to figure out the path for your OS.
S.Arun Prasath

Problems connecting to 32 bit msaccess database from 64 bit 11G

Here is the issue:
I have a 9i (32 bit windows) database with an hsodbc connection to an an older access database so once schema can see & copy data from said access database, all works fine.
I'm getting ready to move the database to 64 bit 11.2.0.3 on windows 2008 64 bit server, database is migrated and tested ok.
The problem is with the dg4odbc connection, I have created connections for AS400 databases and they're ok, but I set up an ODBC to the access database, using the 32 bit ODBC interface as MS recommends, but I still keep getting this error:
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture
mismatch between the Driver and Application {IM014}
ORA-02063: preceding 2 lines from RADERDB
According to MS technet this is from not using the c:\Windows\SysWOW64\odbcad32.exe to set up the ODBC connection, but I did use that executable, when I use the regular 64 bit ODBC admin I can't even see msaccess drivers to begin with.
The funny thing is, when I point the tnsnames.ora entry to the old 9i server, it uses that ODBC connection and then the 11G dblink then works fine. However this is a band-aid solution and I want to get everything working from the new production database server.
Any suggestions?
thanks in advance..

The message means that you're using a 32bit ODBC driver with a 64bit program. That does not work. If you want to connect with the 64bit DG4ODBC you need to use a 64bit ODBC driver. There's a package available from the Microsoft Technet sites (AccessDatabaseEngine_x64 - http://www.microsoft.com/en-gb/download/details.aspx?id=13255 ) that ships 64bit ODBC drivers for their Excel/Access programs.
Please be aware that installing 32bit gateway products on 64bit Windows is NOT supported.
- Klaus

SSIS Package with Scheduled Task

Hi there,
We have on a SQL-Server some SSIS Packages which refers to Navision. If I start the job manually directly in Navision, it works fine. If I start the Job in MSSQL manually (SQL Server Agent --> Jobs --> 'MyJobPackage' --> Start Job at Setp) or through
the Job Activity Monitor ('MyJobPackage' --> Start Job at Step) it works also fine without any problems. But if the Job starts automatically (Scheduled Job in MSSQL) it will never end. So the Job is running endless. Now, we thought we could try to start
this SQL Job with a Scheduled Task in Windows. So I created a cmd-File with the following line:
dtexec /f "E:\SSIS Schnittstelle\TEST_Navision2XAPF\Navision2X.APF\bin\EGHU.dtsx" /De MyPassword
And then I get this errors:
C:\Users\exprma\Desktop>dtexec /f "E:\SSIS Schnittstelle\TEST_Navision2XAPF\Navision2X.APF\bin\EGHU.dtsx" /De MyPassword
Microsoft (R) SQL Server Execute Package Utility
Version 10.50.2500.0 for 64-bit
Copyright (C) Microsoft Corporation 2010. All rights reserved.
Started: 10:17:44
Progress: 2014-03-12 10:17:45.32
   Source: Dimensionen
   Validating: 0% complete
End Progress
Error: 2014-03-12 10:17:45.34
   Code: 0xC0047062
   Source: Dimensionen Dimension [134]
   Description: System.Data.Odbc.OdbcException: ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
   at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode)
   at System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcConnectionString constr, OdbcEnvironmentHandle environmentHandle)
   at System.Data.Odbc.OdbcConnectionOpen..ctor(OdbcConnection outerConnection, OdbcConnectionString connectionOptions)
   at System.Data.Odbc.OdbcConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.Odbc.OdbcConnection.Open()
   at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName, String connStr, Object transaction)
   at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager100.AcquireConnection(Object pTransaction)
   at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
   at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper100 wrapper, Object transaction)
End Error
Error: 2014-03-12 10:17:45.34
   Code: 0xC0047017
   Source: Dimensionen SSIS.Pipeline
   Description: component "Dimension" (134) failed validation and returned error code 0x80131937.
End Error
Progress: 2014-03-12 10:17:45.34
   Source: Dimensionen
   Validating: 4% complete
End Progress
Error: 2014-03-12 10:17:45.34
   Code: 0xC004700C
   Source: Dimensionen SSIS.Pipeline
   Description: One or more component failed validation.
End Error
Error: 2014-03-12 10:17:45.34
   Code: 0xC0024107
   Source: Dimensionen
   Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 10:17:44
Finished: 10:17:45
Elapsed: 0.999 seconds
So what could I try at the next step?
Regards
ÖFES

Hi Öfes,
Based on the error message when executing the package from batch file and the solution provided by Visakh, we can conclude that the package uses 32-bit ODBC drivers. Now let’s go back to the original SQL Server Agent job issue. Since you can run the job
manually from SSMS, the package should run in 32-bit SSIS runtime mode, e.g. the “Use 32 bit runtime” option should be checked for the package executions with in the job step. In this case, SSIS automatically uses the 32-bit DTExec utility, therefore, we don’t
need to specify the 32-bit DTExec utility in the command line for the job step.
Based on the current information, the issue may occur due to two possible factors:
The Dimension component in the package uses User DSN rather than System DSN.
The user account under which the job runs doesn’t have sufficient permissions to execute the package.
So, please try the following steps:
Open the C:\Windows\SysWOW646\odbcad32.exe, and make sure the DSN is a System DSN which can be accessed by any user on the server.
Create a new SQL Server Agent proxy account which has sufficient permissions to execute the package, for example, the user account that you execute the job manually from SSMS.
Reference:
http://technet.microsoft.com/en-us/library/ms190698(v=sql.105).aspx
Regards,
Mike Yin
TechNet Community Support

Connection to local .mdb using CR 10.5 x64 runtimes

Hi,
I am using the CR 10.5 x86 and x64 runtimes for an application built in VS 2008. The application builds and runs correctly, and I am able to load and view a .rpt using an .mdb as the datasource.
In the x86 version of the application:
I use the CR 10.5 x86 runtimes, and the .rpt file was built using a DAO connection to an .mdb. I apply the following code to dynamically change the datasource:
public bool ChangeDatasource(string DatabasePath)     // E.g. DatabasePath = "C:\newdata.mdb"
            crConnectionInfo.ServerName = DatabasePath;
            crConnectionInfo.DatabaseName = DatabasePath;
            crConnectionInfo.UserID = "";
            crConnectionInfo.Password = "password";
            //Loop through all tables in the main report
            crDatabase = crReportDocument.Database;
            crTables = crDatabase.Tables;
            for (int i = 0; i < crTables.Count; i++)
                crTable = crTables[ i ];
                crTableLogOnInfo = crTable.LogOnInfo;
                crTableLogOnInfo.TableName = crTable.Name;
                crTableLogOnInfo.ConnectionInfo = crConnectionInfo;
                crTable.ApplyLogOnInfo(crTableLogOnInfo);
                bool bOn = crTable.TestConnectivity();
                if (!bOn)
                    MessageBox.Show("Failed to connect to " + crTable.Name);
            crReportDocument.VerifyDatabase();
The above works perfectly in x86.
However, in the x64 version:
Using the CR 10.5 x64 runtimes, the application builds and runs correctly, and displays a simple report just fine.
However, when I use the code above, TestConnectivity() fails and I get the following error during VerifyDatabase():
"Error in File ____.rpt: Invalid mapping type value."
As I understand it, this is because the .rpt was built with a DAO connection, which does not support 64-bit. Thus, I am trying to alter the .rpt to use another connection. My results are as follows:
32-bit DSN, using DAO / ODBC / ADO: I can create the connection, but I still get the "Invalid mapping type value" error when running the code above in x64.
64-bit DSN using ODBC: I get an IM014 "The specified DSN contains an architecture mismatch" error in the Database Expert when trying to set up the connection.
64-bit DSN using ADO: None of the provider options seem to work when setting up the connection in the Database Expert. I get errors like "Data source name not found and no default driver specified".
Note, before anyone asks: Yes, I do have the 64-bit Access ODBC drivers installed, and working. I use them in another part of my x64 application, and they work correctly.
Any help would be GREATLY appreciated.

Ludek,
I think there must still be some confusion here.
I am well-aware that I can design reports using the Access 2007 (32-bit ODBC) drivers. In fact, I have already tried this, and it works fine with my 32-bit app using CR 10.5 32-bit.
However, those reports do not connect when using my 64-bit app using CR10.5 64-bit. This makes sense, because the Access 2007 drivers are 32-bit.
The reason I have been trying to use Access 2010 is that, unlike 2007, it has 64-bit ODBC drivers.
I'll try to make this more clear, once again:
My 32-bit app, using CR 10.5 32-bit:
- Report built with DAO: Works
- Report built with Access 2007 32-bit ODBC: Works
- Report built with Access 2010 32-bit ODBC: Works
My 64-bit app, using CR 10.5 64-bit:
- Report built with DAO: (no 64-bit DAO) "Invalid mapping type value" error when running app
- Report built with Access 2007 32-bit ODBC: "Invalid mapping type value" error when running app
- Report built with Access 2010 32-bit ODBC: "Invalid mapping type value" error when running app
- Report built with Access 2010 64-bit ODBC: "Architecture mismatch" error when trying to design the report
You also said you would test CRVS2010 x64 with Access 2010 x64. Do you have a result for that yet?
P.S. Your first link results in an error. Can you provide a corrected link?
Edited by: DKouts on Aug 18, 2010 11:44 PM

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.

Architecture Mismatch IM014

Similar Messages

Maybe you are looking for