When launching or logging on to SAS Enterprise Miner via Java Web Start on SAS 9.3 or 9.4, you might encounter any of the following error messages:

The application cannot find the URL for the file that identifies the SAS environments.

The application was unable to load the SAS environment definitions. The file location or file contents might be invalid.

The application could not find a valid SAS environment to use.

The application has encountered an unexpected problem with the selected SAS environment.

Collectively, these errors are referred to as SAS Environment errors. There are a number of potential causes for SAS Environment errors. The following information provides a background for the various errors, and outlines diagnostic and resolution approaches for each.

This SAS Note discusses how to diagnose and resolve SAS Environment errors that occur when using SAS Enterprise Miner via Java Web Start. A similar SAS Note is available to address SAS Environment errors within SAS Enterprise Miner Client.

Background

When launched, SAS Enterprise Miner via Java Web Start attempts to determine the SAS Environments URL. If the URL is successfully determined, then SAS Enterprise Miner via Java Web Start attempts to access the resource that is given by the URL. The URL should point to an XML file that is called sas-environment.xml by default.

The contents of the XML file instruct SAS Enterprise Miner via Java Web Start about the location of the servers to which the client can connect. After some cursory inspection of this XML and limited validation of each server, the logon screen for SAS Enterprise Miner via Java Web Start is displayed.

After you enter credentials and click Log On, SAS Enterprise Miner via Java Web Start attempts to log on to the selected server.

SAS Environment errors result from failures that occur during this process. Each error is associated with a failure at a specific point in the process, but each failure could have several possible causes as discussed below.

Diagnosing and resolving "The application cannot find the URL for the file that identifies the SAS environments."

This error message typically occurs when attempting to launch SAS Enterprise Miner via Java Web Start. The error suggests that SAS Enterprise Miner via Java Web Start is unable to determine the SAS Environments URL. The main.jnlp file that is associated with the Launch link on the Status page contains configuration information that is used to make this determination.

You can inspect the configuration of the main.jnlp file on the Status page under the heading "Enterprise Miner Configuration for Java Web Start". The two configuration elements of interest are "SAS Environment URL" and "Inject Default sas-environment File".

The URL might be explicitly defined with a value under the "SAS Environment URL" name. The main.jnlp file might also be configured to inject the default URL with a value of "true" under the "Inject Default sas-environment File" name. Note that it is possible to improperly configure the main.jnlp file such that an explicit URL is not defined and that the default URL is not injected. Such a configuration most probably causes a SAS Environment error because there is no URL to use. If the URL is explicitly defined and the default URL is injected, then the explicitly defined URL takes precedence.

The configuration of the main.jnlp file can be modified within SAS^® Management Console. Follow these steps:

1. On the Plug-ins tab, expand Application Management ► Configuration Manager ► SAS Application Infrastructure.
2. Right-click Enterprise Miner Mid-Tier JWS, and choose Properties.
3. Select the Settings tab.
4. Select Enterprise Miner Java Web Start Options from the list on the left.
5. Make the desired changes in the panel on the right, and then click OK.

The Status page needs to be re-loaded in the browser in order for the changes to take effect. After re-loading, the changes should be reflected on the Status page and within the main.jnlp file.

By default, the main.jnlp file is configured without an explicit URL defined, but with the default URL injected.

By default, SAS 9.3 uses the following format: host-name:port/Levn/SASLogon/sas-environment.xml
host-name is the fully qualified host-name of the server machine that is running the web application server.
port is the web-application-server port that is listening for HTTP requests.
Default listening ports are: JBoss, 8080; WebSphere, 9080; WebLogic, 7001. The default format above assumes that this default location of the sas-environment.xml file is used: SASConfig/Lev#/Web/Common/sas-environment.xml

SAS 9.4, by default, uses the following format: http(s)://host-name:port/sas/sas-environment.xml

The value for host-name:port depends on your configuration. Use the host-name:port that the users use in the URL to access the SAS Web Applications. This host:port could be as follows:

• a single web server host
• a Reverse Proxy host
• a load balancer

By default, in the single web server host configuration, the listening port for the SAS web server on Windows servers defaults to 80. On UNIX servers, the port defaults to 7980. The default format above assumes that this default location of the sas-environment.xml file is used: SAS-configuration-directory/Lev/Web/WebServer/htdocs/sas/sas-environment.xml

If the issue persists, then engage SAS Technical Support. Be sure to include these items:

1. a screenshot of the error message
2. a copy of the main.jnlp file that is being used

Diagnosing and resolving "The application was unable to load the SAS environment definitions."

This error message typically occurs when attempting to launch SAS Enterprise Miner via Java Web Start. The message suggests that SAS Enterprise Miner via Java Web Start was able to determine the SAS Environments URL, but encountered a problem when using the URL. The problem could occur while accessing the URL, while inspecting the XML contents, or while validating the server(s) that are referenced in the XML.

