Symptom
ERROR:
Code............................................. -2147467259
Description...................................... [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
At line: 90
Procedure........................................ clsImpProcessMgr.fLoadAndProcessFile
Component........................................ upsWObjectsDM
Version.......................................... 1112
Thread........................................... 78068
In Windows, for FDM, use the correct architecture to create a 32-bit DSN
steps
Prerequisite: Fully functional 64-bit Windows server (e.g., Windows Server 2008 R2).
Create a 32-bit DSN by launching a 32-bit version of the Data Source Administrator.
%windir%\SysWoW64\odbcad32.exe
Either of SQL Native Client or 32-bit POracle database ODBC drivers are required
description
For a Release 11.1.2.x Financial Data Quality Management application, an error may occur like [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application. The error log often facilitates identification of the connectivity issue. For example, “-2147467259” might indicate the installation ‘guru’ should use a 32-bit DSN rather than the 64-bit version accessed by default.
This will be found from the command line in Windows Server 2003 or 2008 at %windir%\SysWoW64\odbcad32.exe
external links
none.
This article from Easysoft Limited also discusses
solutions to thisarchitecture mismatch problem.Andy, your product looks interesting; However it is not a solution for this particular problem.