How can I reinstall the common ODBC Drivers in a Windows 2008 Server install

I have a Windows 2008 Server OS install. For some unknown reason, most of the ODBC drivers have simply disappeared. I have no idea how. Just a few months ago I was using a connection to an Access DB accdb and a mdb for some reports. Now they all seem to be gone see images of errors below. Does anyone know how to fix this. How can I reinstall these. Many of my reports and they happen to be Crystal Reports have stopped working. Please advise if you know what I can do and as always thank you for being here.
ODBC-AdminError.png
ODBC-AdminError2ndScrn.png
SystemDSNAdd.png
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bcolladayCommented:
Re-installl Access or do a repair install I would think this would do it.

or :

http://support.microsoft.com/kb/313008
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
When you say do a repair install do you mean with the Window 2008 Server disk or the Office Enterprise CD? Also it would appear that there is a download of the drivers from the link you sent pertaining to Access 2007 which is what we have but we would get those drivers from using an MDAC file install? Is that correct?

0
bcolladayCommented:
I meant a microsoft office install, but it looks like this mdac install 2.6 doesn't contain Access drivers after all. But it is supposed to leave them alone.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

bcolladayCommented:
http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/4054aef6-c404-4cdb-b738-a1fbb10995cc

Basically re-register the odbc dll for access whichever dll that may be.

odcbconf.dll
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
Okay I did that and registered the file. See image.
However it did not work.TThe ODBC is still the same as before. I wonder if I need to be in a different folder since it is Windows 2008 server? Do you know if the file should be registered to a different folder? Or do I need to restart the whole server?


RegisterDLL.png
0
bcolladayCommented:
We have reached the end of my knowledge.  That usually works for me with a different companies odbc driver.  I'll click on the "request attention" flag to get someone else in here.
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
I looked up the files and just wanted to show you they are there. See image. Then I noticed that there was a Windows and Windows.old. I spoke to the Administrator and he said he had not named the Windows.old file and did not know how it got there. He is confused about that as I am. I do not know if that is relevant. The Win 2008 Server install is fairly new around 1 year. Could it be part of a Win 2008 Server install?

ODBCFiles.png
0
LinInDenverCommented:
I encountered the same issue when I attempted my Crystal Reports Server 2008 install on Windows Server 2008. The only ODBC connection I had visible was for MS SQL Server.

The only thing I could determine was the 64-bit OS did not jive with my 32-bit software, including Crystal's Data Direct ODBC drivers (these are only available in 32-bit).

I resolved the issue by re-installing the OS as 2003, 32-bit. Not the best solution for most, but I needed a quick fix!

Maybe you can do some research on locating 64-bit ODBC drivers for Access, etc? Good luck.
0
Jim P.Commented:
You need to do a Start --> Run--> %syteemroot%\syswow\odbac32.exe. Or something similar.

The 32 bit vs. the 64 Bit driver is probably your issue.
0
johnb6767Commented:
In pre 2008 (64bit systems as well), if I had ODBC problems, I would simply import the following key in the registry form a working PC....

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI

Dont do that yet though.....

Do you have another similar server you could at least compare the values with?
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
I won't be able to resort back to 2003 unfortunately.
I should tell you that when this machine was originally setup and Crystal Reports was installed I had not problems with the report setup or running. I am wondering if a recent Windows 2008 Server Update screwed things up ???

I can find odbac32.exe and I can run that and see what happens?

I found this information below actually on EE. Is this what I need to do. If so I am having a hard time following it.
http://www.experts-exchange.com/Database/Miscellaneous/Q_25273368.html
 
It points to this link at the bottom of the page.

http://msdn.microsoft.com/en-us/library/ms724072%28VS.85%29.aspx

My problem is understanding and following what I need to do. Any translation or interpretations are appreciated.
 
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
I do not have a server to export this to to test. Here is what I found when I looked at the
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI      See Image below.

