SQL Developer

Interesting.  Java 8 and 11 are both LTS releases, and so far I have ignored the other Java releases, sticking with Java 8 for SQL Developer, with 8u221 as my latest update.

Upgrading to 8u261, I see the same problem you experienced. But  running 20.2 with jdk-11.0.8 works fine. Neither 8u261 or 11.0.8 ship with any msvcr*.dll files.

I recall that some components / extensions of SQL Developer may still require Java 8 so, pending new, detailed guidance from the SQL Developer team, I would recommend staying with 8u251 or lower.

Cheers

Edit:  This dependency change is also mentioned in the Java 8 release notes: https://www.oracle.com/java/technologies/javase/8u261-relnotes.html

Hi Glen,

Thanks - I also saw the update in the relnotes.

As mentioned, for SQL*Dev I can happily stay on 8u251.

But I wish to understand the problem (and eventual solution) better, as it may affect othe Oracle product lines installed at my customer. For the moment I may just recommend to not go above 8u251 until I know what's cooking.

Fortunately in this scenario, but JDK and SQL*Dev are Oracle products, so hopefully that will expedite matters.

.. Roelof

Quoting the JDK relnotes:

Native applications (including JNI) that have depended on and assumed the presence of MSCVR100.dll in the JDK/JRE directory will fail to run. When this happens, users will see an error such as:

"The code execution cannot proceed because MSVCR100.dll was not found. Reinstalling the program may fix this problem."

These applications should be rebuilt and shipped with modern C++ runtime dependencies that use a later instance of Visual Studio. Applications should not depend on DLLs included with the JDK/JRE that are not documented in the product as offering support for the specification or other functionality in Java SE.

--------
If I look at the DLLs in the SQL*Developer folder, then by naming it looks like there are several that do native/JNI calls.

Apparently this behavior was described in the Release Notes:

https://www.oracle.com/java/technologies/javase/8u261-relnotes.html

If anyone has not already done so, please file a Service Request with Support and ask that a bug be reported so that this can be fixed.  I've been told that SqlDev Development is already investigating, but having a formal report is a better approach,

So I guess SQL Developer 20.2 gets a pass on this since 8u261 is very new and the download with a bundled JRE uses 8u221.

The 20.2 release notes have an inconvenient warning about the Data Miner and SVN client features requiring Java 8

but if you do not use those, then it looks like Java 11.0.x is the way of the future barring whatever fix it takes to make 20.2 or higher work with 8u261 or higher.

You can't always get what you want.

Hello Sudhakar,

Thank you for your feedback.
I previously tried manually installing MS Redistributable files 2010, which installs msvcr100.dll, albeit not into the JDK folder.

Does SQL*Dev really need this DLL to be inside the JDK? Can the logic be updatedto pick it up from the MS Redistributable installation when not found inside the JDK?

This will be fixed in the next SQLDev update.

In the meantime, use an older JDK or manually copy the dll over.

Thanks all.

In the past (not really sure if that means the recent past or the far past), SQL Developer would not look for msvcr100.dll in the installed JDK (under C:\Program Files\Java). It had to be found somewhere of course, somewhere in a directory present in the PATH environment variable (or in the bundled JDK shipped with SQL Developer as noted in Newbie having problems starting sqldeveloper)).

So before posting my initial answer on Saturday ( ) I made sure msvcr100.dll could be found in PATH, not understanding that the rules have changed!

With 8u261 in the Java 8 series, and the lack of msvcr100.dll there, it is revealed that the search for msvcr100.dll goes specifically to the JDK. No doubt an improvement, as at least we should be assured of getting the expected version of msvcr100.dll and not something else.

Edited.

Cheers

hi all

I faced the same issue but on windows 7 32bit.

I found that .dll file in a windows folder (system folders) and copied it over into the java folde (where the error messages pointed it out). it worked nicely.

from C:\Windows\System32 to C:\Program Files\Java\jdk1.8.0_261\jre\bin

regards

Felipe Quiroz

User_6D1T2 it worked with your approach. Thanks

Next release, 20.4.1, is out, but this issue seems to be forgotten. Workaround mentioned by Jeff still applies. You might find that file under C:\Windows\System32, if not, install other software you'll need first, it might add it there.
Whatever you do, don't download it directly from a random internet site.

you can copy the file(msvcr100.dll) from older java version (jdk1.8_211)

use below command in windows

C:\Program Files\Java\jdk1.8.0_311\jre\bin>copy C:\PROGRA~1\Java\jdk1.8.0_211\bin\msvcr100.dll