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.

steps

Prerequisite: Fully functional Financial Consolidation application to which to connect.
Select Tools > Clear Error Log
Logoff
Logon
Begin by selecting Metadata > Control Tables
Click Ok on any messages
Click in a cell under Target Year; If values are returned, the connection to an HFM application is active.
Otherwise select Tools > View Error Log
Use the output to identify the issue.
The number of active custom dimensions in the FDM Adapter must match the number of custom dimensions in the HFM application
Connect to Oracle Hyperion FDM Workbench
Expand the Dimensions of the Target System Adapter
Right-Click Custom1 and check Active
Repeat for Custom2, Custom3, Custom4
Set the System Code and Save

description

For a Release 11.1.2.2 Financial Data Quality Management application, an error may occur like Unable to retrieve target System Data. The error log often facilitates identification of the connectivity issue. For example, “ActiveX component can’t create object: ‘fdmFM11xG5B.clsFMAdapter'” might indicate the System Code should be changed from FM11x-G5-B to FM11x-G6-A for HFM connectivity.
An error like Adapter function [fConnect] failed might indicate the number of dimensions Active in the adapter does not match the number of custom dimensions in the HFM application.
The OTN Community for FDM is well established and supportive of properly crafted requests:

external links

Additional thanks for the post: by Nicholas King.