Fixing a “Java failed to start during the SAS startup” Error in PC SAS

By | March 9, 2015

SASI have many different types of software installed on my PC, and Java is required by the majority of them. This shouldn’t be a problem, but unfortunately each of those applications require different Java versions. Again, this shouldn’t be a problem either, but applications respond differently to the presence of newer (or older) versions that they expect.

After installing and uninstalling various versions of Java while troubleshooting, I started PC SAS 9.3 to work on a project. The first three lines were errors:

Java proxy error

A search of quickly provided an answer in Installation Note 44853. When I installed SAS on my PC, I chose to use an existing version of Java, which was Java 6 Update 26, the organization standard. In subsequent months I installed Version 7 Update 7 and Version 8 Update 25. I intentionally removed Version 6 Update 26 because I knew that my SAS products were compatible with the newer versions. I also wanted to prevent conflicts with other Java-dependent applications on my PC. So much for organization standards.

I submitted proc options option=jreoptions; run; in SAS, and the log showed what I was pointing to Java 6 Update 26 like I expected:

Java version and location

To fix this problem I needed to edit my sasv9.cfg file located at
C:\Program Files\SASHome\x86\SASFoundation\9.3\nls\en\sasv9.cfg. I just needed to change the -Dsas.jre.libjvm line to point to my current version of Java (8 Update 25):sasv9.cfg

There is one more configuration file in the SAS deployment that had to be updated as well. It is the sassw.config in the C:\Program Files\SASHome directory. The JREHOME option needed to point to the new version of Java: C:\Program Files (x86)\Java\jre1.8.0_25\bin\java.exe:


With those changes made to two SAS configuration files, I successfully launched PC SAS without errors:

Launch PC SAS

Leave a Reply

Your email address will not be published. Required fields are marked *