Stats

  • Locked Locked
  • Replies 7
  • Subscribers 166
  • Views 10689
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Migrating CIS from 16.5 to 17.2 -- 32-bit vs. 64 bit?

Tmills

Hey guys...long time user of Capture CIS. We have always used MS Access to maintain our CIS database. After loading v17.2 and connecting to our .dbc and our CIS Database, we get an error as follows:

ERROR(ORCIS-6245): Database Operation Failed
Please Check Session For More Details
ERROR(ORCIS-6250): ODBC Error Code: -1
Description: The specified DSN contains an architecture mismatch between the Driver and Application

ODBC Error Description: State:IM014,Native:0,Origin:[Microsoft][ODBC Driver Manager]

After further investigation, it appears that error indicates a mismatch between 32-bit and 64-bit versions. We have made many attempts at changing our ODBC connection to correct this mismatch, but to no avail. Any thoughts or recommendations on fixing this would be appreciated.

Now what we noticed was the BenchAccess1720 sample file is, indeed, linked to an SQL database and NOT an Access database. I converted our Access Database over to an SQL database and managed to get things running again, however, this is NOT our preferred solution. 

We are looking for a solution to get our MS Access database connected to CIS in v17.2 without any changes.

Has anybody else had to deal with this? I can't believe that we are the only ones having this issue.

  • redwire

    This has been a known issue for years with the 64-bit OS releases.  You need to run the ODBC setup from C:\Windows\SysWow64\odbcad32.exe

    There should be a 64-bit migration guide that was issued with 16.5 since it had the same issue.

  • steve
    Hi - Take a look at:- www.orcad.co.uk/.../CaptureCIS_Datasources_172.pdf. You can access a 64-Bit ODBC driver that will connect to a 32-Bit database.
  • Tmills

    Thanks to both of you guys for the replies. We have tried multiple times to install the 64-bit driver, however, to no avail. It may be a local environment issue with our corporate permissions. 

    We will continue to hammer away on the 64-bit compatibility and this ODBC connection.

  • steve

    The important part is to run the downloaded exe from a DOS command prompt with the /passive switch. This should resolve the issues you are seeing

  • Bennigin
    I had the same problem. This is what I had to do. I had a hell of a time getting this to work with Office. Do you happen to have Microsoft Office 2010?


    Capture 17.2 is a 64 bit architecture hence 64 bits ODBC drivers are required to configure CIS database.
    You can download the 64 bit ODBC drivers from the below location however it is recommended to consult your IT before downloading them:
    www.microsoft.com/.../details.aspx
    For 64 bit Microsoft office:
    Package in the above link should work fine, simply install them and you will see 64 bit ODBC driver for MS access in administrative tools-> ODBC.
    For 32 bit Microsoft office:
    Same above package can be used for 32 bit Microsoft office as well however an additional switch ‘passive’ needs to be added. Follow the below steps in
    order to have 64 bit ODBC drivers with 32 bit Microsoft office.
    1. Store the above package in a folder.
    2. Go to command prompt and cd to that folder
    3. Now type AccessDatabaseEngine_x64.exe/passive on the prompt, so here an additional passive switch needs to be added.
    4. Now go to administrative tools-> ODBC and you will see the driver.
    Configuration of database to ODBC:
    For 64 bit ODBC drivers in Windows7 go to Control Panel\All Control Panel Items\Administrative Tools\ODBC
    In ODBC UI, you would see User DSN and System DSN.
    If you want to configure the database for logged in user only, then use 'User DSN'. If you want that anyone who logins in this system should have access to
    the database, use 'System DSN'.
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.