When launching or logging on to SAS Enterprise Miner Client on SAS® 9.3 and 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.
Note: Some of these errors could be caused by simply using the incorrect variety of SAS Enterprise Miner. If you are not sure that you are using the correct variety of SAS Enterprise Miner, see the section "Prerequisite: Ensuring that the correct variety of SAS Enterprise Miner is being used".
Background
When launched, SAS Enterprise Miner Client attempts to access the SASHome\sassw.config file and obtain the value that is associated with the SASENVIRONMENTSURL key that is in this file. If the value is successfully obtained, then SAS Enterprise Miner Client treats the value as a URL and 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 Client 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 login screen for SAS Enterprise Miner Client is displayed.
Once you enter credentials and click the Log On button, SAS Enterprise Miner Client attempts to log on to the selected server.
SAS Environment errors stem 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 Client. The error suggests that SAS Enterprise Miner Client is unable to find a value for the SASENVIRONMENTSURL key within the SASHome\sassw.config file.
As a first step, check whether the sassw.config file exists and that it contains a value for the SASENVIRONMENTSURL key. If no value is given for the SASENVIRONMENTSURL key, then specify an appropriate value. Save the changes to the sassw.config file before reattempting to launch SAS Enterprise Miner Client.
By default, SAS 9.3 uses the following format: http://host-name:port/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:
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/LevN/Web/WebServer/htdocs/sas/sas-environment.xml
If the issue persists, then engage SAS Technical Support. Be sure to include these items:
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 Client. The message suggests that SAS Enterprise Miner Client was able to find the value for the SASENVIRONMENTSURL key, but encountered a problem when using that value as a 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 investigation should focus on further diagnostics within SAS Enterprise Miner Client: em_console output. See the section "Collecting em_console output" for details.
If a web browser on the same machine cannot return the XML successfully, then investigation should turn to 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:
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 Client and suggests that SAS Enterprise Miner Client was unable to successfully validate the server(s).
Diagnosing and resolving this particular error typically requires an analysis of both em_console output and server-side logs. See the sections “Collecting em_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:
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 Client and suggests that SAS Enterprise Miner was unable to log on to the selected server.
Diagnosing and resolving this particular error typically requires an analysis of both em_console output and server-side logs. See the sections “Collecting em_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:
The following SAS Note tells about how to collect em_console output:
SAS Note 56002: "Collecting diagnostic output from SAS® Enterprise Miner(tm) Client or SAS Enterprise Miner Workstation with em_console".
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 further, the status of all SAS related server-processes need to be inspected. If there are multiple server-machines in the environment, then the following inspection needs to be performed on each server machine.
services.msc
.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 SAS Note details how files can be transferred to SAS Technical Support, 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.
Prerequisite: Ensuring that the correct variety of SAS Enterprise Miner is being used
In SAS 9.3 and 9.4, there are three primary varieties of SAS Enterprise Miner:
Both SAS Enterprise Miner Client and SAS Enterprise Miner via Java Web Start are designed to connect to a SAS Enterprise Miner server and can generate SAS Environment errors. Alternatively, SAS Enterprise Miner Workstation is self-contained, does not connect to a server, and cannot generate SAS Environment errors when launching or logging on.
Launching the incorrect SAS Enterprise Miner variety can lead to a SAS Environment error.
Example: if SAS Enterprise Miner Client is launched in an environment without a server, then a SAS Environment error is encountered. In this case, there is no method for correcting this error within SAS Enterprise Miner Client itself, because SAS Enterprise Miner Client requires a server. If you want to use SAS Enterprise Miner without a server, then launch SAS Enterprise Miner Workstation.
Given this understanding, a prerequisite to addressing SAS Environment errors is to ensure that you are using the correct variety of SAS Enterprise Miner. This SAS Note discusses how to diagnose and resolve SAS Environment errors within SAS Enterprise Miner Client. A similar SAS Note is available to address SAS Environment errors within SAS Enterprise Miner via Java Web Start:
SAS Note 52932: "SAS Environment errors might be displayed by SAS Enterprise Miner via Java Web Start"
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Enterprise Miner | Microsoft Windows Server 2003 for x64 | 7.1 | 9.3 TS1M0 | ||
z/OS | 7.1 | 9.3 TS1M0 | ||||
Microsoft® Windows® for x64 | 7.1 | 9.3 TS1M0 | ||||
Microsoft Windows Server 2003 Datacenter Edition | 7.1 | 9.3 TS1M0 | ||||
Microsoft Windows Server 2003 Enterprise Edition | 7.1 | 9.3 TS1M0 | ||||
Microsoft Windows Server 2003 Standard Edition | 7.1 | 9.3 TS1M0 | ||||
Microsoft Windows Server 2008 | 7.1 | 9.3 TS1M0 | ||||
Microsoft Windows Server 2008 R2 | 7.1 | 9.3 TS1M0 | ||||
Microsoft Windows Server 2008 for x64 | 7.1 | 9.3 TS1M0 | ||||
Microsoft Windows XP Professional | 7.1 | 9.3 TS1M0 | ||||
Windows 7 Enterprise 32 bit | 7.1 | 9.3 TS1M0 | ||||
Windows 7 Enterprise x64 | 7.1 | 9.3 TS1M0 | ||||
Windows 7 Home Premium 32 bit | 7.1 | 9.3 TS1M0 | ||||
Windows 7 Home Premium x64 | 7.1 | 9.3 TS1M0 | ||||
Windows 7 Professional 32 bit | 7.1 | 9.3 TS1M0 | ||||
Windows 7 Professional x64 | 7.1 | 9.3 TS1M0 | ||||
Windows 7 Ultimate 32 bit | 7.1 | 9.3 TS1M0 | ||||
Windows 7 Ultimate x64 | 7.1 | 9.3 TS1M0 | ||||
Windows Vista | 7.1 | 9.3 TS1M0 | ||||
Windows Vista for x64 | 7.1 | 9.3 TS1M0 | ||||
64-bit Enabled AIX | 7.1 | 9.3 TS1M0 | ||||
64-bit Enabled HP-UX | 7.1 | 9.3 TS1M0 | ||||
64-bit Enabled Solaris | 7.1 | 9.3 TS1M0 | ||||
HP-UX IPF | 7.1 | 9.3 TS1M0 | ||||
Linux | 7.1 | 9.3 TS1M0 | ||||
Linux for x64 | 7.1 | 9.3 TS1M0 | ||||
Solaris for x64 | 7.1 | 9.3 TS1M0 |
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2023-08-24 13:45:35 |
Date Created: | 2014-05-06 10:59:43 |