ODBC Problems

Question

ODBC Problems

jbrewer

Default port

Points: 1453
More actions
February 7, 2006 at 6:04 am

#89411

SQL Server ODBC is not showing up in SYSTEM DSN after is it created. Everything looks fine when it is created and the test is successful but never appears in the SYSTEM DSN. It is showing up in the registry under ODBC.ini. This problem is only on one PC. Please HELP!!!

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

Brian Fenton SSC-Addicted Points: 429 More actions · Answer 1

On that workstation, do you see an entry in the registry similar to this?

"HKLM\Software\ODBC\ODBC.INI\%ODBCNAME%\Description" with an appropriate string value? Also, make sure the entries are in HKEY Local Machine (System DSN) and not HKEY Current Users (User DSN)

Brian

jbrewer Default port Points: 1453 More actions · Answer 2

We have verified that the information is in the ODBC.ini is correct. We were putting the information under the System DSN. Every looks great and it passes the connection test but it does not appear in the SYSTEM DSN. The user needs the information in to appear in the SYSTEM DSN so that she can see it when she runs Crystal Reports. We have tried everything that we can think of. We appreciate any help that you can give us.

Jeff Gray SSChampion Points: 10667 More actions · Answer 3

Hello,

I think I've seen this one. Good thing you mentioned Crystal, because that made me remember.

Installing Crystal Reports v8 breaks your computer, but there is a fix:

http://support.businessobjects.com/library/kbase/articles/c2007581.asp

You can either d/l their fix, or manually repair the registry permissions. The article has the details. I found it pretty easy to do it manually.

hth

jeff

jbrewer Default port Points: 1453 More actions · Answer 4

Thanks Jeff, We will try this this afternoon and I will report back.

jbrewer Default port Points: 1453 More actions · Answer 5

This is what I have done.

I applied the Crystal patch suggested by Jeff.

Thanks Jeff, but that did not correct the problem.

I have applied MDAC 2.8 SP1

I have Set myself up as a local administrator on the PC and as a doman administrator.

It is still not working. I hope someone has another Idea. All I know to do is rebuild the PC and I hate to do that. Any and ALL Suggestions are welcome.

David Griffiths-273839 Say Hey Kid Points: 663 More actions · Answer 6

I haven't got an answer, except to say you're not going mad - I have exactly the same problem on my PC. I have given up using ODBC Data Source Administrator and now have to edit the registry directly.

Jeff Gray SSChampion Points: 10667 More actions · Answer 7

Jeff Gray

SSChampion

Points: 10667

February 9, 2006 at 7:25 am

#619767

Did you try checking the registry permissions?

jbrewer Default port Points: 1453 More actions · Answer 8

Jeff,

We thought we checked the permissions but please walk us through it so that we are doing it correctly.

Thanks for all your help

Jeff Gray SSChampion Points: 10667 More actions · Answer 9

Open REGEDT32 and list out the permissions on the key (under HKLM/Software/ODBC/ODBC.INI) that matches the DSN that doesn't show up in the system DSN dialog box.

Compare that list with the permissions for one of the DSN subkeys that does work correctly, either on that same machine or another.

Make them the same on the target machine, keping in mind that there may be a different user on the target machine if you are comparing to a different machine.

Optionally, you could grant "Full Control" on the subkey to the everyone group temporarily. If that makes it show up, you are on the right track. You might even want to try this first.

Unfortunately, I don't have a "broken" situation that I can reference to give you more details. I am pretty sure that permissions are the culprit, though. I can't really think of any other scenario that would give the symptoms you describe. It could be a completely hosed up box, but that is less likely.

jeff

jbrewer Default port Points: 1453 More actions · Answer 10

Jeff,

Thank you, you put us on the right track and the problem is now resolved. The ODBC Registry entry was corrupted. We went to a PC that was working and exported the ODBC.ini registry entry and copied the C:\WINNT\ODBC.ini to the computer with the problem. Then we imported the ODBC.ini registry entry to the PC with the problem and replaced the C:\WINNT\ODBC.ini file with the one from the working PC. You have NO IDEA how much I appreciate all your help.