Odbc error im014

how can i fix this error? ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application.. it is occuring in a new project tha...

how can i fix this error? ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application.. it is occuring in a new project that i am doing… im using vb 2008 , MYSQL as my database and windows 8.1 as my OS

i read on forums that you just fix with the odbc administrator tool… i tried creating my DSN there but it still doesnt work… i tried opening an old project of mine it works fine.. but this new project keeps getting that error.. i need this to work so that i can do my crystal reports.. i’ve been trying to fix this error for a full day now and i cant fix it..

can someone help me?
THANKS..

asked Jan 28, 2014 at 2:02

bolek evora's user avatar

its a 64 vs 32 bit issue. You are accessing a 32 bit odbc driver on a 64 bit system.

IF YOU OPEN c:windowssystem32odbcad32.exe you will not see a driver there that is in c:windowssyswow64odbcad32.exe (or just the opposite)

Check the target platform of your application, and if that doesn’t fix it, you might be able to sneak by just installing the correct driver ( 64 or 32 bit )

If you are debugging the project from Visual Studio, you will also need to run it as 32-bit. In order to do this you need to open the project properties by right clicking on the project and selecting properties. Once here you need to set Run64BitRuntime to FALSE.*

enter image description here

J.C. Gras's user avatar

J.C. Gras

4,5441 gold badge36 silver badges42 bronze badges

answered Jan 28, 2014 at 3:27

2

After searching on the internet I found the solution for my .vb project:

  1. Open ODBC Data Sources (32-bit) (location: C:Windowssyswow64odbcad32.exe)
  2. Open tab System DNS
  3. Add -> Sybase ACE ODBC Driver -> Fill in Name (example: DSN_32), net work address (address and port, example: 192.168.1.1,4100) and database name -> Test connection ->OK

enter image description here

  1. From your application, update your connection string to use DSN=DSN_32
    Example:

value=»PWD=123456;DSN=DSN_32;UID=123456;SRVR=123456;DB=123456″

enter image description here

Hope this helps.

answered Nov 15, 2019 at 7:15

anhtv13's user avatar

anhtv13anhtv13

1,5644 gold badges26 silver badges49 bronze badges

RESOLVED !

  1. Go to IIS.
  2. Choose Your app pool.
  3. Go To Advanced Settings, and
  4. Enable enable32bitAppOnWin64

answered Feb 6, 2020 at 18:35

Fad Sel's user avatar

Fad SelFad Sel

791 silver badge6 bronze badges

2

For those running things in IIS Express, this can be fixed by the Bitness setting in the project properties under the Web section. As seen in the screenshot below

Visual Studio project property settings

answered Aug 28, 2020 at 9:48

Craig's user avatar

CraigCraig

3903 silver badges13 bronze badges

This is how I solved it to access a MS Access database via ODBC. Make sure that your bit architecture matches everywhere. For instance, in my case this is the only setup that worked on my W10 pro 64 bit PC, accessing a MS Access database hosted on a W2012 64 bit server. On my PC:

  • Install XAMPP 32bit (I tried 64 bit, but it gave me the «architecture mismatch» error)
  • Install AccessDatabaseEngine.exe 32 bit version (available from Microsoft)
  • Configure your data source using the 32 bit program: C:WindowsSysWOW64odbcad32.exe. There I selected the «Microsoft Access Driver (*.mdb, *.accdb)» driver.

answered Aug 2, 2020 at 6:35

Manny Ramirez's user avatar

how can i fix this error? ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application.. it is occuring in a new project that i am doing… im using vb 2008 , MYSQL as my database and windows 8.1 as my OS

i read on forums that you just fix with the odbc administrator tool… i tried creating my DSN there but it still doesnt work… i tried opening an old project of mine it works fine.. but this new project keeps getting that error.. i need this to work so that i can do my crystal reports.. i’ve been trying to fix this error for a full day now and i cant fix it..

can someone help me?
THANKS..

asked Jan 28, 2014 at 2:02

bolek evora's user avatar

its a 64 vs 32 bit issue. You are accessing a 32 bit odbc driver on a 64 bit system.

IF YOU OPEN c:windowssystem32odbcad32.exe you will not see a driver there that is in c:windowssyswow64odbcad32.exe (or just the opposite)

