This content has been marked as final. Show 9 replies
Did you see if Windows 7 is supported?
Windows 7 has only one thing going for it ... they changed the name from Vista II.
If you can not get a real operating system XP or Linux then uninstall and download the full version with its own JVM.
I have to confess I do not understand anyone having Windows 7. Once we got past the contrived marketing-hyperbole
there hasn't been real-world good experience reported by anyone doing serious work that has made it to my desk.
You have downloaded the 64bit version of SQL Developer.
To use this you require the 64bit JDK (on a 64 OS, with 64bit CPU).
C:\Program Files (x86)\... are 32 bit programs.
Download the 64bit JDK which should install into C:\Program Files\...
SQL Developer Team
It worked when i followed your instructions.
I am having the same problem, but I havent been able to find the jdk for 64 bits, could you please tell me in what web page you downloaded it?
Thanks for your help
Any search engine like Google can help you find anything.
The version of SQL Developer actually depends on the version of Java you are running, not the version of Windows. For example, I run Windows 7 64-bit, but for compatibility with some other programs that I use, I run standard 32-bit Java. The 32-bit version of SQL Developer runs just fine on my computer, but the 64-bit version of SQL Developer does not. The 64-bit version of SQL Developer gives me the error message indicated by the original post.
It's easy question.
1. find msvcr71.dll from google.
2. copy and paste to C:\windows\system32
3. run again.
I use Windows7 professional, JAVA 1.6, Sql developer 22.214.171.124(JRE included)
It works perfectly.
Guys, May be a old post.
But if some1 comes accross this again : here are the solutions :
Thanks for posting both solutions. A slight variation on the second solution is what I usually recommend: copy the DLL to the directory containing the sqldeveloper.conf file, where the lower-level exe's are located rather than the top-level exe's directory.
The first solution is OK for those willing to modify the Windows registry, and who keep only one release of SQL Developer installed at any given time. If you have two or more, use the second solution as needed.