Lỗi version mismatch between driver and daemon windows năm 2024
|
-[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application Symptoms: Error appears when attempting to connect to an ODBC data source. Even though ODBC connection test tests successfully in ODBC Data Source Administrator. Cause: This error can occur if the ODBC driver you are using does not match the bit level of erwin Data Modeler. So for example, if the ODBC drivers are 32 bit and erwin Data Modeler is 64 bit, or vice versa. This error can also occur if you use the wrong version of ODBC Administrator to try to configure an ODBC driver that does not have the same bit level. Resolution To manage a data source that connects to a 32-bit driver under a 64-bit platform, use c:\windows\sysWOW64\odbcad32.exe. To manage a data source that connects to a 64-bit driver, use c:\windows\system32\odbcad32.exe. Also make sure that whatever bit level is used for your ODBC driver, be sure to use the same matching bit level for Data Modeler. So always use 64 bit drivers with 64 bit Data Modeler and 32 bit drivers with 32 bit Data Modeler. Sorry, I am not very clarify with your question. Are you mean you try this with SQL Server and Oracle, both failed? If yes, you will get this error if you attempt to do the following on a 64-bit Windows machine:
To resolve this, please refer to Managing Data Sources to get more details. If I have misunderstanding your question, please feel free to let me know. When accessing the VDP server through ODBC, it is necessary to make sure the architecture of the driver and client application are the same. Select the 32 bits or the 64 bits version of the ODBC driver depending on the client that will use it. E.g., a 32 bits client such as Microsoft Excel 2003 can only use a 32 bits ODBC driver, even if it is running on a 64 bits O.S. When there is an architecture mismatch, the result will be an error message similar to the following: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application. References Disclaimer The information provided in the Denodo Knowledge Base is intended to assist our users in advanced uses of Denodo. Please note that the results from the application of processes and configurations detailed in these documents may vary depending on your specific environment. Use them at your own discretion. For an official guide of supported features, please refer to the User Manuals. For questions on critical systems or complex environments we recommend you to contact your Denodo Customer Success Manager. QuestionsAsk a questionYou must sign in to ask a question. If you do not have an account, you can register here Same problem here. I had the "failed to open config key" problem, solved it by going into Safe Mode and installing SPTD there, then booten in normal mode, installed DT 4.03-x86. When I'm trying to start the program, I get the Driver version mismatched error. I'd like to mention that I had DT version 4 running OK, then I changed my motherboard, and reinstalled Windows using the Repair option. DT stopped running after that, so I unistalled it, when I tried to install it back, I got the failed to open config key error. DT 3. latest worked ok. Today, as I said above, I solved the config key error and now I'm getting this error instead. If not a solution, then I'd at least want to know which drivers is DT refering at? Sorry, I am not very clarify with your question. Are you mean you try this with SQL Server and Oracle, both failed? If yes, you will get this error if you attempt to do the following on a 64-bit Windows machine:
To resolve this, please refer to Managing Data Sources to get more details. If I have misunderstanding your question, please feel free to let me know. |
