VERIFIED SOLUTION i
X

Vault ODBC export isn't working

Issue

12:33:57 exporting [docdata\20140321130414_d1dpbilpr.drd] to [DocumentRepository] table [tblDoc1ArchiveUpload] 
0 10 20 30 40 50 60 70 80 90 100 
| | | | | | | | | | | 
12:33:57 EXPORT: connect to database failed, [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified 
 
Made some changes and now they get: 
 
15:37:13 reseting server cache 
15:37:13 exporting [docdata\20140407090648_provr835its_series5a.drd] to [DocumentRepository] table [tblDoc1ArchiveUpload] 
0 10 20 30 40 50 60 70 80 90 100 
| | | | | | | | | | | 
15:37:13 EXPORT: connect to database failed, [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

Cause

12:33:57 exporting [docdata\20140321130414_d1dpbilpr.drd] to [DocumentRepository] table [tblDoc1ArchiveUpload] 
0 10 20 30 40 50 60 70 80 90 100 
| | | | | | | | | | | 
12:33:57 EXPORT: connect to database failed, [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified 
 
Made some changes and now they get: 
 
15:37:13 reseting server cache 
15:37:13 exporting [docdata\20140407090648_provr835its_series5a.drd] to [DocumentRepository] table [tblDoc1ArchiveUpload] 
0 10 20 30 40 50 60 70 80 90 100 
| | | | | | | | | | | 
15:37:13 EXPORT: connect to database failed, [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

Resolution

UPDATED: September 18, 2017


The first error:
 
12:33:57 exporting [docdata\20140321130414_d1dpbilpr.drd] to [DocumentRepository] table [tblDoc1ArchiveUpload] 
0 10 20 30 40 50 60 70 80 90 100 
| | | | | | | | | | | 
12:33:57 EXPORT: connect to database failed, [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified 


happened because they did not have the ODBC connection set up at all.  

The second error
 
 
15:37:13 reseting server cache 
15:37:13 exporting [docdata\20140407090648_provr835its_series5a.drd] to [DocumentRepository] table [tblDoc1ArchiveUpload] 
0 10 20 30 40 50 60 70 80 90 100 
| | | | | | | | | | | 
15:37:13 EXPORT: connect to database failed, [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

happened because they were on a 64 bit operating system (windows 2008) and using the ODBC 64 bit setup program.  Vault is 32 bit, so the 32 bit version of the ODBC setup needed to be used.

One of things that can cause it is when a 32 bit application like Vault tries to use a 64 bit ODBC connection (as is the case by default on Windows 2008)
 
One common issue is the difference between 32-bit and 64-bit ODBC data sources.
 
Vault, being a 32-bit process only seems the 32-bit data sources.
 
If you create a data source using the default ODBC tool on a 64-bit OS it will be a 64-bit source.
 
http://support.microsoft.com/kb/942976
---
The 32-bit version of the Odbcad32.exe file is located in the %systemdrive%\Windows\SysWoW64 folder.
The 64-bit version of the Odbcad32.exe file is located in the %systemdrive%\Windows\System32 folder.
 
If you create the ODBC connection using the 32bit version of the ODBC tool you should be able to get past this error.

Downloads

  • No Downloads