Check the target platform of your application, and if that doesn’t fix it, you might be able to sneak by just installing the correct driver ( 64 or 32 bit )

If you are debugging the project from Visual Studio, you will also need to run it as 32-bit. In order to do this you need to open the project properties by right clicking on the project and selecting properties. Once here you need to set Run64BitRuntime to FALSE.*

enter image description here

J.C. Gras's user avatar

J.C. Gras

4,5441 gold badge36 silver badges42 bronze badges

answered Jan 28, 2014 at 3:27

2

After searching on the internet I found the solution for my .vb project:

  1. Open ODBC Data Sources (32-bit) (location: C:Windowssyswow64odbcad32.exe)
  2. Open tab System DNS
  3. Add -> Sybase ACE ODBC Driver -> Fill in Name (example: DSN_32), net work address (address and port, example: 192.168.1.1,4100) and database name -> Test connection ->OK

enter image description here

  1. From your application, update your connection string to use DSN=DSN_32
    Example:

value=»PWD=123456;DSN=DSN_32;UID=123456;SRVR=123456;DB=123456″

enter image description here

Hope this helps.

answered Nov 15, 2019 at 7:15

anhtv13's user avatar

anhtv13anhtv13

1,5644 gold badges26 silver badges49 bronze badges

RESOLVED !

  1. Go to IIS.
  2. Choose Your app pool.
  3. Go To Advanced Settings, and
  4. Enable enable32bitAppOnWin64

answered Feb 6, 2020 at 18:35

Fad Sel's user avatar

Fad SelFad Sel

791 silver badge6 bronze badges

2

For those running things in IIS Express, this can be fixed by the Bitness setting in the project properties under the Web section. As seen in the screenshot below

Visual Studio project property settings

answered Aug 28, 2020 at 9:48

Craig's user avatar

CraigCraig

3903 silver badges13 bronze badges

This is how I solved it to access a MS Access database via ODBC. Make sure that your bit architecture matches everywhere. For instance, in my case this is the only setup that worked on my W10 pro 64 bit PC, accessing a MS Access database hosted on a W2012 64 bit server. On my PC:

  • Install XAMPP 32bit (I tried 64 bit, but it gave me the «architecture mismatch» error)
  • Install AccessDatabaseEngine.exe 32 bit version (available from Microsoft)
  • Configure your data source using the 32 bit program: C:WindowsSysWOW64odbcad32.exe. There I selected the «Microsoft Access Driver (*.mdb, *.accdb)» driver.

answered Aug 2, 2020 at 6:35

Manny Ramirez's user avatar

Problem

When utilizing a 32-bit ODBC driver on a 64-bit platform to connect to an IBM Informix database server, an ODBC application will fail to connect indicating that there is an architecture mismatch.

Symptom

The error message returned from the Microsoft ODBC Driver Manager states: ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

Cause

The cause of the problem is that the ODBC application is compiled within Visual Studio and targeted as ‘Any CPU’ which means the application will run on either a 32-bit or 64-bit platform. The problem with this is that if the application is deployed on a 64-bit platform and utilizes a 32-bit ODBC provider, the application expects to utilize a 64-bit provider.

Diagnosing The Problem

The best way to diagnose the problem is to use Microsoft’s Process Monitor and filter on the application executable to view what libraries the application is attempting to load prior to the failure.

Resolving The Problem

To resolve the problem, one needs to compile the application within Visual Studio targeted for an ‘x86’ CPU. This will ensure that the application attempts to load the 32-bit ODBC provider instead of the 64-bit one. You can do this by right clicking on your project and selecting Properties. In the build tab, you will find the Platform Target (ANY CPU, x86, x64 or Itanium).

