what happens if I import registry keys from a selected branch of registry folders and keys from Win 2003 Server to Win 2008 Server

I was told that I should be able to import the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI contents to the same folder which is empty on my clients machine. How dangerous is this to export from my Windows 2003 Server to my clients 2008 server? My personal machine has all the drivers.  ( 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 or put any files in the appropriate location. I was also told about the odbccad.exe file being put in the C:\Windows\sysWow\  folder?

Can anyone verify this? See images below.
Regedit-ODBCINSTWin2008Serv.png
Win2003Ser-ODBCINST.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.

Rob WilliamsCommented:
There is no risk Exporting the keys.
If you click on the exported file it will automatically add the keys, in the same location, and create any 'folders' within the registry if missing. i.e. the locations will be the same.
Rebooting is dependent on the nature of the changes. I would reboot
However, this adds the registry keys and values but does not mean everything will work. For example if a key contains a path to a file or driver the path has to be the same as well. There can be other limiting factors as well.
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:
I looked closely at all the files all were DLL s and I made sure the files were copied over to the appropriate folder on the Win 2008 Server. One of the folders I noticed I could not exactly find was the one that had this path. I will ask to pardon the ignorance in advance.
C:\\PROGRA~1\\COMMON~1\\MICROS~1\\OFFICE12\\ACEODBC.DLL


0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
Opps I hit submit before I was finished typing.
I would assume that the above path translates to :
C:\ Program Files\Common Files\Microsoft Shared\Office 12\ACEODBC.DLL
I am not sure but that is where I placed the Access 32 bit ODBC drivers hoping that will connect? Any thoughts on that?
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Rob WilliamsCommented:
>>"I looked closely at all the files all were DLL s and I made sure the files were copied over"
.dll files also need to be registered as well.. You can do so at a command line using:
regsvr32 <path>
such as:
regsvr32 "C:\ Program Files\Common Files\Microsoft Shared\Office 12\ACEODBC.DLL"
or
regsvr32 C:\ Progra~1\Common~1\Micros~1\Office12\ACEODBC.DLL
Note: if there are spaces in the path you must use quotes, or you can use the DOS equivalent which removes spaces and limits to 8 characters with ~1. I prefer the former

C:\\PROGRA~1\\COMMON~1\\MICROS~1\\OFFICE12\  is created when Office 2007 is installed.
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
So when you say that this is created. I do not see exactly that path.
C:\\PROGRA~1\\COMMON~1\\MICROS~1\\OFFICE12\
what I did see is this:
C:\ Program Files\Common Files\Microsoft Shared\Office 12\ACEODBC.DLL
Are they one in the same? I don't see any folders with a Tilde in them?
0
Rob WilliamsCommented:
>>" I do not see exactly that path.
C:\\PROGRA~1\\COMMON~1\\MICROS~1\\OFFICE12\ "

I don't know why it is displayed with two back slashes  "\\"
But it is the same path just different nomenclature (naming conventions):
PROGRA~1 = Program Files
COMMON~1 = Common Files
MICROS~1 = Microsoft Shared
A DOS name can only be 8 characters and cannot have spaces so some names are shortened to 6 characters and ~1 added.
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
Understood. Thank you. I will register all files. (I have already move and placed them in the appropriate folders) Then I will import the registry folders from the selected branch into the Win 2008 Server.
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
I started to register the files and I got this error. Have you seen this one I got little from Google. What did I do wrong?

Register-Error.png
0
Rob WilliamsCommented:
I am afraid I have no idea of the cause of the error in your scenario.
As mentioned before there is no guarantee this will work. Normally you  require an installer to create the registry keys, install dll files, and any other you may need. In most cases copying from one machine will not work. I have just been trying to answer specific questions as you have presented them. Did the person that suggested; " was told that I should be able to import the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI "  have any other input as to how to achieve this?
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
Here is what I get when I try to register the second file. Any thoughts...?

2ndRegistryError.png
0
Rob WilliamsCommented:
Among other things the 2003 dll's could be different than the required 2008 dll's.
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
Rob WilliamsCommented:
>>"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?"
The dll files must be in place before you register them. If you import the keys first it should not be a problem there will just be errors generated because they are not accessible when called by the app.

As for how to diagnose the error you could run Process Monitor and review the logs for errors. It generates a lot of errors so start the logging just before creating the error and stop as soon as it appears.
http://technet.microsoft.com/en-us/sysinternals/bb896645.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. Which may have been a factor.  When an app is 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
Rob WilliamsCommented:
I a afraid have no others suggestions at this point. as mentioned from the beginning there is no guarantee importing registry keys and such will work. I have tried to suggest how to complete the steps you wish to take, but this in no way indicates the whole process will work. Generally an installer is written to create the registry keys, install and register the dlls, and associate with the appropriate programs, and usually install exe's as well. To bad who ever made the initial suggestion; "I was told that I should be able to " is not available to assist further as I don't know how to pursue from here. Very sorry,
--Rob
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
I do not know if anyone wants to respond to this but I was able to get "thanks to you guys" the ODBC admin to crank out a connection to the datasource.

How I did it I went to the C:\Windows\sysWOW64\odbccad32.exe
I double clicked on the file and it launched and let me create a connection to MS Access to Crystal Reports Yeah Baby Yeah!
Okay so that works my only problem is when I leave the project if someone else gets to take on this work where I left off. How can I differentiate between the 64 bit version which launches under the Control Panel Administrator Tools ODBC launches the 64 bit version. How can I create a separate version maybe in the same location that shows it is the 32 bit version. Is that possible to add that to the Administrator Tools Menu?
I believe as soon as I leave someone will go in and try to build a simple report, not be able to and think I left something screwed up.
0
RUA Volunteer2?Tableau Trainer & Consultant Sales Exec.Author Commented:
Can I create a separate ODBC Admin under Admin Tools so that I can show both the 64bit and 32bit versions. Can that be created under the same menu. I once saw a way to build a simple tool (batch file) inside of Windows Explorer that would allow a user to create a function/macro something ....that let the user copy a list of files from any Windows Explorer folder and print out the list of files. In that respect could the same be done with a separate selection in the drop down list under Administrative Tools Data Sources ODBC so I can have two separate versions on the same menu list.? Any thoughts and thank you for hanging in there with me.
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.