When you launch a client/server version of SAS Enterprise Miner using either Java Web Start or an installed SAS Enterprise Miner Client application, one of the following errors might be displayed. These errors might also be displayed when you try to log on (after supplying your credentials on the logon page):

The first step to diagnosing these errors is to collect diagnostic output that corresponds to whether you are using SAS Enterprise Miner via Java Web Start, or an installed application:

• Java Web Start: collect Java Console output. See SAS KB0036243: "How to enable logging when SAS Enterprise Miner is launched from Java Web Start (JWS)".


• Installed SAS Enterprise Miner Client application: collect em_console output. See SAS Note 56002: " Collecting diagnostic output from SAS Enterprise Miner Client or SAS Enterprise Miner Workstation with em_console".


•  

Examine the output to see whether the following HTTP 302 status code is displayed:

150 [main] ERROR com.sas.analytics.eminer.visuals.Main  - Could not access HTTP invoker remote service at 

[http://sasbap.demo.sas.com/SASEnterpriseMinerServices/remote/enterpriseMinerService?ticket=ST-1034-5vrhaKMWdJeI71EWCGCp-cas]; 

nested exception is org.apache.commons.httpclient.HttpException: 
Did not receive successful HTTP response: status code = 302, status message = [Found]

The combination of one of these errors and HTTP 302 status code together indicates that the SID file in metadata for SAS Enterprise Miner is expired. You can confirm whether your SID file(s) in metadata is expired by following SAS Note 57183: "Viewing the SID files in metadata via code submission for SAS 9.4 (TS1M1) and earlier or via SAS^® Management Console for SAS^® 9.4 (TS1M2) and later". If the SID file is expired, then renew the SID file in metadata. See the information in the "If You Need to Update the Existing SID Files" section of SAS Note 57183.

Note that you must restart all your SAS services in the correct order after updating the SID files in metadata so that the update is recognized.

If the issue persists even after updating the SID files in metadata, then engage SAS Technical Support. Be sure to include the applicable console output from above, as well as your metadata setinit details, by following SAS Note 57183.

Note: this issue is not relevant for a SAS Enterprise Miner Workstation installation.

Operating System and Release Information