When attempting to open the Interactive Decision Tree window in SAS Enterprise Miner, you might encounter then following error message:

There are a number of possible causes for this error message. If you encounter this error message, then complete the steps below to diagnose and resolve the error. These steps apply to SAS Enterprise Miner 7.1 and forward. These steps apply only to SAS Enterprise Miner Client and SAS Enterprise Miner via Java Web Start. These steps do not apply to SAS Enterprise Miner Workstation.

Steps to diagnose and resolve an "Unable to open Interactive Decision Tree" error

1. As the error message suggests, ensure that you run the predecessors to the Decision Tree node before you click the Interactive property. Then, right-click the Decision Tree node, and select Update.
    
2. Check the configuration of the involved SAS Workspace Server to ensure that the server enables "Allow clients to reconnect". Details on how to further diagnose and resolve this possible cause are available in the following SAS Note:
   
   SAS Note 49165: "Interactive error: 'Unable to open Interactive Decision Tree. Please make sure you have run the predecessors to this node and update the path'"
    
3. If SAS Enterprise Miner is using a SAS Workspace Server that resides on a UNIX operating system, then check to see whether the com.sas.analytics.eminer.midtier logger is set to DEBUG. By default, the value for this logger is defined in the following file:
   
   SASConfig/Lev#/Web/Common/LogConfig/SASEnterpriseMiner-log4j.xml
   
   The default value for this logger is WARN. If you encounter this error and this com.sas.analytics.eminer.midtier logger is set to DEBUG, then decrease the logging level back to the default value of WARN. Note that in order for changes to the logging level to take effect, you need to restart the SAS Web Application Server(s).
    
4. If the error persists after completing the above steps, then engage SAS Technical Support for assistance. Be sure to include this information:
    
   1. The release of SAS Enterprise Miner that you are using. Examples: 7.1, 12.1, 12.3, 13.1, 13.2, 14.1, and so on.
       
   2. The variety of SAS Enterprise Miner that you are using:
      • SAS Enterprise Miner Client
      • SAS Enterprise Miner via Java Web Start
   3. A screenshot of the error message that you encountered, including the entire SAS Enterprise Miner window. The bottom right corner of the application is especially important because it tells which SAS Workspace Server is in use.
       
   4. A screenshot of what is displayed when you click the Details button that is displayed with the error message.
       
   5. A screenshot that illustrates that the previous nodes have been run (as discussed in step 1 above).
       
   6. A screenshot of the SAS Management Console showing that "Allow clients to reconnect" is checked for the appropriate SAS Workspace Server (as discussed in step 2 above).
       
   7. A copy of the file: SASConfig/Lev#/Web/Common/LogConfig/SASEnterpriseMiner-log4j.xml (as discussed in step 3).
       
   8. SAS Workspace Server logs from the time of the error. If you do not already have these logs, the follow these steps:
      1. Enable SAS Workspace Server logging (as discussed in the following links)
      2. Re-create the error.
      3. Collect the generated Workspace Server logs.
         Default location: SASConfig\Lev#\SASApp\WorkspaceServer\Logs\
         
         Create a Log File for Workspace Server Troubleshooting :: SAS 9.4 Intelligence Platform: System Administration Guide
         
         Create a Log File for Workspace Server Troubleshooting :: SAS 9.3 Intelligence Platform: System Administration Guide
          
   9. 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 details 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