When trying to log on to SAS^® Enterprise Miner™, SAS^® Forecast Studio or SAS^® Model Manager, you might receive this error:

The application was unable to load the SAS environment definitions. 
The file location or file contents might be invalid.  Please contact your
administrator for assistance.

This error occurs when the Web application server is not started. See SAS Note 36986 "Logging on gives an error: 'the application was unable to load the SAS environment definitions...'" for additional information.

One reason that the Web application server is not started is related to the value chosen by JGroups software. The server is not started if the SAS Remote Services application value chosen by JGroups software does not match the value chosen by JBoss Web application server. If these values are not set correctly on the SAS middle-tier, then the communication protocol that is used by JGroups might not function correctly. As a result, the following errors might appear in the JBoss server.log file. The server.log file is found in the "<JBoss Install Dir>\<JBoss version>\server\SASServer[n]\log" directory. For example, a Windows path might be "C:\JBoss\JBoss-4.2.3-GA\server\SASServer[n]\log".

13:39:35,602 ERROR [ContextLoader] Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean
definition with name 'dashboardServices' defined in ServletContext resource
[/WEB-INF/spring-config/services-config.xml]: Could not resolve 
placeholder 'metadata.user'

ERROR [main] – ****************************************************************
ERROR [main] – Required entry, '/sas/properties/environment', not found in the cache.
ERROR [main] – Possible causes include: the RemoteServices VM is not started or
ERROR [main] – there is a multicast address/port mismatch; using 
ERROR [main] – address=239.168.68.1 and port=8561.
ERROR [main] – ****************************************************************

To resolve this problem, you set the following Java Virtual Machine (JVM) option to ensure that JBoss and the JGroups software use the same bind address:

The following sections explain how to set this option on the JBoss application server and in the SAS Remote Services application.

Note: In the steps that follow, replace "<ip-address>" with an actual IP address, as shown in these examples:

*If you used "localhost" as the machine name during configuration, then use this value.

Setting the JVM Option on the JBoss Web application server

• If JBoss is starting from the SASServer[n] script file, then perform the following steps:

  1. Open the SASServer[n].bat(.sh) file in the following directory:

     <JBoss Install Dir>\<JBoss version>\bin

  2. Edit the JAVA_OPTS variable to include the following option:
     

     −Djgroups.bind_addr=<ip-address>

• If JBoss is starting as a Windows service, then perform the following steps:

  1. Open the wrapper.conf file that is located in the following JBoss directory:

     <JBoss Install Dir>\<JBoss version>\server\SASServer[n]

  2. Add an additional Java property to this file that is similar to the following example:

     wrapper.java.additional.nn=–Djgroups.bind_addr=<ip-address>

The value that is specified for nn is the next sequential number.

Setting the JVM Option in SAS Remote Services

• If SAS Remote Services is starting as a Windows service, then perform the following steps:

  1. Open the wrapper.conf file that is located in the following configuration directory:

     <SAS_configuration_directory>\Lev1\Web\Applications\Remote Services

  2. Add an additional Java property to this file that is similar to the following example:

     wrapper.java.additional.nn=−Djgroups.bind_addr=<ip-address>

  The value that is specified for nn is the next sequential number.

• If SAS Remote Services is starting from the RemoteServices script file, then perform the following steps:

  1. Open the RemoteServices.bat(.sh) that is located in the following directory:
     <SAS_configuration_directory>\Lev1\Web\Applications\RemoteServices\
     
     
  2. Add the following option to the :start2 section:

     −Djgroups.bind_addr=<ip-address>

For additional information, see the section labeled "Post-Installation Verification and Configuration of SAS Model Manager" in the SAS Model Manager 3.1 Administrator's Guide.

Operating System and Release Information