posts - 76, comments - 26, trackbacks - 0

Cleaning up after a rough week with Oracle

I had a pretty rough week attempting to get the Oracle client installed on my Windows 7 – 64bit machine.  I’m going resist the temptation to throw stones, but let’s just say it was a frustrating week.

Today I went to the Server Explorer in Visual Studio 2008 to do some work with the ADO.NET Entity Framework.  When attempting to connect the designer to my local SQL Server, I immediately received this

An unexpected error occurred in the Oracle Data Provider for .NET.  Please contact the provider vendor to resolve this problem.

image

Siiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiigh

Even though I’ve uninstalled every trace of Oracle from my machine from the Add/Remove Programs dialog, Oracle seems to have failed to cleanup after itself and it’s still left some damaging residue in my registry.

It took a while and some googling to figure this out, but the solution is to find all occurrences of the following GUID in your Windows registry and delete each one.  I found about 25 of these.  After deleting them all and restarting Visual Studio, it looks like I’m back in business.

D601BB95-E404-4A8E-9F24-5C1A462426CE

Print | posted on Sunday, February 14, 2010 5:18 PM | Filed Under [ visual studio ]

Feedback

Gravatar

# re: Cleaning up after a rough week with Oracle

could this be by design that Oracle runs like crap on a Windows machine.
3/16/2010 10:10 AM | dan ramler
Gravatar

# re: Cleaning up after a rough week with Oracle

Well, I'm not going to make any accusations in that regard, but I think it's undeniable that they've invested next to nothing on the install experience for Windows. Installers in 1995 were more polished and user friendly.
3/16/2010 10:45 AM | kellyb
Gravatar

# Dr

I am getting the same error as above when I installed ODAC112011beta on VS 2010 RC. This error could be either because of VS2010 or the Oracle Data Provider installation. Now that VS is Extensible (similar to Eclipse) the burden is with the end users to decipher whether the error is in ODP.NEt or VS2010 extensions pkgdefs
5/2/2010 7:46 AM | LCACM

Post Comment

Title  
Name  
Email
Url
Comment   
Please add 3 and 4 and type the answer here:

Powered by: