windows10 about SAS9.4 ERROR: The Java child process terminated unexpectedly: status -1073741502.

[Surface]

I recently installed SAS 9.4 on windows10 (1703) several machines for my computer. Installation display is successful. The error in the log that I get when I open SAS is ERROR: The Java child process terminated unexpectedly: status -1073741502. ERROR: Failed to attach to Java during SAS startup. I have tried to Reinstalling to see if it would repair. also use Java Runtime Environment hotfix . But all were failed. I have no idea. Please help Thank you.

Editor's update: this is a known issue with Windows 10 Creators Update and SAS 9.4m3 and later.  See: SAS Note 60323: Java errors due to the Windows 10 Creators Update might occur when you invoke SAS and the solution in this topic.

[Mordicus]

I am also having JAVA problems win 10 x64 SAS 9.4 TS1M3
After using for a while after first install, ODS and Java fail.
When I restart SAS it says:
ERROR: The Java child process terminated unexpectedly: status -1073741502.
ERROR: Failed to attach to Java during SAS startup. 

I once was able to fix it by installing the latest hotfix that includes a java update. But it returned.

I then tried the workaround solution you post here. Copied here:

1. Using Windows Explorer, open the following Windows directory: C:\Program Files\SASHome2\SASVersionedJarRepository\eclipse
2. In that directory, locate this file: com.sas.app.launcher.cacheFile
3. Rename the file to com.sas.app.launcher.old.
4. Restart the SAS application.
   
   This solved the problem for a while and now it is back. I noticed that the file is still renamed to .old and a new file was not created, which is what I was expecting to happen based on similar windows fixes. I tried renaming it to .old2. That did not work. I tried renaming it back to the original name. That did not work. I then renamed it back to .old AND THAT WORKED. FOR NOW? Or perhaps the fact that I am closing and opening SAS between each rename is coincidental and that is what is fixing it. 
   
   We obviously need a hotfix for this issue.
   
   This is very frustrating. 
   
   
   

[JWolf]

This is so frustrating, mine was randomly having issues with Java but the problem seemed to get worse and I get the same message.

ERROR: The Java child process terminated unexpectedly: status -1073741502.
ERROR: Failed to attach to Java during SAS startup.

I tried following all the steps described but nothing seems to work temporary or permanently. I even uninstall everything following the procedure and reinstall but the problem still persists.

[SASKiwi]

@JWolf - Are you on SAS 9.4M3 or later and have you applied the hot fix mentioned in this post?

[JWolf]

I'm running 9.4M3, I tried to install the hot fix on both machines but it didn't work however, I installed the windows update and everything is working fine again on one of the machines I'm going to try doing the same thing on the other one with the problem and if that doesn't solve the problem I'll post it.

[hugorm]

I didn´t do a thing. With one of the Winsows 10 updates everything is going right. Running 9.4 (TS1M1).
Make SAS Great Again.

[hugorm]

I did not applied the hotfix.

[art297]

Does the info in the following thread address your problem?: https://communities.sas.com/t5/SAS-Procedures/ERROR-The-Java-proxy-is-not-responding/td-p/149423

Art, CEO, AnalystFinder.com

[Surface]

Thank you for your reply. I tried to do it, but it didn't work.

[MicheleJones]

After recieving this error and reading through the threads you just need to add sas.exe as an exception in your windows defender.  Close out of SAS and open it back up again and your error should go away. 

That is what worked for me anyway. 🙂 

[ccd]

Thanks. But that did not work for me.

[dylsmith]

I encountered this same error code after the most recent Windows update (sigh). I noticed the problem disappeared if I turned off real time protection in Windows Defender, which apparently does not approve of SAS accessing JAVA. So you might try that.

Adding sas.exe to the Windows Defender Antivirus exclusions list appears to have resolved the issue entirely. 

Hope this helps.

[shayne]

Hi dylsmith - since adding sas.exe to the Windows Defender exclusions list several days ago, have you seen the issue reoccur? 

Thanks!

[dylsmith]

Yes, it did recur-I've been meaning to edit my post. However, it continues to be the case that SAS launches normally with no errors if I turn off Windows Defender prior to launching SAS.

[shayne]

Thank you for providing that additional information! If you are willing to work on troubleshooting the issue with SAS Technical Support, please open up a track by sending an email to support@sas.com with a screen shot of the SAS Log showing the error message. 

SAS is continuing to work on identifying the cause of this behavior and a way to consistently/permanently resolve it. I will update this thread once I have more information to share.