Notice you now have two folders called ClientTools, the first one is where some 64 Bit compiled applications are, and the one with the (x86) are where the majority of the client tools are installed, specifically the management studio and the business intelligence development studio.Ĭopy, Paste, and Rename the entire ClientTools (x86) folder as follows: What you would end up with after the installation is complete is this: Let's say for the client tools you chose an install path and folder name as follows: You can either accept the defaults which go to the C: drive or you can choose another drive and custom folder name. When you go through the SQL Server installation you have a choice of where to direct the installation of the database services, the data files, and the client components. There are a couple of workarounds to this and neither are very pretty or what you would want to do in production, but here is a simple workaround that will at least allow you to connect to Oracle and import some data. When you attampt to import data from within the management studio, the data import wizard (DTSWizard) is passing a string to the Oracle provider with (x86) in the string, this exposes a networking bug in Oracle and it breaks on the parenthesis. The majority of the management studio is compiled as a 32 bit application so that is why the (x86) is being appended to the folder where the studio is being installed. There is no control over this path name at install time because the SQL Server install routine is doing it. I ran into the same problem, the issue as was previously mentioned is because the client components (management studio) are installed into a folder with (x86) in the folder name.
0 kommentar(er)