How dangerous is this to export from my Windows 2003 Server to my clients 2008 server. My personal machine has all the drivers. Also if I export based on your advice ( I am responsible for the outcome I am aware ) If I export that "selected branch" , when I go to import it does it know to place it in the same location on the new machine? Like this:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI

In other words I do not have to do anything different to import it other than just point to the exported file click import and it will do the rest? Do you know if I need to restart or anything like that?

Regedit-ODBCINSTWin2008Serv.png
Win2003Ser-ODBCINST.png
0
Jim P.Commented:
Unfortunately, I don't have a 64 bit server to play with.

As far as the MS Oracle db Provider -- all it is, its a shell over the the Oracle ODBC Provider. If you don't have the Oracle driver loaded, it doesn't work.
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
All I need are the Microsoft Drivers for Access and Excel. I guess worse case scenario is if I backup the registry and then try it and id does not work the worse thing is that everything fails I should be able to simply restore the registry? Does that sound about right?
Also if I do the import of just the ODBCINST selected branch does it replace only the registry keys for that folder...? I just want to make sure does anyone know if this is what happens? I have gotten as far as the import registry files and to the open the file but I have not opened it officially. One more thing, currently in the C:\Windows\sysWow\ I copied the ODBCcad32.exe into that folder but there was already a file called GDIPFONTCACHEV1.DAT. I hope I am not messing something up by making these moves..? Any thoughts on that?
0
johnb6767Commented:
"If I export that "selected branch" , when I go to import it does it know to place it in the same location on the new machine? Like this:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI"

Yes. As long as you only export that ODBCINST.INI subkey.....

"GDIPFONTCACHEV1.DAT"

Dont worry about that file.....

" I guess worse case scenario is if I backup the registry and then try it and id does not work the worse thing is that everything fails I should be able to simply restore the registry?"

Yes, just that key though.....
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
I started trying to register some of the files and I got this error. Does anyone know what this means. I googled it and found little pertaining to my issue. Here is the error message

Register-Error.png
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
This is what I get when I try to register the second file. Any thoughts.

2ndRegistryError.png
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
Does anyone know if you are supposed to import the registry keys and have the DLL files in the proper place before I go in and register the files with regsvr32?

I tried to import the file into the registry and I got an error seen below. How can I determine what file is being used. The only thing I can think of is MS Access is being used by other users on the network but I do not know if that is a factor. The ODBC Drivers section of the registry is as empty as the first image at the beginning of the question.

Does anyone have anymore thoughts or is this about as far as we can go?



RegistryEditorError.png
0
Jim P.Commented:
Well on further reading of the MSDN link it was redirecting your ODBC call when you were using the syswow ODBCAD32 to create the registry keys from one set of keys to another.

Also did you have an app running when you tried to register them?


http://msdn.microsoft.com/en-us/library/ms724072%28VS.85%29.aspx
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
Okay here is what I did. I am not sure if I had any apps running. When you say apps running do they have to be present on the desktop and open for them to be technically running or could they be running in the background without my knowledge. If so where do I look for the apps to be running.
Also I am putting up what does show up when I try to setup a connection using Crystal Report. I am clear this has nothing to do with Crystal Reports I have spent 12 years working with it.
Here is the ODBC Admin and it shows many of the connections present but none of them work. Then what I get is an Error 193 when I try to connect. Remember this is on a Windows 2008 Server machine. MS Access was reinstalled and there were no changes other than the DLLs now show up under the ODBC Admin which I suspected would as I copied the files from one server Win2003SBS to the Win2008Server. To the appropriate folder. Listed above. Any more ideas. It seems like I am close yet so far?

CrystalConnectionfailed.png
ODBCAdminNowShowsUp.png
ErrorCode-193.png
0
Jim P.Commented:
Delete -- refund.
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
Through a combination of your support, I got the darn thing to work honestly I do not know for sure which combo did it. I left this question and forgot about it. I am truly sorry. You deserve the points though for sure. Again very sorry.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.