[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 743
  • Last Modified:

MyODBC driver doesn't appear in driver list

Hi there,

I have installed MyODBC3.51.8 and MySQL 4.0.20d on my system (Windows2K+SP4). However, after the installation, the MyODBC driver doesn’t appear in the driver list of ODBC Data Source Administrator. I removed them and installed them, the problem insists. It makes it impossible for my to use the MySQL.

From the document on the Internet, the installation of MyODBC is simple and easy, why I got such problem? Any idea?

Thank you,

Anlee
0
Anlee
Asked:
Anlee
  • 3
  • 3
1 Solution
 
ajaikumarrCommented:
Hai,

Check this
1. Go to winnt\system32 folder and check you have myodbc3.dll exist. if exist goto step 4
2. if not Under the registry HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ you should have [MYSQL ...] if it does not created please make sure you have permission for the installing user.
3. Run RegEdt32 goto above registry entry (ODBCINST.INI) and click on Security and provide permission for the user as read & write.
4. Sample Registry entry if you export the key (or you can import this to your registry)
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\MySQL ODBC 3.51 Driver]
"UsageCount"=dword:0000000c
"Driver"="C:\\WINNT\\System32\\myodbc3.dll"
"Setup"="C:\\WINNT\\System32\\myodbc3.dll"
"APILevel"="2"
"ConnectFunctions"="YYN"
"DriverODBCVer"="03.51"
"FileUsage"="0"
"FileExtns"="*.txt"
"SQLLevel"="1"
"CPTimeout"="60"
"DSNHelpFile"="C:\\WINNT\\help\\my3dsn.hlp"

<Make sure you have a blank line at end of file in your importing registry file (.reg file)>
5. restart your system and check

Hope this helps your.
0
 
AnleeAuthor Commented:
ajaikumarr:

Thank you for your idea. I checked the system32 directory for myodbc3.dll, the file is there, and I checked system registry, the key has the values as below:

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\MySQL ODBC 3.51 Driver]
"UsageCount"=dword:00000001
"Driver"="C:\\WINNT\\System32\\myodbc3.dll"
"Setup"="C:\\WINNT\\System32\\myodbc3.dll"
 
then I imported your sample reg file. Checked the key values are imported successfully. Than, rebooted my system, checked the ODBC Administrator. The MyODBC is still not in the Driver list.

What can I do to resolve this?

Anlee
0
 
AnleeAuthor Commented:
I seems cannot resolve this problem. I believe  someone here should have had the same experience as I. Please let me share your idea.

Anlee
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
ajaikumarrCommented:
Hai,

I had read some where that this kind of problems had occured for somebody... What he did was he just exports the registry HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ with it subdirectories and then removed the original registry entry and then he imported the same from the file... That works well for him...

Bye
Ajai
0
 
AnleeAuthor Commented:
It works. Thank you very much!

Anlee
0
 
ajaikumarrCommented:
Hai,

Happy to hear that it works for you... Most welcome.

Bye
Ajai
0
 
samadenbaumCommented:
I'm had a similar problem and exporting the registry and importing didn't work.  However after exporting ODBC entry in the registry file, I inspected the text version.  In the [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers] list of drivers, I found an entry @="" three lines from the bottom.  My mySQL entry was below this.  I don't know the significance of the @=, so I moved it to the end of my list.  I reimported the ODBC and I now had three new drivers in my list.

0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now