Cannot connect to notes SQL with ODBC Data Source Administrator

I downloaded notes SQL and now I am trying to connect via ODBC Data Source Administrator that comes with Windows XP.

Under the User DSN tab, I click add, then choose Lotus Notes SQL driver, but when I hit finish I get a ‘Microsoft Data Access - "ODBC Administrator has encountered a problem and needs to close. We are sorry for the inconvenience.’

error every time.

Has anyone else experienced this?

What I am trying to do is export email addresses from a nsf into excel.

any assistance is greatly appreciative.

regards,

Bruce Gilbert

Subject: cannot connect to notes SQL with ODBC Data Source Administrator

Hi, I am a developer on NotesSQL @ IBM and have heard of this problem before, only on XP, unfortunately, we haven’t been able to reproduce the problem. Can you tell me, do you log into a domain and do you know if you have administrative privileges on your machine? Are you creating a System DSN or a User DSN. If you are creating a System DSN, try creating a User DSN as a test to see if you don’t have the rights needed to create registry entries in HKEY_LOCAL_MACHINE. I want to try to figure this out so we can notify support and/or make a fix in the driver itself.

Thanks,

Ron

Subject: RE: cannot connect to notes SQL with ODBC Data Source Administrator

Was a solution ever discovered here? I have downloaded the latest NotesSQL driver and I was able to create User and System DSN’s on my Windows 2000 machine. My Windows XP machine is where I’m having this same problem. I could not create a User or System DSN. I do logon to a Domain and I do have admin priviledges to my machine.

Any help is appreciated.

Chris

Subject: RESOLVED: cannot connect to notes SQL with ODBC Data Source Administrator

Resolved my own problem anyway. The solution was almost too obvious. I searched the hard drive for multiple Notes.INI files and for whatever reason there was a blank one under the Windows directory. Deleting this one solved my problem.

Subject: cannot connect to notes SQL with ODBC Data Source Administrator

I’m able to set up DSN’s on WinXP SP2 without a hitch, so there must be a problem with the machine you’re working on. You could try downloading the latest MDAC update from MS and see if that resolves the ODBC error, if that doesn’t do I’d suggest checking your registry entries for the notes client to make sure they point to the actual client install location.

Subject: RE: cannot connect to notes SQL with ODBC Data Source Administrator

thanks for the reponse Nathan. I downloaded the lastest MDAC, restarted my computer and I still get the fatal MS error. This seems to be specific to connecting with the LotusSQL.

How do I do the second part you mentioned? (check the registry entries to make sure they point to actuall client install location).

-Bruce

Subject: RE: cannot connect to notes SQL with ODBC Data Source Administrator

If you’re not familiar with working in the registry I suggest you try uninstalling and reinstalling the Notes client. As long as that completes successfully it will ensure that the registry settings match the install path.

If you do want to check the registry do the following:

Go to the start menu and choose Run. Enter regedit and click OK.

The Registry Editor window will open and give you a standard MS navigator. Expand HKey_Local_Machine, expand Software, expand Lotus, expand Notes and click on the 6.0 folder.

On the right hand side of the screen you’ll see the DataPath key and the Path key. What you want to see in the DataPath key is the Notes data directory location (ie C:\Program File\Lotus\Notes\Data). In the Path key you want to see the location of the Notes executables (ie C:\Program Files\Notes).

If those do not match your install locations then try uninstalling and reinstalling Notes, which should correct the registry keys.

Hope that helps!

Subject: RE: cannot connect to notes SQL with ODBC Data Source Administrator

I followed these instructions and everything looks as it should. I’m still not able to connect to NotesSQL, though. I guess the next option is to reinstall the client and see if that does anything.