[{«Product»:{«code»:»SSVT2J»,»label»:»Informix Tools»},»Business Unit»:{«code»:»BU059″,»label»:»IBM Software w/o TPS»},»Component»:»Informix Client Software Development Kit (CSDK)»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»3.5;3.7;4.0″,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]

  • Remove From My Forums
  • Question

  • 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

Answers

  • Hi DCady,

    To manage a data source that connects to a 32-bit driver under 64-bit platform, we use C:WindowsSysWOW64odbcad32.exe. To manage a data source that connects to a 64-bit driver, we use C:WindowsSystem32odbcad32.exe.

    Generally, if we use the 64-bit odbcad32.exe (C:WindowsSystem32odbcad32.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:WindowsSysWOW64odbacad32.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

    • Proposed as answer by

      Thursday, December 20, 2012 9:25 PM

    • Marked as answer by
      Mike Yin
      Monday, December 24, 2012 4:55 PM

  • Remove From My Forums
  • Вопрос

  • Hi All,

    When I try to connect MySQL database through SSIS I am getting this error «ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application».

    I have successfully installed MYSQL ODBC driver 64 bit, OS is 64 bit and SSDT 2015 is also 64 bit. But still I don’t know why i am getting this error. I have gone through many blogs but unable to fix it. 

    Tried to change the platform in connection manager but unable to do it. As I click on NEW under active platform drop down it is not opening new window for me.

    Can anyone help me to fix this issue.

    Thanks all in advance.

    Regards,

    Naga

Ответы

  • SSDT 2015 is also 64 bit

    Hello Naga,

    No, it’s not, even when you used a x64 installer. SSDT is a plugin for Visual Studio and that was & is a
    32 bit app; there is no VS as 64 bit available.

    You have to install 32 bit data provider when you want to use them in SSDT/VS.


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    • Предложено в качестве ответа

      30 января 2018 г. 5:05

    • Помечено в качестве ответа
      manisubbu
      30 января 2018 г. 7:50

    • Изменено
      Visakh16MVP
      29 января 2018 г. 12:48
    • Предложено в качестве ответа
      Xi Jin
      30 января 2018 г. 5:05
    • Помечено в качестве ответа
      manisubbu
      30 января 2018 г. 7:50

Главная » Основные форумы » Экспорт в системы тех.анализа

Страницы:
1

 

Олег Лефлер


Пользователь

Сообщений: 3
Регистрация: 11.09.2017

#1

05.12.2017 15:12:04

ОС Win10-х64. Квик вер.7.14.1.7

Догадываюсь почему возникает такая ошибка, но не знаю как решить. Подскажите пожалуйста.

 

Alexey Ivannikov


QUIK clients support

Сообщений: 1275
Регистрация: 22.12.2014

#2

05.12.2017 16:19:55

Цитата
Олег Лефлер написал:
ОС Win10-х64. Квик вер.7.14.1.7

Догадываюсь почему возникает такая ошибка, но не знаю как решить. Подскажите пожалуйста.

Добрый день.

Необходимо использовать администратор источников данных, расположенный по адресу: %windir%syswow64odbcad32.exe

 

Олег Лефлер


Пользователь

Сообщений: 3
Регистрация: 11.09.2017

#3

05.12.2017 16:47:22

Цитата
Alexey Ivannikov написал:

Цитата
Олег Лефлер   написал:
ОС Win10-х64. Квик вер.7.14.1.7

Догадываюсь почему возникает такая ошибка, но не знаю как решить. Подскажите пожалуйста.

Добрый день.

Необходимо использовать администратор источников данных, расположенный по адресу: %windir%syswow64odbcad32.exe

А как конкретно его использовать, можете уточнить?

 

Alexey Ivannikov


QUIK clients support

Сообщений: 1275
Регистрация: 22.12.2014

#4

05.12.2017 17:20:10

Цитата
Олег Лефлер написал:

Цитата
Alexey Ivannikov   написал:

Цитата
Олег Лефлер   написал:
ОС Win10-х64. Квик вер.7.14.1.7

Догадываюсь почему возникает такая ошибка, но не знаю как решить. Подскажите пожалуйста.

Добрый день.

Необходимо использовать администратор источников данных, расположенный по адресу: %windir%syswow64odbcad32.exe

А как конкретно его использовать, можете уточнить?

Удалите ранее настроенный DSN источник, запустите из командной строки %windir%SysWOW64odbcad32.exe
Создайте там новый DSN источник с тем же именем. Дело в том, что на x64 системах существует две программы по настройки ODBC. Одна в папке %windir%System32, а другая в папке %windir%SysWOW64. Использовать нужно ту, которая в SysWOW64, а по умолчанию ярлык в Пуск — Панель управления — Администрирование  ссылается на System32. Потому и не работает. Почему именно так а не иначе, вопрос к Microsoft.

 

Heldar


Пользователь

Сообщений: 3
Регистрация: 08.06.2018

#5

08.06.2018 16:30:43

Цитата
Удалите ранее настроенный DSN источник, запустите из командной строки %windir%SysWOW64odbcad32.exe
Создайте там новый DSN источник с тем же именем. Дело в том, что на x64 системах существует две программы по настройки ODBC. Одна в папке %windir%System32, а другая в папке %windir%SysWOW64. Использовать нужно ту, которая в SysWOW64, а по умолчанию ярлык в Пуск — Панель управления — Администрирование  ссылается на System32. Потому и не работает. Почему именно так а не иначе, вопрос к Microsoft.

А если в ODBC х64 нет драйвера к PostgreSQL?

Компьютер Win7 64
Сервер PostgreSQL 9.5.3 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4), 64-bit
Задача: подключиться с помощью мастера импорта-экспорта в MS SQL Management Studio к табличкам из БД PostgreSQL.

 

Heldar


Пользователь

Сообщений: 3
Регистрация: 08.06.2018

#6

08.06.2018 16:36:01

Скачал необходимую ODBC. В запускаемом по умолчанию (который по факту х32) все ок, выбираю PostgreSQL Unicode(x64). Соединение устанавливается. К БД через Excel все ок.
Но при попытке через мастер импорта-экспорта в MS SQL Management Studio выдает ошибку «В указанном DSNархитектура драйвера и архитектура приложения не соответствуют друг другу.»

 

Egor Zaytsev


QUIK clients support

Сообщений: 3548
Регистрация: 27.01.2015

#7

09.06.2018 12:03:03

Ошибка
«Но при попытке через мастер импорта-экспорта в MS SQL Management Studio выдает ошибку «В указанном DSNархитектура драйвера и архитектура приложения не соответствуют друг другу.»у Вас возникает при работе в MSSQL. К сожалению, мы не подскажем пути решения. На сайте microsoft.com есть рекомендация по запуску либо для 64-разрядной версии либо 32х разрядной. Попробуйте этот вариант.

 

Heldar


Пользователь

Сообщений: 3
Регистрация: 08.06.2018

#8

01.10.2018 19:15:26

Помогла установка odbc-драйвера версии x86, т.к. MS SQL Management Studio оказалось именно данной архитектуры  :smile:  

 

Sequtan


Пользователь

Сообщений: 2
Регистрация: 30.07.2019

#9

31.07.2019 00:42:06

Цитата
Alexey Ivannikov написал:

Цитата
Олег Лефлер написал:

Цитата
Alexey Ivannikov   написал:

Цитата
Олег Лефлер   написал:
ОС Win10-х64. Квик вер.7.14.1.7

Догадываюсь почему возникает такая ошибка, но не знаю как решить. Подскажите пожалуйста.

Добрый день.

Необходимо использовать администратор источников данных, расположенный по адресу: %windir%syswow64odbcad32.exe

А как конкретно его использовать, можете уточнить?

Удалите ранее настроенный DSN источник, запустите из командной строки %windir%SysWOW64odbcad32.exe
Создайте там новый DSN источник с тем же именем. Дело в том, что на x64 системах существует две программы по настройки ODBC. Одна в папке %windir%System32, а другая в папке %windir%SysWOW64. Использовать нужно ту, которая в SysWOW64, а по умолчанию ярлык в Пуск — Панель управления — Администрирование  ссылается на System32. Потому и не работает. Почему именно так а не иначе, вопрос к Microsoft.

Вполне понятно почему. Так как QUIK является 32-разрядным приложением, то используются источники, которые настраиваются через утилиту %windir%SysWOW64odbcad32.exe, а если бы было 64-разрадным, то использовались те, что настраиваются через утилиту %windir%System32odbcad32.exe. Давно пора обновляться на 64-бита.

Страницы:
1

Читают тему (гостей: 1)

Did you create a DSN, but your application cannot access the DSN?

I created a DSN, but could not connect via SSIS. It seems that the DSN I created was 64-bit, while the application I was using (SSIS) could only connect to 32-bit DSNs.

After some research I have realized that there are two different ODBC Administrator runtimes on a 64-bit machine.

The first ODBC Manager is used to manage 64-bit data sources, while the second is used to manage 32-bit data sources.

If you are running a 32-bit Operating System, you will have only 32 bit drivers installed. If you are using a 64 bit machine, the default ODBC Manager will be for 64-bit data sources.

Use this ODBC Manager to Review 64-Bit Data Source Names

c:windowssystem32odbcad32.exe

Use this ODBC Manager to Review 32-Bit Data Source Names

c:windowssysWOW64odbcad32.exe

If you are trying to access a DSN in your application and receive the error “ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application” check to see if you have a DSN configured for the architecture of your application ( 32-bit / 64-bit ).

I create my DSNs twice – once for 32 bit architecture and once for 64 bit architecture. My naming convention is as follows:

  • DSN_NAME_64 created using c:windowssystem32odbcad32.exe
  • DSN_NAME_32 created using c:windowssysWOW64odbcad32.exe

Good Luck

Published by john.dacosta

I am a Database Consultant based in South Florida. I specialize in SQL Server Development and Administration. I have worked on projects including data archival, log shipping, SQL Server installation, performance tuning, database mirroring, disaster recovery and more recently data integration. Currently my role as a consultant has had me add focus to the particularly important subject of Documentation, Quality, Timeliness and Cross-Training within the realm of Technology Delivery.
View all posts by john.dacosta

Published
2011-10-272013-02-05

Содержание

  1. ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch
  2. Troubleshooting
  3. Problem
  4. Symptom
  5. Cause
  6. Environment
  7. Diagnosing The Problem
  8. Resolving The Problem
  9. Error im014 microsoft диспетчер драйверов odbc
  10. Answers
  11. All replies
  12. Error im014 microsoft диспетчер драйверов odbc
  13. Вопрос
  14. Ответы
  15. Все ответы
  16. Error im014 microsoft диспетчер драйверов odbc
  17. Answers
  18. All replies
  19. Error im014 microsoft диспетчер драйверов odbc
  20. Вопрос
  21. Ответы
  22. Все ответы

ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch

Troubleshooting

Problem

When utilizing a 32-bit ODBC driver on a 64-bit platform to connect to an IBM Informix database server, an ODBC application will fail to connect indicating that there is an architecture mismatch.

Symptom

The error message returned from the Microsoft ODBC Driver Manager states: ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

Cause

The cause of the problem is that the ODBC application is compiled within Visual Studio and targeted as ‘Any CPU’ which means the application will run on either a 32-bit or 64-bit platform. The problem with this is that if the application is deployed on a 64-bit platform and utilizes a 32-bit ODBC provider, the application expects to utilize a 64-bit provider.

Environment

Diagnosing The Problem

The best way to diagnose the problem is to use Microsoft’s Process Monitor and filter on the application executable to view what libraries the application is attempting to load prior to the failure.

Resolving The Problem

To resolve the problem, one needs to compile the application within Visual Studio targeted for an ‘x86’ CPU. This will ensure that the application attempts to load the 32-bit ODBC provider instead of the 64-bit one. You can do this by right clicking on your project and selecting Properties. In the build tab, you will find the Platform Target (ANY CPU, x86, x64 or Itanium).

Источник

Error im014 microsoft диспетчер драйверов odbc

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

Answers

To manage a data source that connects to a 32-bit driver under 64-bit platform, we use C:WindowsSysWOW64odbcad32.exe. To manage a data source that connects to a 64-bit driver, we use C:WindowsSystem32odbcad32.exe.

Generally, if we use the 64-bit odbcad32.exe (C:WindowsSystem32odbcad32.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:

To resolve this error, we need to use the 32-bit odbcad32.exe (C:WindowsSysWOW64odbacad32.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.

Regards,
Mike Yin

If you have any feedback on our support, please click here

Mike Yin
TechNet Community Support

You have to note that SSRS is independent from IIS.

I have a SQL 2012 running in what I think is 64 bit on 2008 O/S. I have a data source that MUST be and uses, 32 bit ODBC successfully setup on the box. I have a report on my machine, hitting the data on my 32 bit ODBC connection. When I push the SSRS connection out to my server, I setup the connection to use the ODBC connection and I get error below. Now, I need to know if I can configure SSRS to use 32 bit ODBC or must I install 32 bit SSRS.
I see some say 2012 will use either, old versions you had to use either, but nobody has been very specific as to how to configure or use 32 bit. Also, on my SQL 2012, I cannot seem to create a Linked Server via this 32 bit ODBC connection that works, so any suggestion would be appreciated. Thanks in advance.

ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

Источник

Error im014 microsoft диспетчер драйверов odbc

Вопрос

I have created the Excel 2007 DSN using SysWOW64Odbcad32.exe. I am trying to create the Data Sourse in SSRS 2008 report server, but am getting this error

ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

I can not install the 32bit Excel 2007 on Windows Server 2008, as we are not supposed to use it.

Please help in solving this error.

Ответы

Thanks for your post.

According to your description, you would to take use of ODBC data source to extract data from excel file and show it on report, I would suggest use ODBC data source Administrator to create the relevant DSN of the data source to associate your excel file, and then refer to the DSN as data source into your report. More details steps, please refer to the link below:
Using Excel as a Reporting Services datasource

TechNet Community Support

Все ответы

I have downloaded & installed the exe fromt the below link and the 64 bit drivers are available now.

After creating the DSN for excel, I got new error as below while testing connection

ERROR [HY024] [Microsoft][ODBC Excel Driver] ‘(unknown)’ is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. ERROR [IM006] [Microsoft][ODBC Driver Manager] Driver’s SQLSetConnectAttr failed ERROR [HY024] [Microsoft][ODBC Excel Driver] ‘(unknown)’ is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.

Any help in resolving this issue is appreciated.

Источник

Error im014 microsoft диспетчер драйверов odbc

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

Answers

To manage a data source that connects to a 32-bit driver under 64-bit platform, we use C:WindowsSysWOW64odbcad32.exe. To manage a data source that connects to a 64-bit driver, we use C:WindowsSystem32odbcad32.exe.

Generally, if we use the 64-bit odbcad32.exe (C:WindowsSystem32odbcad32.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:

To resolve this error, we need to use the 32-bit odbcad32.exe (C:WindowsSysWOW64odbacad32.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.

Regards,
Mike Yin

If you have any feedback on our support, please click here

Mike Yin
TechNet Community Support

You have to note that SSRS is independent from IIS.

I have a SQL 2012 running in what I think is 64 bit on 2008 O/S. I have a data source that MUST be and uses, 32 bit ODBC successfully setup on the box. I have a report on my machine, hitting the data on my 32 bit ODBC connection. When I push the SSRS connection out to my server, I setup the connection to use the ODBC connection and I get error below. Now, I need to know if I can configure SSRS to use 32 bit ODBC or must I install 32 bit SSRS.
I see some say 2012 will use either, old versions you had to use either, but nobody has been very specific as to how to configure or use 32 bit. Also, on my SQL 2012, I cannot seem to create a Linked Server via this 32 bit ODBC connection that works, so any suggestion would be appreciated. Thanks in advance.

ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

Источник

Error im014 microsoft диспетчер драйверов odbc

Вопрос

I have created the Excel 2007 DSN using SysWOW64Odbcad32.exe. I am trying to create the Data Sourse in SSRS 2008 report server, but am getting this error

ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

I can not install the 32bit Excel 2007 on Windows Server 2008, as we are not supposed to use it.

Please help in solving this error.

Ответы

Thanks for your post.

According to your description, you would to take use of ODBC data source to extract data from excel file and show it on report, I would suggest use ODBC data source Administrator to create the relevant DSN of the data source to associate your excel file, and then refer to the DSN as data source into your report. More details steps, please refer to the link below:
Using Excel as a Reporting Services datasource

TechNet Community Support

Все ответы

I have downloaded & installed the exe fromt the below link and the 64 bit drivers are available now.

After creating the DSN for excel, I got new error as below while testing connection

ERROR [HY024] [Microsoft][ODBC Excel Driver] ‘(unknown)’ is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. ERROR [IM006] [Microsoft][ODBC Driver Manager] Driver’s SQLSetConnectAttr failed ERROR [HY024] [Microsoft][ODBC Excel Driver] ‘(unknown)’ is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.

Any help in resolving this issue is appreciated.

Источник

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Odbc error hy008
  • Odbc error data source name not found and no default driver specified
  • Odbc error backup exec
  • Odbc error 3146
  • Odbc error 08001

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии