|
We have been using the built in msi for SQL Anywhere 12.0x without incident for a few years, an have noticed recently, that the drivers will not install properly on a 32 bit machine - thus the ODBC connectivity test will not work. Has anyone run into this problem? And if so, how did you solve it. |
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 18 Dec '15, 12:51
question was seen: 2,406 times
last updated: 18 Dec '15, 16:43
Can you elaborate on what you mean by not install properly?What error do you get testing connectivity?
It says that Component not found in the registry. We have seemed to trace this to .Net 2.0 not being installed, but even after we go to Windows Control Panel Add Features, we see that the .Net 3.51 IS installed along with the 2.0 versions.
We think there was some patch applied by Microsoft that is interfering. At first we thought it was new machine, where .NET 2.0 was not getting installed, but that is not the case after others with older machines have run into the issue. The dialog box has a header that says Driver's ConfigDSN, ConfigDriver, or ConfigTranslator Failed, and then the message "Errors Found:" Component not found in the registry.