I downloaded the latest version of SQL Developer (4.1.2) to a just-provisioned, pristine server running Windows Server 2012 R2.
I downloaded sqldeveloper-4.1.2.20.64-x64.zip, unzipped it, and placed it under c:\program files\sqldeveloper-4.1.2.20.64-x64\. I double-clicked the main sqldeveloper executable and expected it to "just work" (as it usually does), but this time it didn't.
I got the following error message:
sqldeveloper64W.exe - System Error
The program can't start because MSVCR100.dll is missing from your computer. Try reinstalling the program to fix this problem.
I searched the disk and found a copy of msvcr100.dll at C:\Program Files\sqldeveloper-4.1.2.20.64-x64\sqldeveloper\jdk\jre\bin\msvcr100.dll.
I then copied the above file to C:\Program Files\sqldeveloper-4.1.2.20.64-x64\sqldeveloper\sqldeveloper\bin\msvcr100.dll
I then double-clicked the main sqldeveloper executable again, and this time it started without errors.
Thanks for the workaround. Worked perfectly. This seems to be a change from previous version of SQL Developer which did not have this issue.
ReplyDeleteThanks, a simple fix that worked.
ReplyDeleteOk. Thanks you!!
ReplyDeleteGreat post! Thank you very much!!
ReplyDeletegreat! that work!
ReplyDeleteTHANKS IT WORKED!!
ReplyDeleteMuchas gracias, funcionó!!!
ReplyDeleteWorked for me as well. Thanks for posting this workaround.
ReplyDeleteThis also works for sqldeveloper 4.1.3.
ReplyDeleteThanks a lot!
Thanks! It worked!!!
ReplyDeleteThanks man !!
ReplyDeletethanks.. it worked ..
ReplyDeleteThanks a lot!! It worked!!
ReplyDeleteI was skeptical but this worked an absolute treat! Thank you ever so much.
ReplyDeleteThank you!.....
ReplyDeleteThanks, Dude
ReplyDeleteIt's Working...
Thanks a lot ! it worked for me !
ReplyDeleteTHanks a lot Sir, this worked for me :-)
ReplyDeleteTHANK YOU
ReplyDeletesuperb!!!!!! works perfect...
ReplyDeleteThanks! but instead of copying DLLs around, its better to put the path to the dll (C:\Program Files\sqldeveloper-4.1.2.20.64-x64\sqldeveloper\jdk\jre\bin) in system PATH variables through the environment variables screen.
ReplyDeletethe effect is same - the issue is fixed without copying DLLs around.
Regards,
Jaimini Ram
Awesome!! thank you
ReplyDeleteas per indian saying no Guru..no Knowledge...worked like a charm...
ReplyDeleteThanks, worked like a charm!!
ReplyDelete