As a first step, attempt to access the URL with a web browser on the problematic machine. If a web browser on the same machine can return the XML successfully, then investigate diagnostics within SAS Enterprise Miner via Java Web Start: Java Console output. See the section "Collecting Java Console output" for details.

If a web browser on the same machine cannot return the XML successfully, then investigate the server or to the connection between the client and server. Is the server process serving up the XML and running as expected? See the section "Inspecting server status" and "Collecting relevant server logs" for details.

If the issue persists, then engage SAS Technical Support. Be sure to include these items:

1. a screenshot of the error message
2. a copy of the main.jnlp file that is being used
3. a screenshot that illustrates the results of the attempt to access the URL with a web browser
4. If accessing the URL via web browser is unsuccessful, then send these items:
   1. a screenshot or other output that illustrates the status of the server processes as described in the section "Inspecting server status"
   2. relevant server-logs as described in the section "Collecting relevant server-logs"
5. If accessing the URL via web browser is successful, then send this item: Java Console output from the time of the error as described in the section "Collecting Java Console output"

Diagnosing and resolving "The application could not find a valid SAS environment to use."

This error message typically occurs when attempting to launch SAS Enterprise Miner via Java Web Start. The error suggests that SAS Enterprise Miner via Java Web Start was unable to successfully validate the server(s).

Diagnosing and resolving this particular error typically requires an analysis of both Java Console output and server-side logs. See the sections “Collecting Java Console output” and “Collecting relevant server-logs” for more details.

If the issue persists, then engage SAS Technical Support. Be sure to include these items:

1. a screenshot of the error message
2. a copy of the main.jnlp file that is being used
3. Java Console output as described in the section "Collecting Java Console output"
4. relevant server-logs as described in section "Collecting relevant server-logs"

Diagnosing and resolving "The application has encountered an unexpected error with the selected SAS environment."

This error message typically occurs when attempting to log on using SAS Enterprise Miner via Java Web Start. The error suggests that SAS Enterprise Miner via Java Web Start was unable to log on to the selected server.

Diagnosing and resolving this particular error typically requires an analysis of both Java Console output and server-side logs. See the sections “Collecting Java Console output” and “Collecting relevant server-logs” for more details.

If the issue persists, then engage SAS Technical Support. Be sure to include these items:

1. a screenshot of the error message
2. a copy of the main.jnlp file that is being used
3. Java Console output as described in the section "Collecting Java Console output"
4. relevant server-logs as described in section "Collecting relevant server-logs"

Collecting Java Console output

The following SAS Note tells about how to collect Java Console output:

SAS Note 47311: "How to enable logging when SAS Enterprise Miner is launched from Java Web Start"

Inspecting server status

If any of the SAS related server-processes are not Started (or not Up), then a SAS Environment error could occur. In order to investigate this possibility, the status of all SAS related server-processes needs to be inspected. If there are multiple server-machines in the environment, then the following inspection needs to be performed on each server machine.

• For server processes on Windows operating systems, inspect the status of the SAS related services that are displayed in the Services window. To locate the Services window, select Start to display the Search programs and files text box. Enter services.msc.
• For server processes on UNIX operating systems, inspect the output that is displayed when you execute the following command from this location:

       location: SASConfig/Lev#/
        command: ./sas.servers status
  

For SAS 9.3 environments, inspecting the web-application-server status is an additional step that must be performed according to the provider’s instructions.

If any processes are not started, then the server processes need to be re-started. Be sure to stop and start the processes in the correct order as described in the documentation below:

"SAS 9.3 Intelligence Platform: System Administration Guide, Second Edition", Overview of Server Operation
"SAS 9.4 Intelligence Platform: System Administration Guide, Second Edition", Overview of Server Operation

Collecting relevant server-logs

Collect and submit all of the logs in the following server locations from the time of the error:

  SAS 9.3:
     SASConfig/Lev#/Web/Logs/
     JBoss/server/server_name/log/
     WebSphere/profiles/profile_name/logs/server_name/
     WebLogic/user_projects/domains/domain_name/servers/server_name/logs/

  SAS 9.4:
     SASConfig/Lev#/Web/Logs/SASServer1_1/
     SASConfig/Lev#/Web/Logs/SASServer11_1/ (if such a path exists)
     SASConfig/Lev#/Web/WebAppServer/SASServer1_1/logs/
     SASConfig/Lev#/Web/WebAppServer/SASServer11_1/logs/ (if such a path exists)
     SASConfig/Lev#/Web/WebServer/logs/

It is possible that these log files are too large to send via email, even after compression. The following Knowledge Base article explains how files can be transferred to SAS Technical Support via FTP, after a support request number has been created: KB0036136, “How to upload and download files using the SASTSDrive file sharing server.”

A support request number is created automatically when you engage SAS Technical Support.

Operating System and Release Information