Tagjava

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

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 support.sas.com 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:

sassw.config

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

Launch PC SAS

Email this to someoneTweet about this on TwitterShare on LinkedInPin on PinterestShare on Google+Share on FacebookPrint this page

SAS Web Report Studio in a Headless Configuration

saslogo We ran into a problem recently in SAS Web Report Studio 3.1 where our web reports that contained graphs produced java errors while our table-only reports did not.  Our platform is SAS Enterprise Business Intelligence Server 9.1.3 Service Pack 4 running Solaris 10 on Sun SPARC Servers.  Our web server is Apache Tomcat 4.1.18.  The error we received looked like this:

Error messages:There is a problem with the current page. Error Rendering the Report
 
Root Cause: java.lang.NoClassDefFoundError
  at com.sas.servlet.tbeans.graphics.BaseBarChart.(BaseBarChart.java:23)
  at com.sas.servlet.tbeans.olapgraphics.html.OLAPBarChart.(OLAPBarChart.java:83)
  at com.sas.servlet.tbeans.olapgraphics.html.OLAPBarChart.(OLAPBarChart.java:74)
  at com.sas.servlet.tbeans.olapgraphics.html.OLAPBarChartComposite.(OLAPBarChartComposite.java:57)
  at com.sas.servlet.tbeans.olapgraphics.html.OLAPBarChartComposite.(OLAPBarChartComposite.java:43)

 

I contacted SAS tech support and they had the answer instantly.  When running in a headless environment (a server that does not have a display (monitor) attached to it), Tomcat requires the following option in its startup script:

Djava.awt.headless=true

 

Once I added the option to the Tomcat startup script and restarted Tomcat and SAS Remote Services, no more errors and we were getting our graph output in Web Report Studio again.

Email this to someoneTweet about this on TwitterShare on LinkedInPin on PinterestShare on Google+Share on FacebookPrint this page

SAS Web Report Studio 3.1 Doesn’t Like Newer Browsers

SAS developed Web Report Studio (9.1.3 BI Server installation) for Internet Explorer 6.0. I have used IE 7.0 and Firefox 2.x and 3.x with Web Report Studio and ran into a few different Javascript errors. These errors don’t necessarily make Web Report Studio completely unusable, you just have to know what NOT to do. To save everybody from having to learn what not to do, you have a couple of options. You could stick with IE6.  How old is that technology?  I recently ran across another option which utilizes Firefox as the browser at the SAS BI-ogsource (http://sas-bi.blogspot.com/2007_08_01_archive.html):

IE 7 Headaches – Try Firefox

Once you have mistakenly loaded IE 7 and can no longer use the SAS web applications, you’ll find that reverting back to IE 6 will take an act of congress. (Really, and you know how slow they are.)

Use Firefox and install their IE tab. You can download it from the site:

https://addons.mozilla.org/en-US/firefox/browse/type:1

posted by Angela Hall @ 8/26/2007 0 comments

I installed the IE Tab Add-On in Firefox and Web Report Studio works just like I’m running IE6 (probably even better). In the options for IE Tab, I had to include my Tomcat server name and port in the sites filter so Firefox knows when to use the add-on.

Like many of the SAS promises, IE7 and FireFox support should be included in the 9.2 version of BI Server, so maybe everything will work like it is supposed to in a few months.  9.2 is shipping in Q1, right?

Email this to someoneTweet about this on TwitterShare on LinkedInPin on PinterestShare on Google+Share on FacebookPrint this page

© 2017 Technoleros

Theme by Anders NorénUp ↑